feat(Routes): voice state endpoint

[imnaiyar]

Please describe the changes this PR makes and why it should be merged:

If applicable, please reference Discord API Docs PRs or commits that influenced this PR:

• Document get voice state endpoints discord/discord-api-docs#7061

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
discord-api-types	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 15, 2024 11:58pm

[imnaiyar]

Also I'm not sure if we should rename GatewayVoiceState type (possibly to APIVoiceState ?) now that it is possible to get it over http

[vladfrangu]

Also I'm not sure if we should rename GatewayVoiceState type (possibly to APIVoiceState ?) now that it is possible to get it over http

Yes, and deprecating the gateway alias

[imnaiyar]

Also I'm not sure if we should rename GatewayVoiceState type (possibly to APIVoiceState ?) now that it is possible to get it over http

Yes, and deprecating the gateway alias

Did that if you wanna have a look

[almeidx]

Missing the REST types, which should be added to rest/voice.ts to match the Discord docs

The patch endpoint types are in rest/guild.ts, which should be moved to rest/voice.ts as well. Not sure if we'd have to add a re-export on the patch types in rest/guild.ts since users can import individual files too

[imnaiyar]

Missing the REST types, which should be added to rest/voice.ts to match the Discord docs

The patch endpoint types are in rest/guild.ts, which should be moved to rest/voice.ts as well. Not sure if we'd have to add a re-export on the patch types in rest/guild.ts since users can import individual files too

not re-exporting from guild.ts right now, we can wait for others to see what they want to do

[vladfrangu]

since users can import individual files too

No, they cannot. So moving exports from the right file is perfectly fine