QuoteCommand: Getting it working again #1033
Merged
Conversation
This file contains 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
Instead of trying to fetch a message with the ID of the application command (?) just to then use it to get to its channel, we can just use the channel on our interaction
New message IDs can be 19 characters long, and they may grow up to 2^64-1 (20 characters) in the future.
The plugin will actually throw `Error`s for a lot of failure states, which weren't caught before
bgianfo
approved these changes
Dec 19, 2023
|
Thanks! |
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.
With these patches,
/quoteseems to work again (on a testing repo of mine, link).I don't know the cause of #533 yet (an issue in the create-pull-request plugin repo points to missing authentication, link). Could someone with access to the public bot confirm that our issue is still valid?