Style RefreshToken URL as <code> in the OAuthFlow #2397
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
…on like Token URL is styled, for consistency in rendering.
AlexVarchuk
approved these changes
Aug 31, 2023
|
Hi @ckszabi, thank you for the contribution 🙌 |
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.
Represent refreshToken URL in a similar fashion like Token URL is styled, for consistency in rendering.
What/Why/How?
When an OAuth security scheme definition is rendered the refreshToken URL is presented as plain text, but it should be a (non-clickable) URL, rendered via
<code>tag, as the tokenURL is rendered.One line of template is changed
Reference
Tests
Screenshots (optional)
the wrong rendering:
better rendering:
Check yourself