@zvenigora/ng-eval-core 0.7.0 → 0.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/CHANGELOG.md CHANGED
@@ -14,6 +14,47 @@ Versions 0.1.104–0.1.107 are on npm without entries here.
14
14
 
15
15
  ---
16
16
 
17
+ ## [0.8.0] - 2026-10-02
18
+
19
+ **`EvalContext.getKey` resolves through `get`'s own chain —
20
+ [A4](../../docs/backlog-retired.md#a4) and [A10](../../docs/backlog-retired.md#a10).** A breaking
21
+ minor. No exported symbol changes shape — the `.d.ts` differs from 0.7.0 in documentation comments
22
+ only — but `getKey`'s answers change, and with them the `key` of identifier and member read events
23
+ and the key the write visitors assign to under `caseInsensitive`. `eval-signals` 0.2.0 and
24
+ `eval-forms` 0.2.6 widen their peer ranges to admit it.
25
+
26
+ ### Breaking
27
+ - **`getKey` answers what `get` resolved, and nothing when `get` finds nothing.** It used to walk
28
+ its own copy of the resolution order, which disagreed with `get` in four ways; each is now
29
+ `get`'s answer:
30
+ - **A namespace is reported as the scope declares it.** With a prior scope namespaced `dog`,
31
+ `Dog.Says()` under `caseInsensitive` reports read keys `['dog', 'says']`, where it reported
32
+ `['Dog', 'says']`.
33
+ - **An unbound name gets no key.** With a plain-object scope pushed, `getKey` answered every
34
+ key as present, so a name nothing holds came back as itself; and a key held only in a source
35
+ `get` does not read — a wrong-case key in a case-sensitive `Registry`, a key inside a
36
+ non-global prior scope — came back spelled as that source holds it. All of these are now
37
+ `undefined`. An identifier read still reports the name as written when `getKey` answers
38
+ nothing.
39
+ - **A key only a lookup resolves is reported as written**, where `getKey` returned `undefined`
40
+ because it never consulted lookups. Under `caseInsensitive` the write visitors resolve their
41
+ target through `getKey`, so an assignment to such a key now writes, or is refused, under its
42
+ name: a `@zvenigora/ng-eval-signals` context's write error names `'COUNT'` rather than
43
+ `'undefined'`.
44
+ - **A spelling comes from the source that supplied the value.** Under `caseInsensitive` with a
45
+ case-sensitive `Registry` holding `a`, `getKey('A')` returned `'a'` while `get('A')` found
46
+ nothing there and went on to later sources.
47
+ - **A member of the context itself resolves through `getKey`'s answer.** Under `caseInsensitive`,
48
+ `This.COUNT` for a key only a lookup resolves, and `This.Dog` for a namespace `dog`, evaluated
49
+ to `undefined`: the member visitor read `get(getKey(key))`, and `getKey` answered nothing. Both
50
+ now resolve.
51
+
52
+ ### Changed
53
+ - `getKey`'s JSDoc states its answers, and two sentences in `getFromScopes` / `scopeHolding` that
54
+ described `getKey`'s drift are corrected. Those are the whole `.d.ts` difference from 0.7.0.
55
+
56
+ ---
57
+
17
58
  ## [0.7.0] - 2026-10-01
18
59
 
19
60
  **Errors keep their identity, `thisArg` is applied, and three silent outcomes now throw —