Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[FR]: Support path-based $refs when resolving OpenAPI Specs
See original GitHub issueIs your feature request related to a problem? Please describe.
I’d like to use this on OpenAPI Specs that use the $ref feature to refer to definitions from other files, such that large APIs can be split into multiple files for reuse/readability purposes.
Presently, this library only supports $refs within the same file.
Describe the solution you’d like
Ability to use multi-file OpenAPI specs, since I’m trying to making them with https://stoplight.io/studio
Describe alternatives you’ve considered
I wonder if there are any OpenAPI tools that can rewrite a spec that uses path based $refs such that all the content gets imported into 1 file under the “components” key, for the benefit of tools that aren’t designed to work with multi-file OpenAPI specifications such as this one.
Additional context Add any other context or screenshots about the feature request here.
- Related reading about Refs: https://swagger.io/docs/specification/using-ref/
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:5
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Noticed today that the latest https://www.npmjs.com/package/swagger-parser might work better than
swagger-cli, since it’s compatible with external files, but unlike swagger-cli, supports working with circular references (which was necessary for working with recursive data types)Workaround obtained via my coworker:
swagger-clistitched together my files, e.g.https://www.npmjs.com/package/swagger-cli