controlled redirect to /host or /player on invalid/missing context
refresh rehydrate support by restoring host session code and hydrating on shell init using existing JSON endpoints
No backend contract changes.
Implements #191.
- add host/player route guards + context resolvers
- enforce session-context checks for phase routes
- controlled redirect to /host or /player on invalid/missing context
- refresh rehydrate support by restoring host session code and hydrating on shell init using existing JSON endpoints
No backend contract changes.
Route-level guard/resolver wiring for host/player entry is consistent across route variants.
Session-code persistence and bootstrapping behavior in host/player shells look correct for hash-route re-entry.
Existing player gameplay specs pass with the refactor.
No blockers found.
LGTM ✅
Review notes:
- Route-level guard/resolver wiring for host/player entry is consistent across route variants.
- Session-code persistence and bootstrapping behavior in host/player shells look correct for hash-route re-entry.
- Existing player gameplay specs pass with the refactor.
No blockers found.
... > wires showQuestion, mixAnswers and calculateScores ...
... > runs next-round transition without reload ...
Kommando kørt: cd frontend/angular && npm test
Resultat: 3 failing tests i src/app/features/host/host-shell.component.spec.ts.
Konsekvens: PR er ikke merge-klar før host-regressionen er rettet og tests er grønne.
Forslag til fix-retning:
Bevar/retabler eksisterende host refresh-semantik i startRound/phase-overgange, så der fortsat sker forventet efterfølgende GET-refresh.
Opdater route/session-guard integration så den ikke ændrer runtime-adfærd for eksisterende host actions.
Kør mindst npm test i frontend/angular og vedhæft nyt head SHA når grønt.
Blocker review (REQUEST_CHANGES):
- **blocker:** `frontend/angular/src/app/features/host/host-shell.component.ts` introducerer regression i host-flow.
- På branch `feat/issue-191-route-session-guards` fejler host-specs lokalt:
- `HostShellComponent gameplay wiring > runs startRound transition and refreshes session details`
- `... > wires showQuestion, mixAnswers and calculateScores ...`
- `... > runs next-round transition without reload ...`
- Kommando kørt: `cd frontend/angular && npm test`
- Resultat: 3 failing tests i `src/app/features/host/host-shell.component.spec.ts`.
Konsekvens: PR er ikke merge-klar før host-regressionen er rettet og tests er grønne.
Forslag til fix-retning:
1. Bevar/retabler eksisterende host refresh-semantik i `startRound`/phase-overgange, så der fortsat sker forventet efterfølgende GET-refresh.
2. Opdater route/session-guard integration så den ikke ændrer runtime-adfærd for eksisterende host actions.
3. Kør mindst `npm test` i `frontend/angular` og vedhæft nyt head SHA når grønt.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Implements #191.
No backend contract changes.
LGTM ✅
Review notes:
No blockers found.
Blocker review (REQUEST_CHANGES):
frontend/angular/src/app/features/host/host-shell.component.tsintroducerer regression i host-flow.feat/issue-191-route-session-guardsfejler host-specs lokalt:HostShellComponent gameplay wiring > runs startRound transition and refreshes session details... > wires showQuestion, mixAnswers and calculateScores ...... > runs next-round transition without reload ...cd frontend/angular && npm testsrc/app/features/host/host-shell.component.spec.ts.Konsekvens: PR er ikke merge-klar før host-regressionen er rettet og tests er grønne.
Forslag til fix-retning:
startRound/phase-overgange, så der fortsat sker forventet efterfølgende GET-refresh.npm testifrontend/angularog vedhæft nyt head SHA når grønt.Official review-state: APPROVED.