- 🇫🇷France musa.thomas France 🇫🇷
any update about this ?
I do a test and extra field work perfectly but computed field are stille not available inside layout builder - 🇷🇴Romania claudiu.cristea Arad 🇷🇴
As there is an ExtraFieldBlockDeriver why not a new ComputedFieldBlockDeriver? Because I think there are zero chances that
::getFieldMap()to be fixed I would prefer to have a single collector to avoid the possibility of having different ids in case it is finally integrated into the getFieldMap method, in addition to not making the editing to editors more complex than it already is (by having another different category).
If that happens, as code makes an array merge, i think no other change will be required than removing deprecated code (no massive update should be necessary, in any case, display, overrides & other like section library...).I've been trying to use "hook_entity_field_storage_info", "hook_entity_bundle_field_info" && "\Drupal::service('field_definition.listener')->onFieldDefinitionCreate($bundle_definition);" into "hook_entity_bundle_create" & this patch is no necessary but that generates other problems like field table removed when a bundle field is used more than once. That was based into "entity_schema_test_entity_field_storage_info".
We have been using #patch with core ^9.5 && ^10 for a while & is working perfectly (VLSuite). So only pending step whould be test coverage.
- Status changed to Closed: duplicate
9 months ago 10:54pm 13 March 2024 - 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
Why do we think we cannot fix
::getFieldMap()🤔Let's fix that in #3045509: EntityFieldManager::getFieldMap() doesn't show bundle fields → 😊.
