-
-
Notifications
You must be signed in to change notification settings - Fork 211
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
Issue with some $ref #183
Comments
@cdimascio I found the explanation : it is an issue of json-schema-ref-parser As explained here ( APIDevTools/json-schema-ref-parser#101 (comment) ) , we must use :
instead of
If I changed that in your |
cdimascio
added a commit
that referenced
this issue
Dec 24, 2019
Fix $ref issue with special characters (#183)
@jy95, merged your PR. the new option for the json schema ref parser is available in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I saw it is possible to split specifications into multiple files.
I tried to split mine ( from my master branch ) into a separate branch : the "main file" and the rest
( I didn't forget to escape special characters like explained in Swagger : https://swagger.io/docs/specification/using-ref/ or in this old open api v2 tutorial )
To test if the specifications are correct (and work as expected), I used the following commands explained in my readme :
The validator seems to accept the specifications :
However, some endpoints like /auth/login and /auth/register no longer work and send me an error of this type :
Any idea what caused this problem? The path seems to be recognized in other tools ( like the OpenAPI (Swagger) Editor extension in Visual Studio Code )
Thanks
The text was updated successfully, but these errors were encountered: