Skip to content

docs: note fetch_request_container in the 2.0.0 release notes #2

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.

Sign up for GitHub

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
lesnik512 merged 1 commit into from
Jul 2, 2026
Merged

docs: note fetch_request_container in the 2.0.0 release notes #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
3 changes: 2 additions & 1 deletion planning/releases/2.0.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,8 @@ dependencies.
via `web.WebSocketResponse().can_prepare(request).ok` and opens a
`Scope.REQUEST` child container for each HTTP request or a `Scope.SESSION`
child for each WebSocket connection, injecting the connection as context and
closing the child when the connection ends. Per-message work inside a
closing the child when the connection ends. A handler reads its child
container with `fetch_request_container(request)`. Per-message work inside a
WebSocket handler can open a nested `Scope.REQUEST` child of the SESSION
container.
- **`FromDI` + `@inject`.** Mark a handler parameter with
Expand Down