![]() Additionally, we have 'base_field_override' config entities for using config to override a code-defined base field, but do not have 'bundle_field_override' config entities for overriding code-defined bundle fields.So, in theory, contrib modules can implement non-config-based bundle fields, but we don't provide an implementation class with which to do so.Core's only real implementation of bundle fields is via field_entity_bundle_field_info(), which implements them via config entities.HEAD's current example of hook_entity_bundle_field_info() creates a bundle field via BaseFieldDefinition::create(), but that is incorrect, because BaseFieldDefinition::isBaseField() returns TRUE, which is incorrect for a bundle field.In this issue, let's call the latter case "bundle fields". ContentEntityInterface::bundleFieldDefinitions() and hook_entity_bundle_field_info() can return either bundle-specific overrides of base field definitions, or definitions of fields that are not base fields. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |