To create an authorization filter based on resources in ASP.NET Core, I need to prescribe a requirement, a handler for it, register it. And all just to call it in the action controller? What's the point of this? What is the difference from a simple call containing this test method? If he had pre-loaded the resource model before calling the controller action, it would be justified, but in all manuals the check is called from within the action.
|