Andrew Tatomyr

**Note:** This might be tangentially related to https://github.com/Redocly/redocly-cli/issues/1285.

Thanks for reporting! We'll take a look at this.

The issue comes from AJV: ``` ┬ @redocly/[email protected] -> ./packages/core └─┬ @redocly/[email protected] └─┬ [email protected] └── [email protected] ```

Hi @Gidgidonihah, Could you check if using the `allOf` trick solves your issue? ```yaml allOf: - $ref: ./id.yaml readOnly: true description: A generic ID but that is specifically read only...

> But I don't think that should be a long-term solution. I agree. The behaviour isn't obvious. I believe it stems from the difference in [JSON Schema drafts](https://json-schema.org/understanding-json-schema/structuring#dollarref): > _Draft-specific...

@adamaltman the issue is still there though, as we don't properly resolve `description` either. Regarding other keys, maybe it's worth introducing a rule that will warn if someone uses a...

Related issue: https://github.com/Redocly/redocly-cli/issues/1510

Hi @CidTori! The rule itself relies on resolving refs on the current filesystem. As far as I'm aware, the Windows system is case-insensitive, so the refs are getting resolved successfully....

That makes sense. Thanks for sharing.

I'm for it. The current behaviour has some implications in the code, which I stumbled upon the other day, and it was hard to figure out what it was about.