Andrew Tatomyr

Hi @Nothing-Works, This is designed that way due to internal implementation 😅. We're considering removing this in future versions, but it's too early to state anything.

@wuuti what OpenAPI version is that?

@christianseel for OAS 3.1, it's possible (and recommended) to use `examples` instead of `example`. Then you should be able to use `$ref` as a literal value like in the following...

Hi, thanks for reporting! Could you specify the exact and OAS and Redocly CLI versions?

Hi @kekel87, Thanks for creating the issue! However, I'd vote for extending the `dissallowed` assertion functions to accept RegExps (currently it only accepts arrays). So the rule could be written...

Hi @ParanoidUser, > using all recommended rules as is, but with tweaked severity to fail tests even on warnings. Is it related to [this issue](https://github.com/Redocly/redocly-cli/issues/747)?

A similar request: https://github.com/Redocly/redocly-cli/issues/1304

Hey @jeremyfiel, does a configurable rule like the following solve your problem? ```yaml rules: rule/encoding: subject: type: MediaType filterInParentKeys: - application/json assertions: disallowed: - encoding ```

I'm reluctant to write yet another built-in rule for that, or to extend the existing `spec` rule. What about introducing an extended 'recommended' ruleset that includes only configurable rules? I'm...

Thanks for reporting this!