Jeremy Whitlock
Jeremy Whitlock
All top-level objects that `sway` supports should have a `getVendorExtensions` API for getting all `x-*` definitions at the root of its schema definition.
Whenever we process the `paths` or some other OAS type, we do not handle vendor extensions appropriately. This could lead to some `x-*` property beneath `paths` being turned into a...
It would be really nice if `sway` were modularized so that tooling consumers could cherry-pick what they want to use instead of getting everything.
We need to move the code that validates unresolvable references out of the structural validation, or move the unreferenced referenceable objects _(mouthful, I know)_ into structural validation.
To avoid consumers of `sway` to directly depend on `json-refs`, we should update the error/warning details to contain the JSON Pointer to the error/warning location.
Whenever we process parameters, we will use the default value provided by Swagger. Or so we thought. It seems for objects, we do not attempt to set the default values...
Originally reported here: https://github.com/apigee-127/swagger-tools/issues/241
We need to validate the `readOnly` field: https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-13
Right now, we have two types of validation: 1. Built-in validation that cherry-picks the places of the OAS document where we do validation 2. Custom validation that walks the document...
Without the ability to write M8 files, this library isn't very useful. While this isn't technically hard, there are places in the M8 files _(specifically the `Song` file)_ where data...