Skip to content

docs: say aiogram error handlers get their own child container #718

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
Oct 17, 2026
Merged

docs: say aiogram error handlers get their own child container #718

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
6 changes: 6 additions & 0 deletions docs/integrations/aiogram.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,6 +93,12 @@ The integration creates one `Scope.REQUEST` child container per update. Its midd
child is closed with `close_async()` after the handler returns or raises, so REQUEST-scoped
finalizers may be async or sync. Resolution itself is synchronous, as everywhere in modern-di.

An error handler on `dispatcher.errors` runs after that child is closed, so the middleware is also
an outer middleware there and builds the error handler a child of its own, bound to the failing
update and its event. REQUEST-scoped instances in it are new ones, not the failing handler's. Before
modern-di-aiogram 4.3.4, an `@inject` error handler that resolved a REQUEST-scoped dependency raised
`ContainerClosedError` instead.

There is no `Scope.SESSION` for aiogram: each Telegram update is handled
independently; there's no persistent per-chat/per-user connection comparable
to a WebSocket. See [the scope hierarchy](../providers/scopes.md#what-each-scope-is-for).
Expand Down
Loading