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
If we add guards into the dependency graph, it would allow them to receive the same kwargs as dependencies as well, making them more convenient to use since they can opt to receive things such as query params, cookies and headers as needed, without having to go through the ASGIConnection.
Making the same data available in route handlers, dependencies and guards also makes for a better DX imo, since it's a bit more intuitive.
After looking into this - it will be both complex to do, and will probably degrade performance. I dont think we should proceed with this - the current design is sufficent IMO.
Originally discussed n #1116 (comment)
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: