fix(GuildAuditLog): Assert target
to null upon not finding invite codes
#6171
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:
Hi there!
Upon running
<Guild>.fetchAuditLogs({ type })
wheretype
is 40 (INVITE_CREATE
), 41 (INVITE_UPDATE
) or 42 (INVITE_DELETE
), there is a possibility thattarget
on the returnedGuildAuditLogsEntry
will beundefined
.One case where this is easily reproducible is by simply creating and then deleting an invite and then running
<Guild>.fetchAuditLogs({ type: 40 })
.I've simply added the nullish coalescing operator after that check to ensure that if an invite code cannot be found, it will default to
null
and notundefined
.Status and versioning classification: