[Upd4ting]

Why

The contract never said whether a dotted index field, orderBy name or lookup key is a nested path, so backends disagree. Localized fields and _internal records from interface-database-decorators need the nested reading. This PR states that a dotted name is a nested path. It adds a conformance test that every backend runs, and it lets lookup(other, local, "a.b") typecheck without a cast.

Summary

flowchart LR
  A["dotted name 'title.fr'"] --> B{where}
  B -->|"IndexDefinition.fields entry, or index name without fields"| N["nested path: fr inside title"]
  B -->|"orderBy(name): index name, or else a field"| N
  B -->|"lookup otherKey: FieldPath<U>"| N
  N -.->|"never"| L["top-level key named 'title.fr'"]

Loading

+export type FieldPath<T> = (keyof T & string) | `${keyof T & string}.${string}`;
 lookup(right: Stream<U>, localKey: TK,
-  otherKey: keyof U & string,
+  otherKey: FieldPath<U>,
 )

• FieldPath checks only the first segment. A strict path type would reject "title.fr" on a decorators model, which types a localized field as string but stores a locale record.
• localKey stays a top-level field, because the result type replaces that field.
• The TSDoc of IndexDefinition.fields and Stream.orderBy, and the lookup, indexes, stream and datum docs, state the rule.
• Two lint directives in the touched files suppressed nothing. The suppressions check fails on such a directive in a touched file, so this PR removes both and lowers the anti-slop/no-chained-type-assertions ceiling from 3 to 1.

Evidence

The new suite is src/tests/dotted_paths.test.ts. Each case fails on a backend that reads the literal top-level key. The rows' insertion order and their title.fr, title.en and meta.rank orders all differ.

• Before (types): pnpm exec tsc --noEmit with stream.ts and datum.ts at main:

  src/tests/dotted_paths.test.ts(148,62): error TS2345: Argument of type '"meta.sku"' is not assignable to parameter of type '"_id" | "title" | "meta"'.
  src/tests/dotted_paths.test.ts(161,37): error TS2345: Argument of type '"meta.sku"' is not assignable to parameter of type '"_id" | "title" | "meta"'.
  

  After: exit 0, no output.
• Before (behavior): the compiled suite run against @antelopejs/postgres main (ad431a5) and @antelopejs/rethinkdb main (95126f3), which read the literal key:

  postgres:  1 passing, 6 failing  (getAll: expected [] to deeply equal [ Array(1) ]; lookup: Target cannot be null or undefined.)
  rethinkdb: 1 passing, 6 failing  (getAll dotted field: ReqlLogicError: Expected type ARRAY but found STRING)
  

  After: @antelopejs/mongodb 1.6.0, which reads the nested path, through pnpm exec ajs module test . -f dist/tests/dotted_paths.test.js:

  ✔ getAll on an index whose fields entry is dotted finds the row by its nested value, not a literal top-level key
  ✔ getAll on a dotted index name without fields finds the row by its nested value, not a literal top-level key
  ✔ orderBy on an index with a dotted field sorts by the nested value, not in insertion order
  ✔ orderBy on a dotted name that is no index sorts by the nested value, not in insertion order
  ✔ Stream lookup on a dotted otherKey matches the nested value, not a literal top-level key
  ✔ Datum lookup on a dotted otherKey matches the nested value, not a literal top-level key
  7 passing
  

• pnpm run checks: Checks: 11 passed, 0 failed.

Scope

• Postgres (ANT-2089) and rethinkdb fail the new suite until they read nested paths. Their fixes are separate PRs in those repos.
• The ### Upgrade notes entry follows in the docs(changelog) PR after release.

Merge Danger

Door: two-way

Blast Radius: backends

A backend that bumps to this version and runs the conformance suite fails it until it reads nested paths. Typed callers only gain accepted keys: FieldPath<U> contains keyof U & string, and FieldPath<any> is string.