Posted by fago on September 28, 2012 at 5:32pm
25 followers
Jump to:
| Project: | Drupal core |
| Version: | 8.x-dev |
| Component: | field system |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
| Issue tags: | Entity Field API |
Issue Summary
With #1696640: Implement API to unify entity properties and fields being committed every "property" on an entity is called a "field" now. Once everything is converted to use that, most code should rely just upon the Entity Field API. However, still some code will have to work specifically with field.module fields, i.e. fields that can be configured via the UI (and so extend the entity).
Some suggestions for this were:
- configurable field
- dynamic field
Fields defined by the entity type are right now called "base fields", other suggestions were
- pre-defined
- static
- intrinsic
Also, the 'fieldable' key in hook_entity_info() could be need renaming. E.g. to 'extendable' or 'configurable'.
Comments
#1
#2
My current favourites would be:
"configurable field", "configurable" entity types (instead of fieldable) and "base field".
#3
Suppose configurable is not suitable here because of configurables (ConfigEntity) which would lead to misunderstanding
Extendable makes more sense
#4
True, I've not thought of that. Given the high potential for confusion, I agree this is a dealbreaker for configurable.
#5
New suggestion:
"configurable field", "extendable" entity types (instead of fieldable) and "base field".
So if an entity type is extendable, you can configure additional fields for it.
#6
The term "configurable" is not used at all by ConfigEntity, that's "configuration entity".
We just still use it in issue tags for legacy reasons, but we can update those.
#7
When this gets resolved, there will be something todo related it #1498674-82: Refactor node properties to multilingual.