mirror of
https://github.com/pbakaus/impeccable.git
synced 2026-09-20 01:56:37 +03:00
The immediate tier moves to the registry, and reaches wasm
The design hook's immediate-tier list is the set of rule ids worth fixing at the edit site, and a downstream reviewer wants the same set to decide how loudly a finding is reported. `impeccable-hook` is native-only, so the list moves to `impeccable_core::registry` (the hook re-exports it) and the `detect` feature gains `immediate_tier_rules_json()`. The export is behind `detect`, which the in-page bundle does not build, so the tracked browser asset is unchanged. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Vau2X53xGTjjTCXWMVBoNY
This commit is contained in:
co-authored by
Claude Fable 5.1
parent
453a6e1500
commit
7bf0743852
+6
-1
@@ -206,7 +206,12 @@ and return the findings array `impeccable detect --json` prints, same keys and
|
||||
same order. `designSystem` carries the DESIGN.md inputs rather than a
|
||||
normalized object, because the JS API's normalized form used `Set`s and
|
||||
`Map`s that JSON cannot hold. Unparseable options fall back to the defaults.
|
||||
`antipatterns_json()` lists the built-ins followed by any pack's rows.
|
||||
`antipatterns_json()` lists the built-ins followed by any pack's rows, and
|
||||
`immediate_tier_rules_json()` returns the design hook's immediate tier (the
|
||||
rule ids worth fixing at the edit site). That list lives in
|
||||
`impeccable_core::registry::IMMEDIATE_TIER_RULES`, which `impeccable-hook`
|
||||
re-exports, so a wasm consumer reads the same one the hook runs on instead of
|
||||
keeping a copy.
|
||||
|
||||
A pack reaches those exports through `impeccable_wasm::set_rule_pack` and
|
||||
`exports_detect::set_static_rule_pack`, both Rust-only: the consumer is a
|
||||
|
||||
Reference in New Issue
Block a user