Display name for needs_extra_options
See original GitHub issueIt would be nice to have a possibility to specify an additional name for needs_extra_options
. For example, an internal name (as of now) and an external name which is then displayed in, for instance, needtable
.
This might require the specification of needs_extra_options
similar to needs_types
needs_extra_options= [dict(option="sec-asm, title="Security Assumption") ]
This could be extended with additional attributes in the future.
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Change the display name that email recipients see - Microsoft ...
Change the display name that email recipients see · In Outlook, choose File > Account Settings > Account Settings. Options available when you...
Read more >displayName | Apple Developer Documentation
Instance Property. displayName. The name of the font, including family and face names, to use when displaying the font information to the user....
Read more >Add display name guidelines - Slack
Members can use display names to have teammates @mention them in Slack by their first names or nicknames. As an owner of a...
Read more >What are Display Names and Usernames? | The Mighty Help ...
A Display Name is how you want to be known to the community. It can be different from your real name. It is...
Read more >Search name, not display name - ServiceNow Community
Solved: I'm having a problem where my catalog has a search field to find company names from a table. When searching company names...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@danwos I think the
needs_option_titles
could be a good compromise. @twodrops, what do you think ? I had another idea as a workaround: Since it is something which is defining the view of the data, it might also be feasible to just define a needs_layout. But that is too much overhead to achieve this.The change will not be so easy, as a lot of code is working with
needs_extra_options
. So changing the allowed data types would affect a lot of code, which is not related to this new feature.Maybe it is easier to introduce a new config variable, like
needs_option_titles = {"new_option": "Another Name"}
. It’s not the best solution for user experience, but it would have the lowest impact on our code.Just to be clear, to add a new option with a custom name, both config vars
needs_extra_options
andneeds_option_titles
need to be configured!