Feature Suggestion: Need Easily Understandable Names for Variants

[cosmic-flood]

Feature Suggestion: Need Easily Understandable Names for Variants

[mucoban]

In this case, we need to add name field for variant add and edit sections.


And if we will add name property here, backend codes will need to be changed according to this.

[cosmos-explorer]

@mucoban FYI, We have just moved this to the top of our priority list and got a solution. If you haven't started the implementation of your solution, don't waste your time to do it. We should be able to merge our solution tomorrow.

[mucoban]

Hi @cosmic-flood, is it okay for a variant to have a key as 'variantName': 'variant abc' ? So in ui, I can check if the variant is json and has that key, if so, I can show variantName instead of variant's json content. Is this solution okay for you?

[cosmos-explorer]

Hey @mucoban , it's a great idea, you can name the key as name directly. The property is for all type of variation, not just json.

If we do this, we need to think about the UI design carefully, especially in the flag targeting page. We should display the names in the following screen and user should be able to edit the names

We would be happy to listen to your ideas about the UI design.