This repository has been archived by the owner on Jan 25, 2020. It is now read-only.
Refactor rules-message and purge-reaction fetching #1
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
The IDs are now an array of [channel_id, message_id], both ints, and are fetched once on startup.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 IDs are now an array of [channel_id, message_id], both ints, and are fetched once on startup. The channel ID is also an int for consistency. Requiring explicit channel IDs allows
t!purgeto be run from any channel, not just the one the purge reactions message was sent, and also allows properly fetching the rule reminder message.