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
Splitting spec files still throws schema and file not found errors (json_schema exceptions) but still works with Connexion <= 3.0.2 #1909
Comments
Actually, when I test with 3.04 or 3.03, I have a different issue with specs being invalid:
3.0.2 seems to be the most stable for my needs and works perfectly, but it would be great to run the latest and greatest. |
eharvey71
changed the title
Spitting spec files still throws schema and file not found errors (json_schema exceptions) but still works with Connexion <= 3.0.4
Spitting spec files still throws schema and file not found errors (json_schema exceptions) but still works with Connexion <= 3.0.2
Apr 9, 2024
This was referenced Apr 9, 2024
eharvey71
changed the title
Spitting spec files still throws schema and file not found errors (json_schema exceptions) but still works with Connexion <= 3.0.2
Splitting spec files still throws schema and file not found errors (json_schema exceptions) but still works with Connexion <= 3.0.2
May 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have my yml files divided into subdirectories for paths, parameters, schemas, etc. This worked fine (and still works fine) on Connexion
3.0.43.0.2.Connexion
3.0.5 and 3.0.63.0.3 - 3.0.6 are still throwing errors. The prior fixes for $refs don't seem to have fixed issues. I thought this was just a Windows filesystem or jsonschema issue but it's happening all over - in my MacOS, Windows and docker container deployments running Debian.If I downgrade to Connexion
3.0.43.0.2 or prior, the error goes away, in all cases.I am working with a separate swagger UI deployment, so I can do customizations.
In my configuration, I'm initializing my app like this:
Paths are like this to specs, where my swagger.yml contains $refs to the proper paths of each of the divided spec files:
swagger.yml sample:
Full contents of error:
Output of the commands:
The text was updated successfully, but these errors were encountered: