- 🇩🇪Germany Anybody Porta Westfalica
Totally agree here. Just had the same points. The machine name could still be kept as first value in the select, having the human readable name in brackets second.
Sorting the field names alphabetically totally makes sense!
- First commit to issue fork.
- 🇺🇸United States mortona2k Seattle
Sorting the field machine names was easy, and a big QOL improvement when you have lots of fields.
We could check this MR in now and improve it further later. Or create a separate issue?
- 🇺🇸United States erutan
Can confirm that #7 works on 10.5.
Here's a quick patch that includes the labels as well if someone wants to take a look and possibly clean it up.
- First commit to issue fork.
- 🇺🇸United States mlncn Minneapolis, MN, USA
This latest, greatest, and i hope final update to the merge request shows the label (when it exists, which in my testing is always) and what bundle it came from, and if there are more bundles.
field_example "Example" on node:page & 1 other
Also, it sorts by field machine name within entity types, but leaves fields grouped by entity type. We now show the entity type with the bundle (media:image, node:article, user:user - in the same manner displayed in the Bundles field below) so it should become evident quickly that all the media fields are first, then node fields, then user, for example.
For me, definitely the most confusing thing was not knowing what entity type each field name was on, since fields are not shared across different types of entities, so the exact same name can appear twice. Showing the entity type as well as the bundle definitely helps but i still think grouping by entity type is clearer.
As a follow-up we may want to add help text that the label may vary on the additional bundles (where we note "& 1 other" or "& 2 others" etc for each field), but putting "label may vary on Y other bundles" made the already-long option text too long.
The other follow-up that could improve UX is reminding people they can filter for which bundles will have CER active for below. (So field_media_image "Image" on node:page & 5 others can be synchronized with media:image for node:article only.) Also, that saving the form after selecting the fields will update the autocomplete options in Bundles to only the relevant ones (i don't think it works the other way around, but a way to filter the first and second fields by bundle would be nice).