Closed (fixed)
Project:
Drupal core
Version:
9.4.x-dev
Component:
comment.module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
25 Oct 2019 at 16:54 UTC
Updated:
22 Mar 2022 at 15:14 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
adamps commentedCustom block entity type seems fine - there is no preprocess function or template that interferes with the display of any base field.
First patch is missing tests but it gives us a starting point for discussion.
Comment #3
andypostLooks nice start, also this may affect related issues
Comment #4
andypostComment #7
andypostComment #8
andypostRe-roll
Comment #10
andypostFix tests
Comment #12
abx commentedI couldn't apply patch due to this line
'comment.html.twig' => '68718b6de9a0d21f5180a9fbcc40987f',
it should be
'comment.html.twig' => 'f5f6371850371b2db33dacceca455b1c',
Comment #14
ilya.no commentedI've updated patch with tests fix.
Comment #15
adamps commentedThanks @ilya.no. The patch still needs tests, so I wonder it if needs to be "Needs work"? I hope to find some time soon but also quite busy, so if anyone else can that would be great.
Comment #16
andypostThank you, meantime I see following related efforts
- #1875974: Abstract 'component type' specific code out of EntityDisplay
- #2869124: Base field overrides cannot be translated which renders some entity form labels untranslatable
- #2844302: Move Field Layout data model and API directly into \Drupal\Core\Entity\EntityDisplayBase
Comment #17
andypostNW for tests, I bet something could be taken from node tests
Comment #18
ilya.no commentedAttaching patch with test. Not sure, whether it's too simple.
Comment #19
andypostThank you, looks great
Comment #20
adamps commentedGreat thanks, looks good to me too.
It seems that my original patch has been reviewed by @ilya.no + @andypost, and now @ilya.no wrote tests reviewed by @andypost and me.
It feels to me that this is ready for the core committers to look at now. It's very much a copy of #2923701: Mechanism to disable preprocessing of node base fields so they can be configured via the field UI so hopefully nothing controversial, thanks.
Strictly speaking we probably ought to have an "only tests" patch that fails.
Comment #21
adamps commentedYou can test out this patch using the latest 2.0.x dev release of Manage Display module.
Comment #23
adamps commentedRandom fail
Comment #26
catchGreat to see this one ready. Will be amazing to be able to remove these hunks from preprocess when the rest of the steps are done.
Committed/pushed to 10.0.x and cherry-picked to 9.4.x, thanks!
Comment #27
adamps commentedGreat many thanks @catch.
Yes, this completes phase A from #2353867: [META] Expose Title and other base fields in Manage Display of "removing the obstacles". We can now move onto the journey to deprecate the old hunks hopefully in D10 for removal in D11.