FeatureGate filter question about featuremanagement-dotnet HOT 3 OPEN

It makes more sense to use resourse filter for the feature gate scenario. I will take a look at your PR and learn how to implement a filter attribute.

from featuremanagement-dotnet.

Hi, @WeihanLi

The Feature Management ASP.NET library provides FeatureGateAttribute and an extension method of AspNetCore.MVC.FilterCollection called AddForFeature which will add a FeatureGatedAsyncActionFilter.

Here what you pointed out is the FeatureGateAttribute which is built on ActionFilterAttribute.

The ASP.NET Core includes some built-in filter attributes:
ActionFilterAttribute
ExceptionFilterAttribute
ResultFilterAttribute
FormatFilterAttribute
ServiceFilterAttribute
TypeFilterAttribute

There is no built-in filter attributes for resource filter and authorization filter.

The way to use FeatureGateAttribute is to place it on MVC controllers, controller actions, or Razor pages.
The FeatureGateAttribute implements the OnActionExecutionAsync method which will [run before any of the action's filters]
(https://learn.microsoft.com/en-us/aspnet/core/mvc/controllers/filters?view=aspnetcore-8.0#controller-level-filters).

According to the diagram, it seems like the stage of "Model Binding" can be skipped. I don't think using AuthorizationFilter is sensible.

Therefore, it brings two questions:

1. Should the stage of "Model Binding" be skipped?
2. How to implement an Attribute for resource filter?

I need to do more investigation.

from featuremanagement-dotnet.

Thanks for the reply

1. I think it should be skipped if the feature is not enabled, it seems no need to go through the model binding
2. Need to inherit the Attribute to make it work as an attribute and implement the IResourceFilter/IAuthorizationFilter or/and the async interface ...

I tried to propose an AuthorizationFilterAttribute like the ActionFilterAttribute, but seemed the asp.net team does not want to include it in the framework dotnet/aspnetcore#40542

from featuremanagement-dotnet.