-
-
Notifications
You must be signed in to change notification settings - Fork 89
/audit crashes if more than 10 cases #335
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
Comments
Can I have this one please, It may take a little while, and you may get lots of help requests :) (Didn't realise I could self-Assign!) |
Request help as many times as you can, as long as you do your best we're happy! |
You can because you are now "Member of Together-Java/contributors" 🎉 |
Zabu, I know you like to tell me not to overcomplicate, however, I have an alternate suggestion for this, and feel it would look better from a design point of view and we can use the embed fields to our benefit, Using 1 - 3 embeds per /audit command, I suggest we stick to the summary first, then the embed something like this : I just feel it would look a lot tidier. See discord for more details :D |
I see your point but I dislike it. The embeds are really helpful to gain an overview since you can add pictures, color and align things. That said, I am open for suggestions but lets create another issue for this if u want to change the UI/UX and keep this issue/PR just about fixing the bug (by adding pagination). |
@Budbomber Ur coming along well, need help? Should someone take over? |
Overview
When using
/audit
on a user who has more than 10 reported cases, the command crashes with an exception:Possible solutions
The cause is quite clear, it attempts to display all cases and then fails cause there are too many. Obviously, this case is not supposed to be triggered really often and its not thaaat big of a deal but we should find at least a solution.
Dyno has pagination support to solve this, so there is an optional option on the command to show page 2, page 3, ... Would probably be a clean solution to do it that way ourselves as well.
The text was updated successfully, but these errors were encountered: