Problem/Motivation

#2543726: Make $term->parent behave like any other entity reference field, to fix REST and Migrate support and de-customize its Views integration is commited to 8.6. That removes the need for the work-around in TermEntityNormalizer.
See CR https://www.drupal.org/node/2936675

Proposed resolution

When Drupal 8.6.0 is released, remove TermEntityNormalizer and tag a new release which has drupal:system (>= 8.6.0) as a dependency in its info.yml file.

Remaining tasks

Patch + wait.

User interface changes

None.

API changes

None.

Data model changes

None.

Comments

Wim Leers created an issue. See original summary.

wim leers’s picture

Status: Active » Postponed
wim leers’s picture

Title: [PP-1] Remove TermEntityNormalizer when #2543726 lands » [PP-1] Conditionally register TermEntityNormalizer when #2543726 lands, remove when Drupal 8.6.0 is released
wim leers’s picture

Issue summary: View changes
larowlan’s picture

I would prefer to do a new release with a requirement on system > 8.5.0 and just remove it in one fell swoop, instead of adding conditional registration.
8.4 will be EOL when 8.5 is out.

andypost’s picture

I like the idea of new release, it will help better normalizers as well

wim leers’s picture

Title: [PP-1] Conditionally register TermEntityNormalizer when #2543726 lands, remove when Drupal 8.6.0 is released » [PP-1] When Drupal 8.5.0 is released, remove TermEntityNormalizer and tag a new release
Issue summary: View changes

That works too!

wim leers’s picture

Title: [PP-1] When Drupal 8.5.0 is released, remove TermEntityNormalizer and tag a new release » [PP-1] When Drupal 8.6.0 is released, remove TermEntityNormalizer and tag a new release
wim leers’s picture

Title: [PP-1] When Drupal 8.6.0 is released, remove TermEntityNormalizer and tag a new release » When Drupal 8.6.0 is released, remove TermEntityNormalizer and tag a new release

And that patch already was committed to 8.6, so there's no explicit blocker anymore. There's just waiting … ~8 months :)

heddn’s picture

Status: Postponed » Active

We can get back to work on this again now that the first alpha for 8.6 was released.

andypost’s picture

andypost’s picture

Status: Active » Needs review
StatusFileSize
new2.9 KB
berdir’s picture

Status: Needs review » Reviewed & tested by the community

Lovely.

andypost’s picture

StatusFileSize
new630 bytes
new3.51 KB

Also tuned composer and info files

andypost’s picture

Issue summary: View changes

fixed IS to 8.6 according to https://www.drupal.org/node/2936675

berdir’s picture

Status: Reviewed & tested by the community » Fixed

Committed.

  • Berdir committed 0619a2f on 8.x-1.x authored by andypost
    Issue #2921377 by andypost: When Drupal 8.6.0 is released, remove...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.