feat/fix(GuildAuditLogs): handle new event types #3602
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please describe the changes this PR makes and why it should be merged:
This PR builds on top of #3584 handling the data of the new event types.
Integration
was added toAuditLogTargetType
,AuditLogEntryTarget
and cached in the parentGuildAuditLogs
object like webhooks.The previously added event types were added to
GuildAuditLogs.actionType
to properly reflect the type of their action.GuildAuditLogsEntry#extra
now properly holds relevant data for the new types.GuildAuditLogsEntry#target
does no longer create a partial user with the idnull
for event types that do not provide a user id although targetting users (MEMBER_DISCONNECT, etc.)Status
Semantic versioning classification: