javierbrea / eslint-plugin-boundaries / 31324661070

100%

master: 100%

push

github

fix: Point legacy selector warnings to the correct migration guide, with clearer per-form messages (#482)

* fix(#477): Fix wrong migration guide links in legacy selector warnings, and a related matching bug

- Legacy selector deprecation warnings now link to the migration guide that
  actually deprecated the detected syntax, instead of always pointing to
  v5-to-v6. Each legacy form (string, tuple, element selector used directly
  as an entity selector) gets its own message with a concrete before/after
  example and the correct guide anchor.
- boundaries/dependencies and boundaries/element-types now warn when an
  allow/disallow entry omits the from/to wrapper, a case that previously
  passed silently. Placeholder examples in all these messages use
  "your-type" instead of concrete names like "component"/"helper".
- The "unrecognized selector shape" warning now names only the properties
  that actually failed validation instead of always listing all five.
- Fixed a real matching bug uncovered while adding the wrapper check: a
  policy with neither `from` nor `to` at the policy level and a bare
  allow/disallow entry (e.g. `{ allow: { element: { type: "x" } } }`) used
  to invert the policy's meaning and crash the linter on every matched
  dependency, instead of scoping the entry to `to` as allow/disallow have
  always meant.
- Warning summaries say "policy"/"policies" instead of "rule(s)", matching
  v7 terminology.

Adds unit and integration test coverage for all of the above (100% coverage
maintained) and a CHANGELOG entry.

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

* fix(#477): Address PR #482 self-review comments and Sonar findings

Reclassify single-item legacy array selectors (e.g. allow: ["helpers"])
as string selectors instead of tuple selectors, since the tuple example
shows captured values the user never wrote. Clarify the unwrapped-target
warning wording for policies that fix "to" without "from". Require a
valid policy targe... (continued)

2029 of 2029 branches covered (100.0%)

Branch coverage included in aggregate %.

107 of 107 new or added lines in 2 files covered. (100.0%)

2458 of 2458 relevant lines covered (100.0%)

4162.39 hits per line