For the ConfigEditor.py tool, currently what it show up in the UI is the "name" field in the XML, which is also used for generating profile header file that will be consumed by C code, so the naming must follow the C coding rules, but from the user point of view, sometimes the variable name is hard to understand.
For providing more flexibility about the string show up in the tool, it would be better to support the ConfigKnob show up as a string that support white space. ex "Boot Option 1" instead of "BootOption1"
Solution Overview
Add one more field called "Prompt", then in the XML, it would like below example.
For the ConfigEditor.py.
If there is a prompt field of a item, then the tool UI would use the prompt string to show up.
For backward compatible reason, if the XML does not have the prompt field, it would still follow original behavior that use name field to show up in the tool UI.
Feature Overview
For the ConfigEditor.py tool, currently what it show up in the UI is the "name" field in the XML, which is also used for generating profile header file that will be consumed by C code, so the naming must follow the C coding rules, but from the user point of view, sometimes the variable name is hard to understand.
For providing more flexibility about the string show up in the tool, it would be better to support the ConfigKnob show up as a string that support white space. ex "Boot Option 1" instead of "BootOption1"
Solution Overview
Add one more field called "Prompt", then in the XML, it would like below example.
For the ConfigEditor.py.
Alternatives Considered
No response
Urgency
Low
Are you going to implement the feature request?
Someone else needs to implement the feature
Do you need maintainer feedback?
Maintainer feedback requested
Anything else?
changray@microsoft.com would be the one to study and create PR for review.