Docs: Convert usage example to OpenAPI v3 spec #792
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
melroy89
force-pushed
the
update_readme_usage_to_openapiv3
branch
2 times, most recently
from
a946973 to
5104889
Compare
mcollina
requested changes
Mar 20, 2024
Ah yes. Sorry about that. I needed to force push some changes with another editor. Since vscode tried to auto format this whole Readme markdown file. Lol |
|
Indentation is fixed, please review again. |
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.
Usage example updated to OpenAPI v3 specification. This is tested and validated.
Fixes: #790
Troubles reviewing?
GitHub Tip of the day, check the "Hide whitespaces" in the review window:
Checklist
npm run testandnpm run benchmarkand the Code of conduct