UX/DX Feedback for enhancers

Created on 5 September 2018, almost 6 years ago
Updated 3 April 2024, 2 months ago

This is some initial feedback about Enhancers just to collect some thoughts on it, at e0ipso's request. The UI for this is not easy, another example of an awkward UI is the search_api's UI for adding indexed fields, so I'm not a UX guy and I'm just highlighting some things that could make a difference.

Micro-managing fields

I have an enhancer for links/paths that just makes some project specific changes. This enhancer essentially applies to only a field types (link url, file path and entity path) but to apply it I needed to go through hundreds of fields on dozens of entities.

It would be great if I could say "apply this enhancer to every field of type X" - I guess it would be a different UI screen/section?

Visibility of which enhancers are applied

Similar to the above, if I want to check that those dozens of enhancers are applied correctly. My first issue is I can't see easily which fields are the links/etc. I need to cross check this against the entity field configuration. I then need to do the drop-down arrow against any fields to see if there are already any enhancers.

Now separated in πŸ“Œ Expand enhancer UI if applied Active

Allow enhancers to define field type in the plugin design

This would help a fair bit, when allocating enhancers, to not be shown ones that do not apply. I assume this would apply at the plugin level.

✨ Feature request
Status

Active

Version

3.0

Component

Code

Created by

πŸ‡¦πŸ‡ΊAustralia sime Canberra

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.69.0 2024