Reconnexion/ng-eventually
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: les arbitrages de la session entrent dans les taches

Browse Source
This commit is contained in:
Sylvain Duchesne
2026-09-16 15:22:05 +02:00
parent eb8a7163a2
commit 1a4857cb75
6 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.tasks/todo/T01.d-use-shape-query-reads-through-the-sdk.md
+2
View File
@@ -29,6 +29,8 @@ So this change takes the one reactive read that works and puts it on the path th
**Hard gate:** `bun test` → 0 fail; `bunx tsc --noEmit -p packages/polyfill/tsconfig.json` → exit 0; `bunx tsc --noEmit -p packages/polyfill/e2e/tsconfig.json` → exit 0; `python3 ~/.claude/skills/concept/lint.py` → 0 ERROR. Anti-cheat: no `any`, no `@ts-ignore`, no deleting or skipping a test, no widening an assertion.
**Resolved since planning (2026-09-16).** `useShapeQuery` does NOT delegate to the SDK's `useShape` — that return type cannot carry the request state, which is the whole point. It KEEPS `watchShape`'s implementation: the observable and the state tracking are ours. What changes is the PARAMETER (the SDK's `Scope`) and what is queried underneath (the SDK's shape query instead of `readUnion`). **`isError` stays.** The reasoning "it survives only if the SDK exposes an error channel" is wrong: the polyfill's mission is to ENRICH the SDK in its announced direction, not to be bounded by what it exposes today. Wire real errors if you can; otherwise the field stays and is filled later.
## Progress
## Result