Fixing issue #9 and any $ref related issue in the input openapi spec.
This PR basically replaces js-yaml by swagger-parser, which can load a openapi yaml spec, deference $refs and outputs json schema, as js-yaml used to do.
Issue
9
Change Type
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
Checklist
[x] The build is passing
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
Version
Using Semver versioning, what version number should be bumped for this change?
[x] Major
[ ] Minor
[ ] Patch
As the change require the getSchemas function to be async the exported function need to be async too, leading to a breaking api change :neutral_face:
JoeScho
commented
4 years ago
Background
Fixing issue #9 and any
$refrelated issue in the input openapi spec.This PR basically replaces
js-yamlbyswagger-parser, which can load a openapi yaml spec, deference$refs and outputs json schema, asjs-yamlused to do.Issue
9
Change Type
Checklist
Version
Using Semver versioning, what version number should be bumped for this change?
As the change require the
getSchemasfunction to be async the exported function need to be async too, leading to a breaking api change :neutral_face: