core: frontend: vehicle-setup: include parameter names #3044
Description
Current behaviour
We have setup pages that group together relevant parameter sets and somewhat intentionally hides the raw parameter names in favour of more intuitive ones. While that is convenient when it works correctly, it can make it hard to determine which parameters are actually being changed, and also doesn't provide much explanation when things aren't working / aren't available (e.g. a user can't search for if their vehicle is missing a parameter if they don't know which parameter to look for).
Expected or desired behaviour
It should be possible to determine the parameter changed by each control, especially for experienced users.
Ideally we want that to avoid confusing inexperienced users (who we may wish to hide it from entirely), and excessive interface clutter (so we don't want lots of large icons, and likely don't want always-visible parameter names beside the intuitive ones).
One option would be to have little info icons beside the intuitive parameter names that can be hovered over or clicked on to display the raw name (perhaps even in place of the intuitive name, to avoid needing extra interface space).
Additional Context
Idea initially raised by @vshie, in an internal discussion.
Prerequisites
- I have checked to make sure that a similar request has not already been filed or fixed.