Josh Ponelat

Thanks @char0n @derberg I'm happy with the word changes, and I see adding the version as a good thing .

Hi folks, sorry for all the waiting. Will take a look into this. Thank you for your patience.

Can we consider adding a flag to indicate that PKCE is used for Authorization flows? We're currently doing this out-of-band for some tooll, ie: https://github.com/swagger-api/swagger-ui/pull/7438.

hey @devthehuman ... the file ( and function, I think ) you're after lies here... https://github.com/swagger-api/swagger-ui/blob/master/src/core/system.js#L285 That function wraps deepExtend, which is how we combine plugins into one largish object....

@frantuma @char0n Is it possible to at least enhance the error messaging around this? I have bumped into a few invalid YAML documents and have no idea how to fix...

Similar thing happens for me ( emacs 26.1, Linux Mint 18.1 ). Using `helm-do-ag-project-root`. When I type `-G` I get a very similar error as above.

Thanks @pomali do you know if (and which) part of the YAML specification non-leading quotes may be part of?

@mnaumanali94 this sounds like a bug. Where OAS 3.1, supports `prefixItems`, `items`, `unevaluatedItems` or `contains` (more?).

Hey @dtolb, yup you are correct OAS 3.1, [does indeed support having "roles"](https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#patterned-fields-3) (to use the non-oAuth terminology) in the array within the security requirement. So shouldn't report an error....

@mnaumanali94 do we have any use-cases for "passing through unknown spec files as error free"? I would consider throwing an error if spectral can't identify the specification? Couple of ways...