Repository navigation
web: main fails to start: Cannot access 'textInput' before initialization (name clash from the au... - #987
web: main fails to start: Cannot access 'textInput' before initialization (name clash from the au...#987fizzy-linux[bot] wants to merge 5 commits into
Conversation
Agent-Team: linux Worker: codex
Agent-Team: linux Worker: codex
|
TRIAGE @2f12172b auto: mechanical rules met (fizzy-* app author, names work#633, 18 non-test lines <= 400, no risky path). Labelled |
PM note: how this PR will be handledWhat it is for: linux: work-633 Rules that apply: none special. Things to watch (checked by rule):
What happens next:
A living status comment below is kept current. Nothing here is a merge decision. |
Where this PR standsStage: Author's turn What the PM needs before approving (ticks as it is met; the full CI runs only at the end, after the reviews are clean):
Reviews at the current commit (
3 earlier reviews are for older commits and will be redone. Latest fixes comment: https://github.com/fizzyedit/work/issues/669#issuecomment-6524884532 (1 finding answered) Updated 2026-10-30 14:20 UTC by the PM. This comment is edited in place. |
Agent-Team: linux Worker: codex
Agent-Team: linux Worker: codex
|
Follow-ups: |
|
PM decision after two rounds (hard stop): the rework fixed the first CI error but CI fails again on a different web test ('the input stays above the keyboard'), because main's keyboard handling moved (fizzy#1019). Closing this old branch; work#633 is re-cut fresh against current main (first check whether the startup crash still reproduces: fizzy#970 may already have fixed it). |
Part of fizzyedit/work#633
Rework: work#801
In plain words
This fixes the duplicate declaration that stops the web checks from starting when this branch is combined with main. The change keeps the existing startup checks intact.
What you will notice
Nothing visible: internal.
How this serves fizzy
Goal: reliable web startup; keeps the web checks able to detect problems before release.
Goal
Address PR #987's latest PM ruling, duplicate workerMessages declaration only (work#801).
What changed and why
Move the existing declaration beside the worker mock, matching origin/main's insertion location. Three-way merging then produces one declaration rather than two. No other source change.
How it was verified
Formatting, lint, native build, unit tests, integration, check-web, SDK-version and all local web suites pass. A three-way file merge reproduces the duplicate SyntaxError without this edit and passes syntax checking with it. See GATES.md for exact results and the additional merged runtime assertion failure.
Not done / follow-ups
Harness must merge current main, commit, push and post FIXES; this sandbox cannot write Git metadata or use the network. The merged embed test reaches a later existing assertion interaction: this branch moves the input to 30px, main expects 20px. No change made outside the duplicate-declaration-only ruling; merged runtime suite is not claimed passing.
Changes (207 files, +1735/-7317)
Gates: 6 of 6 passed
scripts/check-fmt.sh(exit 0)scripts/zb build --summary all(exit 0)scripts/zb build test --summary all(exit 0)scripts/zb build test-integration --summary all(exit 0)scripts/zb build check-web --summary all(exit 0)scripts/zb build test-sdk-version --summary all(exit 0)