Content
View differences
Updated by Alexander Coles 14 days ago
\- Mission — the Angular re-bootstrap-on-every-turbo:load (turbo-angular-wrapper.ts), crux of DREAM-514
\- Problem — the hidden interface: destroy all root components + runBootstrap on each navigation, skip(1) guard, zero tests. Inlined candidate B's analysis since the temp HTML report was purged (days elapsed)
\- Proposed deepening — named bridge module (bootstrap/onTurboNavigate/teardown), inject event source + appRef for testability; deletion test
\- Integration map — the 6-area coupling surface with file:line (re-bootstrap, plugin-context/useAngularServices seam, opce-\* custom elements, 3 morph guards, Rails op\_turbo, existing nav spec)
\- Build-on, don't redo — PR #23980 test seam; turbo-angular-wrapper.ts deliberately left out for exactly this work
\- Gotchas — jsdom vs browser-mode vitest, precompiled-asset rebuild, chruby 4.0.2, zoneless, RxJS-vs-signals
\- Scope — B in; D/E (OP-19618) and turbo#1300 out; DREAM-514 on-hold → confirm appetite, seam-first
\- Problem — the hidden interface: destroy all root components + runBootstrap on each navigation, skip(1) guard, zero tests. Inlined candidate B's analysis since the temp HTML report was purged (days elapsed)
\- Proposed deepening — named bridge module (bootstrap/onTurboNavigate/teardown), inject event source + appRef for testability; deletion test
\- Integration map — the 6-area coupling surface with file:line (re-bootstrap, plugin-context/useAngularServices seam, opce-\* custom elements, 3 morph guards, Rails op\_turbo, existing nav spec)
\- Build-on, don't redo — PR #23980 test seam; turbo-angular-wrapper.ts deliberately left out for exactly this work
\- Gotchas — jsdom vs browser-mode vitest, precompiled-asset rebuild, chruby 4.0.2, zoneless, RxJS-vs-signals
\- Scope — B in; D/E (OP-19618) and turbo#1300 out; DREAM-514 on-hold → confirm appetite, seam-first