feat(APIGuildScheduledEvent): add more precise types for stage instance/voice/external events #278
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 turns
APIGuildScheduledEvent
into a union ofAPIStageInstanceGuildScheduledEvent
,APIVoiceGuildScheduledEvent
, andAPIExternalGuildScheduledEvent
, which each has more precise types according to the docs.This PR also fixes a bug as previously
APIGuildScheduledEvent#entity_metadata
was not nullable, even though it should be.Reference Discord API Docs PRs or commits:
Technically,
entity_metadata
isn’t alwaysnull
for stage instance events (see discord/discord-api-docs#4198) and contains aspeaker_ids
field, but that isn’t documented anymore.From this comment:
I decided to make
entity_metadata
null
for stage instance events as that is what the documentation states.