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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: allow for single example #1705
base: next
Are you sure you want to change the base?
feat: allow for single example #1705
Changes from all commits
2a5f6a5
8a9997f
3055adb
77bdb63
a5ca9ae
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check failure on line 104 in src/AnnotationsReader/ExtendedAnnotationsReader.ts
GitHub Actions / Test (ubuntu-latest)
Check failure on line 104 in src/AnnotationsReader/ExtendedAnnotationsReader.ts
GitHub Actions / Test (windows-latest)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this actually better? The old format is more predictable and easier to process since it's consistent.
Can you send a link to json schema spec about this tag?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure, Examples does not pass validation under openapi spec, while
example
does.Here is the spec on examples: https://json-schema.org/draft/2020-12/json-schema-validation.html#name-examples it says nothing about
example
There are instances of example being used in open api specs https://swagger.io/specification/ which is not a 1:1 with json schema.
There is a flag:
discriminatorType: 'open-api'
in the config that could be used ?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, then I would say this is an issue to raise with openapi and swagger. I don't really want to diverge from JSON schema.
I was somewhat reluctant to add the discriminatorType flag and would not like to support too many flags.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense.
the open api flag seems to be already there
You might close this PR if you wish, I don't think there is anymore to be done here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about we add one flag for openapi support and use that for all openapi related features?