-
Notifications
You must be signed in to change notification settings - Fork 131
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
FullHistory #623
FullHistory #623
Conversation
took a more configurable way for DevLeoko#427 where you can exclude any punishment type if you so choose
These are changes based on the comments of the pull request
Added a lime to conform to style, and adjusted the javadoc
That makes sense, I made the changes based on what I interpreted of what you said. |
I condensed the new method i added wouldnt let me add the ternary operator in the getpunishments And i got rid of the temp variable because I didn't like it
core/src/main/java/me/leoko/advancedban/manager/PunishmentManager.java
Outdated
Show resolved
Hide resolved
core/src/main/java/me/leoko/advancedban/manager/PunishmentManager.java
Outdated
Show resolved
Hide resolved
Feel free to also message me on Discord if you have questions or want to chat about the comments. |
These are the asked changes, however it cannot stay this way because ambiguous callls
Removing ambiguous calls
if (!Universal.get().hasPerms(input.getSender(), "ab.history")) { | ||
MessageManager.sendMessage(input.getSender(), "General.NoPerms", true); | ||
return; | ||
} |
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.
I don't think that you need to perform a permission check here as the permission for the command is specified a few lines above
Didnt see the previous perm check
Thanks for adding this feature |
took a more configurable way for #427 where you can exclude any punishment type if you so choose