You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The specific use case of having decorator for logging in is probably not a problem in most scenarios:
If used internally, the aversion to accessibility is likely lower.
If used publicly, this problem is irrelevant.
Also, the endpoints themselves can be secured, and there are ACLs that are configurable in the app when this blueprint is registered. Though if the view doesn't load the endpoints, but is still accessible, the user experience is very much less than ideal.
There are still other decorator scenarios that may crop up though, so I'll leave this open for now.
There might be a way around this, but there is currently no way to enforce login decorators, etc... since you don't have direct access to the views.
The text was updated successfully, but these errors were encountered: