-
-
Notifications
You must be signed in to change notification settings - Fork 332
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
Docs: Update usage/security/guards
chapter
#3356
Comments
Just to clarify this point, guards of HTTP routes receive a |
@peterschutt prepared a draft PR to update typing and docs. While working on this I looke a bit into the Alternatively, I could extend the documentation to elaborate that it is fine to access query and path parameters but that the request body may not be accessed by the guard. I'm learning about all of this on the fly, so how I handled it now for my project is, that I put "body guards" (pun intended) at the top of route handler function instead of in the route handler guard list. Maybe it's worth mentioning that in the docs just so newbies don't have to go through the same trial&error process as me :D what do you think? |
When you do |
Thansk @Alc-Alc that's already good to hear. |
Summary
Follow-up from discussion: https://github.com/orgs/litestar-org/discussions/3355
Suggesting changes to chapter: https://docs.litestar.dev/latest/usage/security/guards.html
Request
object as first argument, not anASGIConnection
. Needs correction throughout the chapter.Note
While we are open for sponsoring on GitHub Sponsors and
OpenCollective, we also utilize Polar.sh to engage in pledge-based sponsorship.
Check out all issues funded or available for funding on our Polar.sh dashboard
The text was updated successfully, but these errors were encountered: