Should the single-value parameters (on Feature Filters) be serialized as arrays ? about featuremanagement-dotnet HOT 3 CLOSED

Is there an easy/recommended way to avoid the above issue when configuring the "AllowedBrowsers" parameter in Azure App Configuration UI, as provided in this example: appsettings.json ?

"Home": true,
    "Beta": {
      "EnabledFor": [
        {
          "Name": "Browser",
          "Parameters": { // This json object maps to a strongly typed configuration class
            "AllowedBrowsers": [ "Chrome", "Edge" ]
          }
        }
      ]
    }

To obtain the same array of values ["Chrome", "Edge"] as per above example of appsettings.json, the customer has to configure the parameter "AllowedBrowsers" twice in Azure App Configuration UI.

• AllowedBrowsers=Crome
• AllowedBrowsers=Edge

from featuremanagement-dotnet.

Related to Azure/AppConfiguration#147. The only way to avoid this before we revamp this UI to have more intuitive support for arrays is to suffix the array element with it's position in the array.

E.g.
Allowed:0 Chrome
Allowed:1 Edge

It is on our to-do list to make this more user friendly. At this point it's very hard to work with arrays like this since managing indexes is a lot of overhead.

from featuremanagement-dotnet.

Arrays are supported now. Azure/AppConfiguration#147

from featuremanagement-dotnet.