Adam Altman

I would increase the priority of this. As I understand a use case is parameter (list) enforcement. For example, requiring certain parameters are defined for getting collections.

Here is a look at how we do it: ``` subject: type: Parameter property: name assertions: pattern: /^(after|before|limit|filter|sort|search)$/ where: - subject: type: PathItem matchParentKeys: /.*\/\{\w+\}\/\w+(?:-\w+)?$/ assertions: defined: true - subject:...

> Try to refer a path file relative to an endpoint with a path parameter: it will require something like paths/book_\{bookId\}.yaml When you say "refer" do you mean using `$ref`...

Both ideas are not valid though: The spec (3.1.0) allows only for `summary` or `description` to be sibling to the `$ref` and `allOf` doesn't make sense with `readOnly` in the...

I suggested the decorator originally, and my suggested was considered not viable -- they said it had to be the separate flag because of the order in which they run...

I like this idea. It seems practical. However, what about when you want to target specific subset of operations? Here is a practical example: - Collections are `GET` requests and...

@tatomyr I'm curious why this is a `minor` instead of a `patch`? I thought a bug fix would be a `patch`? Is this bugfix not considered backwards compatible perhaps? (if...

Maybe add to the cookbook?

We have this option which is mostly hidden.  https://redocly.com/docs/cli/configuration/ ```yaml resolve: doNotResolveExamples: true ``` I see the issue is this will not resolve anything. But you want the example...

I wonder if this can be handled through a different way, a combination of the config: ``` resolve: doNotResolveExamples: true ``` And a preprocessor or decorator which actually resolves the...