Closed (outdated)
Project:
Drupal core
Version:
9.4.x-dev
Component:
field system
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
17 Jul 2014 at 15:37 UTC
Updated:
10 Aug 2022 at 15:27 UTC
Jump to comment: Most recent
Comments
Comment #1
iantresman commentedComment #2
webchickI think this sounds like a cool feature, but I'm unsure about adding it to core. Do you anticipate 80% of websites needing this? If so, what do you feel the use cases are? If not, it might make more sense to create a contributed module instead for this.
Comment #3
iantresman commentedI had originally suggested extending the standard CCK text field. A YAML field solves this, but is more flexible. It is also part Hierarchical Select (but much easier to set up), part Conditional Fields, part mixed-data group field, etc.
I think setting the bar at 80% is unrealistic. Probably 80% of sites will use fields, but 80% won't use all field types. I've often considered using, for example, Hierarchical Select, but it is rather challenging. YAML looks trivial to use. I've often wanted a look-up field, YAML does it easily. So I think it's simplicity of use compared with its sophistication, would make people use it.
I think the challenge will be (a) making flexible and usable widgets (b) enabling the display and selection of data
Note that I am not that familiar with YAML, so there may be errors in the examples below.
Usage examples
As an extended text field:
As a Hierarchical Select field:
Comment #15
smustgrave commentedMoving this to closed outdated as this hasn't had a follow up since moving into PNMI 8 years ago.
If you feel it's still an issue please reopen with an updated issue summary and steps for where you are seeing it