From 75423f0c2f3218360a4dce4e7fc4f0b4330674ac Mon Sep 17 00:00:00 2001 From: 4gray Date: Tue, 6 Oct 2026 14:19:20 +0200 Subject: [PATCH] docs(performance): say the zoneless flag ran with the three implemented journeys Review follow-up (Greptile): J4 search is still planned, so the flag was validated with J1-J3 and the Electron E2E suite, not all four journeys. Co-Authored-By: Claude Opus 5.5 --- docs/architecture/zoneless-migration.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/architecture/zoneless-migration.md b/docs/architecture/zoneless-migration.md index 5435efcf6..a676d56bb 100644 --- a/docs/architecture/zoneless-migration.md +++ b/docs/architecture/zoneless-migration.md @@ -51,8 +51,9 @@ must be ticked here. `apps/web`. Each reports the tick counters before and after and runs the affected unit and E2E tests. 4. [x] `provideZonelessChangeDetection()` behind a build-time - `fileReplacements` flag, off by default; all four journeys and the - Electron E2E suite run with it on (see [Zoneless flag](#zoneless-flag)). + `fileReplacements` flag, off by default; the three implemented journeys + (J1-J3; J4 is still planned) and the Electron E2E suite run with it on + (see [Zoneless flag](#zoneless-flag)). 5. [ ] Flag on by default, `zone.js` out of `polyfills`, new tick baselines (`renderer.cdTicksIdle30s` and any counter that becomes deterministic once the zone.js race is gone).