docs: note that lazy sessions and multi sessions are mutually exclusive#1292
Open
Dramex wants to merge 2 commits into
Open
docs: note that lazy sessions and multi sessions are mutually exclusive#1292Dramex wants to merge 2 commits into
Dramex wants to merge 2 commits into
Conversation
grammyjs#936 points out that the docs leave readers with the impression that the lazy-session implementation has feature parity with the strict session middleware, including multi-session support. It does not — the maintainer confirmed on the thread that lazy sessions do not accept a `type: "multi"` configuration and there is no workaround. Add a warning callout at the top of the Lazy Sessions section stating the two are mutually exclusive and pointing users who need multi-session namespaces back to the default `session` middleware with `type: "multi"`. Closes grammyjs#936.
KnorpelSenf
reviewed
Jun 14, 2026
Comment on lines
+644
to
+648
| ::: warning Lazy sessions do not support multi sessions | ||
| Lazy sessions and [multi sessions](#multi-sessions) are mutually exclusive. | ||
| `lazySession` is a separate implementation of the session middleware, and it does not accept the `type: "multi"` configuration that the strict `session` middleware does. | ||
| If you need several independent session namespaces (for example, one per chat and one per user), use the default strict `session` middleware with `type: "multi"`. | ||
| ::: |
Member
There was a problem hiding this comment.
This takes up a bit too much space IMO. What do you think of this?
Suggested change
| ::: warning Lazy sessions do not support multi sessions | |
| Lazy sessions and [multi sessions](#multi-sessions) are mutually exclusive. | |
| `lazySession` is a separate implementation of the session middleware, and it does not accept the `type: "multi"` configuration that the strict `session` middleware does. | |
| If you need several independent session namespaces (for example, one per chat and one per user), use the default strict `session` middleware with `type: "multi"`. | |
| ::: | |
| > Note that the lazy session implementation has no concept of multi sessions. | |
| > Stick with the regular session implementation if you want to use its [multi sessions](#multi-sessions). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #936.
The Lazy Sessions section reads as if the middleware has feature parity with strict sessions, but in fact `lazySession` does not accept a `type: "multi"` configuration — on the thread the maintainer confirmed this and that there is no workaround. Until this is documented, users assume they can combine the two and are surprised when it fails.
Adds a short warning callout at the top of the Lazy Sessions section stating the constraint and pointing readers who need multiple session namespaces back to the default strict `session` middleware with `type: "multi"`.
No code changes — docs only, English-language only for now (translations can follow per the usual process).