Fix Team projection catch-up#595
Merged
potter-sun merged 2 commits intodevfrom May 8, 2026
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## dev #595 +/- ##
=======================================
Coverage 72.01% 72.02%
=======================================
Files 1255 1255
Lines 90723 90723
Branches 11877 11877
=======================================
+ Hits 65338 65341 +3
+ Misses 20703 20700 -3
Partials 4682 4682
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR completes the Console Web Team P0 frontend fixes around canonical Team identity and projection catch-up:
/teams/:scopeId/:teamIdand treats/teams/:scopeIdas a no-team-selected stateWhy
Team creation is write-side authoritative, while Team list/detail/member reads come from projected read models. In the real Garnet + Elasticsearch setup, the committed Team can be accepted before the read model is visible. Before this PR, the UI could immediately hit 404 or fail to show the created Team in list/detail, which made a successful create look broken.
Validation
npm --prefix apps/aevatar-console-web run tscnpm --prefix apps/aevatar-console-web run jest -- --selectProjects jsdom --runTestsByPath src/pages/teams/detail.test.tsx src/pages/teams/new.test.tsx src/shared/studio/api.test.ts src/shared/navigation/teamRoutes.test.ts src/shared/config/proxyConfig.test.ts src/pages/teams/home.test.tsx src/pages/runs/index.test.tsx --runInBandnpm --prefix apps/aevatar-console-web run jest -- --selectProjects node --runTestsByPath src/shared/config/proxyConfig.test.ts --runInBandgit diff --checkhttp://127.0.0.1:5173:POST /api/scopes/{scopeId}/teamsreturned201404200, and list contained the created TeamWatchman emitted a recrawl warning during Jest, but all targeted suites passed.
Issues
Closes #579
Closes #580
Closes #581
Closes #582
Closes #583
Closes #584
Refs #585