-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reorder initializing the view #4006
Conversation
Determining the version and performing content negotiation should be done before ensuring the permission of the request. The reason is that these information can be used in handling the exceptions. For example different versions may return different error scheme. Also, the rendering class can be used to determine how to exception handler response should be rendered.
At a first glance this looks like a small valid enhancement. Anyone else care to review/comment? |
Seems valid too. Need to think about the side effects related to security of performing computations before permissions checks. |
Can't think of any atm, since it's just content neg and determining correct version. |
Consideration: Any point we push permissions later, there are more opportunities to consume resources etc. Having said that I don't think I've any great problems with this change. |
I can see how useful it might be to have access to |
I'm 👍 with this pull request. |
Ok, let's get this moving. |
nice work, thanks :) |
Thank you |
Description
Determining the version and performing content negotiation should be done before ensuring the permission of the request. The reason is that these information can be used in handling the exceptions. For example different versions may return different error scheme. Also, the rendering class can be used to determine how to exception handler response should be rendered.