Getting "incorrectly formatted" errors for swagger file that works with previous version
See original GitHub issueUsing "sbt-guardrail" % "0.44.0"
in a project causes
Spec file service.yml is incorrectly formatted.
Reverting to "sbt-guardrail" % "0.43.0"
works without errors.
It would be helpful if I could know why the parser is failing so I could fix the swagger file if it’s incorrect or report a more useful error message 😄. If you point me in the right direction on this I’d gladly work on a code fix!
Issue Analytics
- State:
- Created 5 years ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
Getting "incorrectly formatted" errors for swagger file ... - GitHub
Spec file service.yml is incorrectly formatted. Reverting to "sbt-guardrail" % "0.43.0" works without errors. It would be helpful if I could ...
Read more >Fix Swagger Validator errors in Power Platform connectors
The Swagger Validator tool validates the connector files you submit in the GitHub open-source repository and the ISV portal. It checks the ...
Read more >OpenAPI Specification - Version 3.0.3 - Swagger
Typically, .patch versions address errors in this document, not the feature set. Tooling which supports OAS 3.0 SHOULD be compatible with all OAS...
Read more >Troubleshooting issues when using Swagger as a REST API ...
To view an earlier version, select the version from the Product ... Syntax errors in the index.html file, located in /swagger/dist/ folder.
Read more >Integrated Swagger UI throws error on valid OpenAPI spec file
Summary When opening a valid OpenAPI JSON file from the Repository / Files section, an error message is displayed saying:
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ve gotten a lot of mileage out of https://mermade.org.uk/openapi-converter for converting my specifications to 3.0, but from what I can tell (and you just confirmed) there’s some oddity in sbt directly. Asking in the sbt gitter channel. Thanks for helping track this down!
@griffio Thanks for confirming, and thanks again for finding the fix!
@natevecc Closing this now, feel free to reopen if upgrading to 0.44.0.1+ didn’t solve the issue for you