Problems with OpenAPI yaml files
See original GitHub issueProblems on version 0.5.1 and 0.5.0, when working with openapi yaml files.
I have used one of the openapi examples. File can be seen here
I’m getting errors such as:
String is not a URI: [UriError]: Scheme is missing: {scheme: "", authority: "", path: "", query: "", fragment: "/components/schemas/Pets"}
This is happening on each line with a reference for schema starting with a #
.
$ref: "#/components/schemas/Pets"
It appears to me that this version does not honor #
, while in 0.4.1 I didn’t have these problems.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:13
- Comments:14 (2 by maintainers)
Top Results From Across the Web
Performance issue with openapi yaml files : IDEA-254097
yaml file is open even after analysis of file has finished. Opening two such files consumes same amount of cpu (one full core)....
Read more >Support YAML files for OpenAPI Specs (#330583) - GitLab.org
Problem. According to the OpenAPI specification a openapi definition can be defined in yaml or json. However API fuzzing only accepts a json...
Read more >Keeping OpenAPI DRY and Portable - Stoplight Blog
When you ask why, you'll often hear a terrible tale of 10,000 line YAML files, repeated content, and never-ending git conflicts. Problems ......
Read more >Redocly OpenAPI structure error. Property `openapi` is not ...
yaml Problem : Property `openapi` is not expected here. File: /Users/xx/Desktop/Projects/api-docs/openapi/paths/kpi-documentation.yaml ...
Read more >Why does multi openAPI yaml not work? Spring Boot
I have the following problem. ... The OpenAPI.yaml serves as the top-level yaml file. ... Does anyone have a solution for this problem?...
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
The fix for this will be available in the next release
Any ETA on when that release is going to happen?