. NETCORE sets the API post mode, which can accept parameters directly in parentheses

as everyone knows , stay .NetCore WebApi in ,Post The way of api When receiving parameters, it cannot be like Get those , Write the accepted parameters directly into the brackets after the method , Such as ：

[HttpPost]
public string GetAreaGroupList(string id){
   return id;
}

This is because api Default inference rules , Binding source reasoning , With the help of these rules , There is no need to manually identify the binding source by applying attributes to the operation parameters , Several of these rules are
　　[FromBody] Infer complex type parameters . However, it does not apply to any complex built-in type with special meaning , Such as IFormCollection and CancellationToken.
　　[FromForm] in the light of IFormFile and IFormFileCollection Type of operation parameters .
　　[FromRoute] Infer the name of any operation parameter that matches the parameters in the routing template .
　　[FromQuery] Infer from any other operating parameters .

But sometimes I don't want to write so complicated api, Just want to write and accept parameters one by one in parentheses , Then just turn off the default reasoning rules .

.NetCore disable api Rules of reasoning , stay Startup.cs ConfigureServices writes ：

services.AddControllers(cfg => { cfg.Filters.Add(new ExceptionHandleAttribute()); })
                .ConfigureApiBehaviorOptions(options =>
            {
                //options.SuppressConsumesConstraintForFormFileParameters = true;// Disable when [FromForm] Property annotation , Reasoning multipart/form-data Request content type 
                options.SuppressInferBindingSourcesForParameters = true;// Ban api The rules of reasoning , This supports post The method accepts parameters and directly in parentheses model Parameters of the way 
            });