feat(APIVoiceChannel): support text in voice, properties last_message_id
and rate_limit_per_user
#544
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:
Adds the missing properties to
APIVoiceChannel
(last_message_id
andrate_limit_per_user
) which were now included in the voice channel payload, with the "Text In Voice" feature, making it a text-based channel.But to make it more dynamic takes
APIVoiceChannel
as a base with the common properties in the voice channel types (Now it will beAPIVoiceChannelBase
) because a guild contains two types of voice channels:GUILD_VOICE
andGUILD_STAGE_VOICE
.So, this PR:
Creates a type called
APIGuildStageVoiceChannel
, which covers the channel with theGUILD_STAGE_VOICE
type.Adds
rate_limit_per_user
property toAPITextBasedChannel
(it already had thelast_message_id
property).Creates an interface called
APIGuildVoiceChannel
, which covers the channel with theGUILD_VOICE
type, usingAPIVoiceChannelBase
andAPITextBasedChannel
, adding thevideo_quality_mode
property.If applicable, please reference Discord API Docs PRs or commits that influenced this PR: