Support limiting users to one reaction #60
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.
Describe the PR changes
limit_to_one
column tomessages
tableon_raw_reaction_add()
if a user has already selected a reaction (and the message is marked as unique), if so the reaction is removed, which causeson_raw_reaction_remove()
to trigger, leading to the removal of the roleWhat could be better
Changing the "unique" status with the
rl!edit
command. The problem here would be iterating through existing reactions and arbitrarily removing all of them but one per user. I just think it's easier for admins to delete the message and recreate it.Known Issues
If you select multiple reactions really fast all of them will get removed. This is due to the API latency, cannot circumvent this.
Closes #44