Closed (fixed)
Project:
Default Content
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
6 Nov 2017 at 19:05 UTC
Updated:
29 Feb 2020 at 10:44 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
wim leersComment #3
wim leersComment #4
wim leersComment #5
larowlanI 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.
Comment #6
andypostI like the idea of new release, it will help better normalizers as well
Comment #7
wim leersThat works too!
Comment #8
wim leers#2543726: Make $term->parent behave like any other entity reference field, to fix REST and Migrate support and de-customize its Views integration will not ship in 8.5, only in 8.6.
Comment #9
wim leersAnd that patch already was committed to 8.6, so there's no explicit blocker anymore. There's just waiting … ~8 months :)
Comment #10
heddnWe can get back to work on this again now that the first alpha for 8.6 was released.
Comment #11
andypost8.6 has more issues raised in #2933777: REST/Serializer improvements in core/contrib make it less suitable for default_content use case
I think better to release alpha 8 for 8.5 core & decide on next alpha in parent issue
Comment #12
andypostIn #3092985-11: Deprecation notice: The entity_type.repository service must be passed to ContentEntityNormalizer::__construct() the same was suggested and 8.6 is gone from supported releases
Comment #13
berdirLovely.
Comment #14
andypostAlso tuned composer and info files
Comment #15
andypostfixed IS to 8.6 according to https://www.drupal.org/node/2936675
Comment #16
berdirCommitted.