oav
oav copied to clipboard
Azure
Tools for validating OpenAPI (Swagger) files.
This raise an OAV problem: https://github.com/Azure/azure-rest-api-specs/pull/3495 Swagger ``` "Zone": { "properties": { "etag": { "type": "string", "description": "The etag of the zone." }, "properties": { "x-ms-client-flatten": true, "$ref": "#/definitions/ZoneProperties", "description":...
API version in examples should be the same as the one specified in swagger, and the folder name
``` bash-3.1$ oav extract-xmsexamples ./azure-rest-api-specs/arm-network/2016-12-01/swagger/network.json ./azure-sdk-for-net /src/SDKs/Network/Network.Tests/SessionRecords c:\Users\vissha\AppData\Roaming\npm\node_modules\oav\cli.js extract-xmsexamples Options: --version Show version number [boolean] -l, --logLevel Set the logging level for console. [choices: "off", "json", "error", "warn", "info", "verbose",...
When running validate.js for arm-authorization spec and recordings from .net tests, I got the following warnings: [ { code: 'UNUSED_DEFINITION', message: 'Definition is defined but is not used: #/definitions/RoleAssignmentFilter', path:...
- Currently the tool is blindly unifying x-ms-paths. This can be a problem if the paths are not unique. Make sure that the paths are unique.
Part of a `WebApps_GetConfiguration` response is a [SiteConfig](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/web/resource-manager/Microsoft.Web/stable/2022-03-01/CommonDefinitions.json#L3093-L3497) model which does not have any [x-nullable](https://azure.github.io/autorest/extensions/#x-nullable) to say that null values are allowed. > By default, a null value should be...
From the [definition](https://github.com/OAI/OpenAPI-Specification/blob/main/versions/2.0.md#paths-object) of path, the parameter of path should be included by `{}`, OAV should report an error if one of `{}` is missing.