[Bug] Blockly tool crashes on load — ViewChild resolves undefined under *transloco (same class as diagram #314 finding) #342

New Issue

2026-07-03T18:08:46Z

spikerj commented

2026-07-03 18:08:46 +00:00

Found by the P1 anonymous walk after tightening the console-error assertion (#314, epic #307) — Angular's ErrorHandler swallows this into console.error, so the previous pageerror-only assertion missed it.

Symptom

Opening /tools/(tools:blockly) logs:

ERROR TypeError: Cannot read properties of undefined (reading 'nativeElement')
    at s.initializeBlockly (...)
    at s.ngAfterViewInit (...)

The workspace never initializes.

Root cause

blockly.component.ts queries #blocklyDiv with a decorator @ViewChild and calls initializeBlockly() from ngAfterViewInit. The element sits inside the *transloco structural directive, whose embedded view renders only after translations load — at ngAfterViewInit the query is still undefined. Same class as the diagram tool bug fixed in spikersoft-angular#104, but a bare guard isn't enough here: the view can render after ngAfterViewInit, so guarding would leave the tool permanently uninitialized.

Fix

Signal viewChild query + an effect that runs initializeBlockly(div) exactly once when the element actually renders (idempotence via the existing workspace signal).

Found by the P1 anonymous walk after tightening the console-error assertion (#314, epic #307) — Angular's ErrorHandler swallows this into `console.error`, so the previous pageerror-only assertion missed it. ## Symptom Opening `/tools/(tools:blockly)` logs: ``` ERROR TypeError: Cannot read properties of undefined (reading 'nativeElement') at s.initializeBlockly (...) at s.ngAfterViewInit (...) ``` The workspace never initializes. ## Root cause `blockly.component.ts` queries `#blocklyDiv` with a decorator `@ViewChild` and calls `initializeBlockly()` from `ngAfterViewInit`. The element sits inside the `*transloco` structural directive, whose embedded view renders only after translations load — at `ngAfterViewInit` the query is still `undefined`. Same class as the diagram tool bug fixed in spikersoft-angular#104, but a bare guard isn't enough here: the view can render *after* `ngAfterViewInit`, so guarding would leave the tool permanently uninitialized. ## Fix Signal `viewChild` query + an `effect` that runs `initializeBlockly(div)` exactly once when the element actually renders (idempotence via the existing `workspace` signal).

spikerj added the bug label 2026-07-03 18:09:00 +00:00

spikerj commented

2026-07-03 19:39:32 +00:00

Resolved in spikersoft-angular PR #106 (merged to master). Replaced the decorator @ViewChild with a signal viewChild + a run-once init effect, so Blockly initializes whenever the *transloco view actually renders. Verified by the tightened anonymous walk (tools spec green). Closing.

Resolved in spikersoft-angular PR #106 (merged to `master`). Replaced the decorator `@ViewChild` with a signal `viewChild` + a run-once init effect, so Blockly initializes whenever the `*transloco` view actually renders. Verified by the tightened anonymous walk (tools spec green). Closing.

spikerj closed this issue

2026-07-03 19:39:39 +00:00

spikerj referenced this issue

2026-07-03 19:39:52 +00:00

[E2E P1] Anonymous walk — every public route + primary actions #314

spikerj referenced this issue

2026-07-03 20:03:37 +00:00

[Epic] Full-coverage Playwright E2E walk of the Angular app with live Jaeger + Seq telemetry #307

spikerj referenced this issue

2026-07-17 05:23:11 +00:00

[Backend] Duplicate placeholder names in structured-log templates render unbound holes and collide in Seq (SonarQube S6677 x3) #635

Sign in to join this conversation.