/role fails to look up roles with logical operators when using autocomplete #218
Labels
No labels
beginner friendly
bug
chore
documentation
duplicate
feature
help wanted
invalid
needs-triage
question
size/L
size/M
size/S
size/XL
size/XS
urgent
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
ScottyLabs/dalmatian#218
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Overall Objective
The
/roleslash command fails to look up users when selecting a role via the autocomplete dropdown if that role name contains a logical operator such asor/and(e.g.Boss and McGill).To reproduce, run
/role membersin the CMU Class of 2030+ server and typeBoss. Click on the autocompleteBoss and McGill. The role command returns "Role not found: Boss", when it should have returned all users with theBoss and McGillrole.Suggested Approach
For now, wrap quotes around any autocompleted role's
value. You'll edit this code.Note that this doesn't fix the error if the user types out the roles, just single role autocomplete (we'll figure out a way to fix the others later)