Skip to content

fix(security): request variable is only available at the resource level #1470

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

Merged
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion core/security.md
Original file line number Diff line number Diff line change
Expand Up @@ -118,7 +118,7 @@ Available variables are:

* `user`: the current logged in object, if any
* `object`: the current resource, or collection of resources for collection operations
* `request`: the current request
* `request` (only at the resource level): the current request

Access control checks in the `security` attribute are always executed before the [denormalization step](serialization.md).
It means than for `PUT` or `PATCH` requests, `object` doesn't contain the value submitted by the user, but values currently stored in [the persistence layer](data-persisters.md).
Expand Down