Guards take a Request object as first argument, not an ASGIConnection. Needs correction throughout the chapter.

Just to clarify this point, guards of HTTP routes receive a Request object. However, guards are also called on ASGI and websocket routes, and receive the relevant connection type in those cases.

@peterschutt prepared a draft PR to update typing and docs.

While working on this I looke a bit into the Request methods, e.g., how json() works. You mentioned in the discussion on this topic that the asgi messages can only be consumed once. So, I'm wondering now how helpful this type hin adjustment actually is - or if "hiding" the type from the user is beneficial for preventing wrong usage.

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?

asgi messages can only be consumed once.

When you do .json or .body on the request instance, it does consume the message body, but it is then cached, further calls to these methods use the cached value. I do not think Peter meant this to be a blanket statement saying "read it only once". It usually is not required to read body in guards, but there is nothing "wrong" with doing this, IMO ofc.

Thansk @Alc-Alc that's already good to hear.