Hayden

Is this solved?

Actually, according to https://github.com/json-schema-org/json-schema-spec/issues/672, `$ref` with siblings in the schema behaves exactly like `allOf`: ``` "reference": { "$ref": "#/definitions/Defined", "required": [ "subproperty" ] } ``` is equivalent to: ``` "reference":...

@goodoldneon The thing is `required` doesn't need to specify properties that only exist in `properties`. That's why it's independent of `properties`. See spec: https://json-schema.org/draft/2020-12/json-schema-validation.html#rfc.section.6.5.3 It mentions NOTHING about the strings...

@goodoldneon nope. `type` also validates independently. see https://json-schema.org/draft/2020-12/json-schema-core.html#rfc.section.7.6.1

With remote - WSL extension, the document format still doesn't work.

+1. Looks like `@types/testing-library__jest-dom` depends on `[email protected]` and if `jest` is upgraded to v27, the two different version of `pretty-format` is causing problem possibly because `[email protected]` exports a different value

I have a similar issue with a different case: I have directory with package.json but they're not part of the workspaces so they don't have symlink in the monorepo root...

@ljharb the package.json also contain name and version. The package is a standalone project that doesn't follow the monorepo release cycle so it's not part of the workspaces

@JoshuaKGoldberg Thanks for bumping this! I was able to look at this again. I ran into some trouble getting the coverage report locally after merging the latest main, do you...

@JoshuaKGoldberg @bradzacher please review the PR again. I delegate most of the non-TS cases to the base rule so I only keep the TS-related test cases.