feat(Routes): add missing OAuth2 routes #218
Merged
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
|
I guess one could also consider this chore rather than feat, dealers choice ig. |
vladfrangu
changed the title
vladfrangu
changed the title
vladfrangu
approved these changes
Oct 9, 2021
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:
The OAuth2 token flow routes are currently only available in
OAuth2Routes, but these are already prefixed with the API base, which makes them inconsistent with all the other route helpers. This PR adds the OAuth2 token flow routes to the mainRoutesobject in a consistent format with all other routes.This PR does not remove them from
OAuth2Routes, to ensure that this is a non-breaking change.Reference Discord API Docs PRs or commits:
https://discord.com/developers/docs/topics/oauth2