builder.Services.AddFeatureManagement() with configuration section does not work since v3.0.0 about featuremanagement-dotnet HOT 7 CLOSED

Agree, we should preserve the behavior for this override. Thanks for raising the issue.

from featuremanagement-dotnet.

@FredericVaugeoisFlo I think this should be an oversight. Thanks for calling it out.
The override method AddFeatureManagement(configuration) should support your scenario. Otherwise, I think this method will be kind of useless.
My thought is that we can add an option for ConfigurationFeatureDefinitionProvider to read from the root of the configuration if no "FeatureManagement" section is found (the behavior in 2.6.0). This option should be false by default. But if it is registered by AddFeatureManagement(configuration), the option will be set to true.

from featuremanagement-dotnet.

Great thank you!

from featuremanagement-dotnet.

Will this feature be patched to work for .NET 8 again?

I don't expect any specific issue for .NET 8. All versions of .NET should behave the same.

It would be relevant to name the configuration-section to a custom name instead of relying on only "FeatureManagement".

Is this a request for that capability? That should be doable once we address the issue using the pattern in the initial issue description. services.AddFeatureManagement(configuration.GetSection("MyCustomFlagsSection"));

from featuremanagement-dotnet.

https://learn.microsoft.com/en-us/azure/azure-app-configuration/use-feature-flags-dotnet-core?tabs=core6x

In our public document, we mentioned this usage.

from featuremanagement-dotnet.

Will this feature be patched to work for .NET 8 again? It would be relevant to name the configuration-section to a custom name instead of relying on only "FeatureManagement".

from featuremanagement-dotnet.

Fixed in release 3.1.0

from featuremanagement-dotnet.