ota-meshi / eslint-plugin-json-schema-validator / 29001337428

91%

push

github

fix: resolve YAML merge keys in `no-invalid` (#501)

* fix: resolve YAML merge keys in `no-invalid`

Closes #500

* refactor: resolve YAML merge keys via `getStaticYAMLValue`

Consume merge-key resolution from yaml-eslint-parser 2.1.0 instead of
resolving `<<` in the plugin. `no-invalid` now calls `getStaticYAMLValue`
directly; the local value-resolution helpers are removed, while the
merge-aware node lookup used for error locations is kept.

Merge keys are only resolved for YAML 1.1 documents, matching the parser.
The merge-key test fixtures declare `%YAML 1.1`, and the rule docs explain
how to opt files in via `defaultYAMLVersion`.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* fix: report merged properties at the `<<` pair and survive transitive merges

Map schema violations on merge-provided properties back to the `<<` pair
(with a "(from merge key)" message hint) instead of throwing. Testing
per-key membership of the merge source is not possible here: resolving a
sub-node with `getStaticYAMLValue` has no document version context, so
merge keys nested inside the source (transitive `<<`) are not resolved,
which crashed the rule with "Unexpected state". Only the source's
top-level shape is checked, mirroring `getStaticYAMLValue`.

Also relocates the merge-key docs to the shared advanced-usage guide.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

611 of 708 branches covered (86.3%)

Branch coverage included in aggregate %.

83 of 84 new or added lines in 2 files covered. (98.81%)

2694 of 2948 relevant lines covered (91.38%)

248.76 hits per line