fix: spec example fix #2
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
Changes: - modify examples in Operation Object
2 tasks
Changes: - modify example to match the correct format of the spec - add new sub-heading to denote what kind of OAuth Flow is - applied suggestion from: asyncapi#1059 (comment)
AnimeshKumar923
force-pushed
the
spec-examples-fix
branch
from
46dd3ef
to
b0d36e7
Compare
AnimeshKumar923
force-pushed
the
spec-examples-fix
branch
from
68ad80e
to
e1b0e65
Compare
AnimeshKumar923
merged commit 9347567
into
embedded-examples-validation
14 of 23 checks passed
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.
This PR contains fixes that will be applied in the
embedded-examples-validationonce we've figured out the necessary overall spec changes.