-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
SwaggerEditor@next - Reference for Parameters Failing #3760
Comments
Hi @ForbiddenEra, Closing as duplicate of #3791 where fix have already been provided, and issue will be remedied completely after the next release. |
Linting was producing false positives when Parameter Object was referenced via Reference Object. Fix was provided by ApiDOM@0.67.1. This commit also contain updates to number of development dependencies. Refs #3760 Refs #3791 Refs #3770 Refs https://github.com/swagger-api/apidom/releases/tag/v0.67.1 Closes #3846 Closes #3844 Closes #3843
Linting was producing false positives when Parameter Object was referenced via Reference Object. Fix was provided by ApiDOM@0.67.1. This commit also contain updates to number of development dependencies. Refs #3760 Refs #3791 Refs #3770 Refs https://github.com/swagger-api/apidom/releases/tag/v0.67.1 Closes #3846 Closes #3844 Closes #3843
Thanks; I was going to say I didn't see the duplicate issue but as I was typing that I noticed 3791 > 3760, so I guess I was first and perhaps not a total duping failure on my part ;) |
@ForbiddenEra not at all, duplicates as normal part of SDLC. THanks for reporting this. |
Q&A (please complete the following information)
Content & configuration
yaml is from example at https://swagger.io/docs/specification/describing-parameters/
Describe the bug you're encountering
I get
Parameter Object must contain one of the following fields: content, schema
- setting the definition version toswagger: '2.0'
or using the non-next version of the editor causes zero error.To reproduce...
Steps to reproduce the behavior:
Expected behavior
No error. Again, this doesn't happen on editor-next when using
swagger: '2.0'
or on the previous version of the editor even when usingopenapi: 3.0.3
The text was updated successfully, but these errors were encountered: