@zvenigora/ng-eval-core 0.7.0 → 0.9.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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@zvenigora/ng-eval-core",
3
- "version": "0.7.0",
3
+ "version": "0.9.0",
4
4
  "description": "An expression evaluator for Angular",
5
5
  "repository": {
6
6
  "type": "git",
@@ -661,8 +661,8 @@ declare class EvalContext {
661
661
  *
662
662
  * {@link get} calls this rather than inlining the loop, so that the read
663
663
  * hooks' `scoped` flag and the resolution it describes are the *same*
664
- * implementation. A second copy of the order would drift - `getKey` already
665
- * shows what that looks like when it does.
664
+ * implementation. A second copy of the order would drift - `getKey`'s did,
665
+ * until 0.8.0 (`docs/backlog-retired.md` A4).
666
666
  *
667
667
  * A binding whose value is `undefined` is **found** here, and no longer reads
668
668
  * as absent - see {@link scopeHolding}.
@@ -713,7 +713,7 @@ declare class EvalContext {
713
713
  * single pass is what keeps that question answered by the same code as
714
714
  * {@link get}'s step 1. The alternative was a second copy of the
715
715
  * innermost-scope walk at each write site, which is the defect
716
- * `docs/backlog.md` A4 and A10 already describe - two copies of one
716
+ * `docs/backlog-retired.md` A4 and A10 describe - two copies of one
717
717
  * resolution order, drifting - reproduced on purpose.
718
718
  *
719
719
  * @param key - The key to look for.
@@ -762,10 +762,29 @@ declare class EvalContext {
762
762
  */
763
763
  getThis(key: unknown): unknown | undefined;
764
764
  /**
765
- * Retrieves the value associated with the specified key from the evaluation context.
766
- *
767
- * @param key - The key to retrieve the value for.
768
- * @returns The value associated with the key, or undefined if the key is not found.
765
+ * The key {@link get} resolves `key` to: the spelling under which the source
766
+ * that answered holds it. The read hooks report this as the key that was
767
+ * read, and the write visitors write to it under `caseInsensitive`.
768
+ *
769
+ * Resolved through {@link get}'s own chain, so the two cannot disagree:
770
+ *
771
+ * - A pushed scope, the original, or a `global` prior scope holding the key:
772
+ * the spelling that source holds it under - corrected only where the
773
+ * source is a case-insensitive `Registry`, which is the only kind that
774
+ * matches another spelling.
775
+ * - A prior scope's namespace: the namespace, as the scope declares it.
776
+ * - A lookup: the key as written, since a lookup returns no key.
777
+ * - Nothing: undefined, exactly when {@link get} finds nothing. A pushed
778
+ * scope binding the key to `undefined` counts as found, as in {@link get}.
779
+ *
780
+ * Since 0.8.0. Up to 0.7.x it walked its own copy of the chain: it never
781
+ * consulted lookups, never matched a namespace, reported keys held inside a
782
+ * non-global prior scope that {@link get} never reads, and answered a
783
+ * spelling from a source where {@link get} found no value - including every
784
+ * key at all, once a plain-object scope was pushed.
785
+ *
786
+ * @param key - The key as written.
787
+ * @returns The resolved key, or undefined when {@link get} finds nothing.
769
788
  */
770
789
  getKey(key: string | number | symbol): string | number | symbol | undefined;
771
790
  /**