TrimKeyPrefix for FeatureFlagOptions

[Edgaras91]

This is my setup, see the last code line below

configBuilder.AddAzureAppConfiguration(options =>
            {
                ...
                options.Select($"{applicationName}:*", $"{azureConfigEnv}");
                options.TrimKeyPrefix($"{applicationName}:");

                options.UseFeatureFlags(featureOptions =>
                {
                    featureOptions.Select($"{applicationName}/", azureConfigEnv);
                    featureOptions.TrimKeyPrefix($"{applicationName}:"); <==== Doesn't Exist!
                });
            });

[zhenlan]

It's correct that the TrimKeyPrefix API doesn't exist for feature flags because you don't need it if you create feature flags like below

In feature flags, you can add any necessary prefixes to the key, but you don't have to trim them as long as they are not part of the flag name.

[Edgaras91]

Then the list of features would be without a prefix, and hard to find (hope features page will have filters and nesting in the future like configs).
We would prefer to see the prefixes and not worry about them in the application (just like the configs).

[zhenlan]

@Edgaras91 in the Feature manager UI, you will see the prefix in the 'Key' column. Maybe we should enable sorting by the 'Key' column so feature flags with the same prefix are organized together. We will soon release an update so you can show/hide or rearrange the columns. We will continue iterating on the UI. Your feedback is appreciated.

[zhenlan]

Please let us know if there is further feedback. Closing for now.