Closed satuday closed 4 years ago
Hello @satuday,
When no FeatureManagement section is provided the library treats the root of the registered IConfiguration as the featuremanagement section. This is detailed in the readme.
Using a FeatureManagement section would be the proper method to prevent all configuration keys from being returned from this API. Otherwise, there is no way to distinguish a non-feature configuration key vs a feature configuration key.
Closing by design. To avoid this please use a "FeatureManagement" section in the application's configuration or pass in an IConfiguration instance which does not contain non-features.
@satuday Hello, I've recently just come across this same issue whilst testing integration with Azure App Configuration and its feature management functionality. Did you manage to get around this using the above steps? Or did you find a different approach that perhaps you could share?
Unfortunately I did not. I stopped using the feature manager and switched to launchdarkly.
Super confusing behavior IMO
I dont have a 'FeatureManagement' section in my appsettings.json, but when I call GetFeatureNamesAsync, it is returning key in IConfiguration.
I'd also try adding 'FeatureManagement' section without any feature set, but the result was the same.
the following are some of the names return from GetFeatureNamesAsync()