Follow-up to #2543726: Make $term->parent behave like any other entity reference field, to fix REST and Migrate support and de-customize its Views integration

@todo Merge here \Drupal\taxonomy\TermHierarchyInterface

Comments

dagmar created an issue. See original summary.

dagmar’s picture

dagmar
Primary language Spanish
Location Argentina
CreditAttribution: dagmar at Globant commented
Title: Follow up #2543726: @todoMerge here \Drupal\taxonomy\TermHierarchyInterface » Follow up #2543726: @todo Merge here \Drupal\taxonomy\TermHierarchyInterface
catch’s picture

catch
he/him
Primary language English
CreditAttribution: catch at Third and Grove commented
Status: Active » Closed (duplicate)

This should probably be part of #2716163: [META] Remove deprecated classes, methods, procedural functions and code paths outside of deprecated modules on the Drupal 9 branch, but with the other issue not in yet it's difficult to see what this is about.

Version: 9.x-dev » 9.0.x-dev

The 9.0.x branch will open for development soon, and the placeholder 9.x branch should no longer be used. Only issues that require a new major version should be filed against 9.0.x (for example, removing deprecated code or updating dependency major versions). New developments and disruptive changes that are allowed in a minor version should be filed against 8.9.x, and significant new features will be moved to 9.1.x at committer discretion. For more information see the Allowed changes during the Drupal 8 and 9 release cycles and the Drupal 9.0.0 release plan.