Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: voice message support #67

Merged
merged 2 commits into from
Apr 20, 2023
Merged

feat: voice message support #67

merged 2 commits into from
Apr 20, 2023

Conversation

TTtie
Copy link
Member

@TTtie TTtie commented Apr 15, 2023

Ref: discord/discord-api-docs#6082

Will be marked as ready to review once the relevant API doc PR is merged.

@TTtie TTtie added type: enhancement New feature or request reason: Discord Issues or pull requests related to Discord's API changes scope: structures Issues or pull requests affecting the structure definitions labels Apr 15, 2023
@TTtie TTtie added this to the 0.2.0 milestone Apr 15, 2023
@TTtie TTtie self-assigned this Apr 15, 2023
While currently the docs specify it is a base64 byte array, it might be
more worthwhile to give the API consumer a raw string and let them deal
with it appropriately. Let alone this is probably a more future-proof
variant, as (although very unlikely) the format could change in the future.
@TTtie TTtie force-pushed the feat/voice-messages branch from 75adee9 to 8751701 Compare April 15, 2023 21:59
@TTtie TTtie marked this pull request as ready for review April 19, 2023 17:10
@TTtie TTtie merged commit 4159d0b into dev Apr 20, 2023
@TTtie TTtie deleted the feat/voice-messages branch April 20, 2023 09:46
TTtie added a commit that referenced this pull request Apr 20, 2023
* feat: voice message support

Ref: discord/discord-api-docs#6082

* keep the waveform as-is

While currently the docs specify it is a base64 byte array, it might be
more worthwhile to give the API consumer a raw string and let them deal
with it appropriately. Let alone this is probably a more future-proof
variant, as (although very unlikely) the format could change in the future.
TTtie added a commit that referenced this pull request May 11, 2023
* feat: voice message support

Ref: discord/discord-api-docs#6082

* keep the waveform as-is

While currently the docs specify it is a base64 byte array, it might be
more worthwhile to give the API consumer a raw string and let them deal
with it appropriately. Let alone this is probably a more future-proof
variant, as (although very unlikely) the format could change in the future.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
reason: Discord Issues or pull requests related to Discord's API changes scope: structures Issues or pull requests affecting the structure definitions type: enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant