-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
update GuildAuditLogs for MESSAGE_DELETE and fixed extras #1464
Conversation
Can you try to make some documentation for extras? 🤢 |
src/structures/GuildAuditLogs.js
Outdated
@@ -4,6 +4,7 @@ const Snowflake = require('../util/Snowflake'); | |||
const Targets = { | |||
GUILD: 'GUILD', | |||
CHANNEL: 'CHANNEL', | |||
MESSAGE: 'MESSAGE', | |||
USER: 'USER', | |||
ROLE: 'ROLE', | |||
INVITE: 'INVITE', |
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.
can you move message to the bottom so they are in order of type mod 10
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.
Ah, that's the way they are sorted.
* update GuildAuditLogs for MESSAGE_DELETE and fixed extras * correct oder of targets
…1464) * update GuildAuditLogs for MESSAGE_DELETE and fixed extras * correct oder of targets
…1464) * update GuildAuditLogs for MESSAGE_DELETE and fixed extras * correct oder of targets
…1464) * update GuildAuditLogs for MESSAGE_DELETE and fixed extras * correct oder of targets
Please describe the changes this PR makes and why it should be merged:
I am not sure whether
target < 80
is correct, it just seemed logical to me.this.options
should bedata.options
Shouldn't at least GuildAudLogs.build be private, if not all methods?
Semantic versioning classification: