feat: api v10 #331
Merged
feat: api v10 #331
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
|
Awaiting replies on
|
vladfrangu
force-pushed
the
feat/api/v10
branch
2 times, most recently
from
a10e45e
to
250af90
Compare
vladfrangu
force-pushed
the
feat/api/v10
branch
from
250af90
to
2dc9a7b
Compare
|
I think we're ready for v10 types 馃帀 |
kyranet
approved these changes
Feb 15, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
Closes #330 (too fast 馃様)
If you want to help out with the changes in v10 (read discord/discord-api-docs#4510), feel free to PR to the branch on my fork.
If applicable, please reference Discord API Docs PRs or commits that influenced this PR: