-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ticket system #1
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You seem obsessed with _names, what's up with that? Should I be too?
Reformat to 80 columns. Fix imports. Fix db init. Use `util.discord.format` for manual mentions. Move schema definition inline. Copied `Enum` definitions into db. Reduced error level for non-existent guild config.
`pager` no longer expects vararg list. `pager` uses `ReactionMonitor` for reaction handling. Add `_all_reaction` to `pager` for displaying all pages.
Add `Expired` to `TicketStatus` db enum. Remove manual quoting from condition formatting.
Store and expect kv config snowflakes as strings.
Remove extraneous `perm_check`. Move comprehension loading/unloading to usual loops.
Use cancel reaction instead of `c` response to cancel.
Clean up `resolve_ticket`. Add `tickets append` sub-command. Generally clean up commands.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have a code path for when an audit log entry originates from the bot itself?
P.S. There's a number of comments that describe things that are syntactically obvious from the code that follows immediately.
Implements a Mod Ticket plugin as specified.
TODO