feat: expose conversation handle to plugins#134
Merged
KnorpelSenf merged 8 commits intomainfrom Apr 17, 2025
Merged
Conversation
OfficialCodinary
approved these changes
Apr 17, 2025
OfficialCodinary
left a comment
There was a problem hiding this comment.
Tested in production, No bugs in a long run.
KnorpelSenf
added a commit
to grammyjs/grammY
that referenced
this pull request
Apr 30, 2025
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
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.
The
pluginsoption allows plugins to be installed inside a conversation, andexternalallows the conversation to read the session data. It was pointed out in https://t.me/grammyjs/291998 that it is currently impossible to access the session data from inside a plugin.This PQ introduces a plugins option that has access to the conversation handle. That way, the following code becomes possible.