@reticlehq/eslint-plugin 2.7.0 → 2.8.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +5 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -4,8 +4,8 @@ Keeps the Reticle **signal layer self-enforcing**. When your store mutates user-
|
|
|
4
4
|
|
|
5
5
|
## Install
|
|
6
6
|
|
|
7
|
-
```
|
|
8
|
-
|
|
7
|
+
```bash
|
|
8
|
+
npm i -D @reticlehq/eslint-plugin
|
|
9
9
|
```
|
|
10
10
|
|
|
11
11
|
Peer dependency: `eslint >= 9` (flat config).
|
|
@@ -95,4 +95,6 @@ function commit() {
|
|
|
95
95
|
|
|
96
96
|
## How it fits the workflow
|
|
97
97
|
|
|
98
|
-
The runtime side advertises signals via `registerCapabilities({ signals: [...] })`
|
|
98
|
+
The runtime side advertises signals via `registerCapabilities({ signals: [...] })` and fires them with `reticle.signal(name, data)`. A Zustand `signalMap` / `commitAndSignal` pair centralizes that in your store. This lint rule is the **static** counterpart that guards those pairs so the signal map can't silently fall behind the store.
|
|
99
|
+
|
|
100
|
+
Apache-2.0.
|
package/package.json
CHANGED