[ext.pages] Compatibility patch for ext.bridge #1288
Merged
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.
Summary
This adds compatibility for
ext.pages
when used withext.bridge
by allowing aBridgeContext
object to be passed instead of anInteraction
inPaginator.respond().
If a
BridgeContext
object is passed,Paginator.respond()
uses theext.bridge
methods to send the paginated message instead of theInteraction
methods.Due to
BridgeContext.respond()
not recognizing theephemeral
keyword, paginators passing aBridgeContext
object cannot be ephemeral and that parameter will be ignored.Checklist
type: ignore
comments were used, a comment is also left explaining why