David Biesack

I had the same problem with other projects which depend on jsonpath; see https://github.com/LucyBot-Inc/api-spec-converter/issues/132 for example. I'm on Mac with npm 5.6.0 and node 8.11.3 Adding `--unsafe-perm=true --allow-root` to the...

How about allowing us to organize parameters into **sets**? Then a path could reference parameter sets to automatically get all the parameters in those sets: ``` parameters: - name: id...

FWIW, I would like OAS to use structural abstractions (such as the tags I suggest above) over `$ref` representation "tricks" which IMHO hide or obscure the intent. The API designer's...

Please also see the discussion on #445 which discusses creating reusable parameter sets. I see all these as related topics: how to get effective reuse of OAS constructs, either through...

What we are doing in the interim is to use `#tag` in the paths to differentiate these. /a/b/c: post: /a/b/c#merge: post: We have customized Swagger UI to hide these tags...

in particular, injecting the sluggified version of the operation's `tags` into the anchor name ( `#tag/Sluggified-Tag-Text/operation/operationId` makes this harder and is not necessary. One should be able to reference the...

It is not represented anywhere. I'd like to see it in the table that describes the parameters. It is just defined as `array[string]` The code samples do not show parameters.

We have our own custom templates for parameters, so I can add include `{{p.style}}` in our layout. (We use a simpler two columns, Name in the left column, with optional...

It's minor. The processing log gets swamped by all the repeated lines about loading all the template files and is thus harder to view or track.

yes, I'm using `user_templates`...