Skip to content

builder.Services.AddFeatureManagement() with configuration section does not work since v3.0.0 #308

@FredericVaugeoisFlo

Description

@FredericVaugeoisFlo

I know that there was a breaking change in v3.0.0 created by #261, but I feel like that should not affect the use case of targeting the configuration section to use in the appsettings.json file.

For example, with this configuration file:

{
  "Logging": {
    "LogLevel": {
      "Default": "Information",
      "Microsoft.AspNetCore": "Warning"
    }
  },
  "FeatureFlags": {
    "PushFeatureEnabled": true,
    "PutFeatureEnabled": true
  }
}

and this program.cs line:

builder.Services.AddFeatureManagement(builder.Configuration.GetSection("FeatureFlags"));

var app = builder.Build();

the feature manager does not load our feature flags like it did in 2.6.0. If we're not allowed to set our own configuration section, it should no be a possible parameter or at least raise a deprecated warning

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions