oav

oav copied to clipboard

keryul

- Retire commands "generate-uml" - Retire commands "generate-wireformat" - Retire commands "resolve-spec" - Retire Autorest plugin

keryul

Some scenarios have the situation that one step use a specific location while others use the global location. For now, whether using jsonp to replace location value or define another...

tadelesh

ARM ID validation

1

Related to #765

matthchr

npm audit output: npm audit report jsdom =0.18.3 Depends on vulnerable versions of yuml2svg node_modules/oav

laurawalker

keryul

Type in response is random string instead of ARM resource type

2

Given an example: ```json { "operationId": "Categories_Update", "title": "Categories_Update", "parameters": { "api-version": "2022-06-01-preview", "subscriptionId": "00000000-0000-0000-0000-000000000000", "resourceGroupName": "rgthrottling", "accountName": "aaaaaaaaaaaaaaaaaaaaaaaaaaa", "categoryName": "aaaaaaaaaaaaaaaaaaaaaaaaa", "properties": { "properties": { "windowDuration": "PT5M" } } },...

abatishchev


Alancere

Support $ref siblings

1

To align with autorest behavior https://github.com/Azure/autorest/blob/main/docs/openapi/howto/$ref-siblings.md

leni-msft

I'm attempting to generate an API scenario test using oav following the directions here: https://github.com/Azure/azure-rest-api-specs/blob/main/documentation/api-scenario/how-to/generateABasicApiScenario.md To avoid the failure documented in #815, I am running oav from the directory that...

mikekistler