Andrew Tatomyr

BTW, what do you mean by '...prevents component from being available in UI'? Is it just linter failing and not passing to the next step or you'd expect the `dependentRequired`...

@jeremyfiel you're correct. And there is one more issue that I think is related to missing the type there: https://github.com/Redocly/redocly-cli/issues/1598.

Interesting. I didn't know arbitrary keys are allowed in Schema Objects. Could you share where exactly in the specification this is mentioned? Anyway, I'm not sure if it makes sense...

Thanks for the link @Drew-Kimberly! I'm still not sure if we want to change the behaviour. Let's wait until we get more votes for that. Meanwhile, you can tweak the...

@marianobntz how exactly are you trying to apply the rules? Could you provide an example of what doesn't work for you?

@marianobntz sorry for the late response. Glad you found the root cause 🎉 I'd love to see your contribution to our Cookbook [🧑‍🍳📖](https://github.com/Redocly/redocly-cli-cookbook).

Do you mean the [spec-strict-refs](https://redocly.com/docs/cli/rules/spec-strict-refs/) rule? What is the error? What OpenAPI and Redocy CLI versions are?

According to the OAS 3/3.1 specification, the `schemas` property inside the `components` must be a map of schema objects (not a $ref): https://spec.openapis.org/oas/v3.1.0#components-object. Although Redocly CLI correctly resolves the $refs...

I confirm this is a bug. Thanks for creating the issue!

That would be amazing! You can start with the `ref-utils` file, specifically [here](https://github.com/Redocly/redocly-cli/blob/main/packages/core/src/ref-utils.ts#L45), where the ref gets split into the url and the pointer. Then, the link itself gets loaded...