feat(FR-2688): migrate notification item VirtualFolderNode branch to Strawberry V2#6934
Merged
graphite-app[bot] merged 1 commit intomainfrom Apr 30, 2026
Conversation
This was referenced Apr 23, 2026
Contributor
Author
Contributor
Coverage report for
|
St.❔ |
Category | Percentage | Covered / Total |
|---|---|---|---|
| 🔴 | Statements | 8.78% (-0.01% 🔻) |
1857/21150 |
| 🔴 | Branches | 7.98% (-0.02% 🔻) |
1187/14866 |
| 🔴 | Functions | 5.14% (-0% 🔻) |
295/5735 |
| 🔴 | Lines | 8.52% (-0.01% 🔻) |
1749/20524 |
Show new covered files 🐣
St.❔ |
File | Statements | Branches | Functions | Lines |
|---|---|---|---|---|---|
| 🔴 | ... / BAIVFolderNotificationItem.tsx |
0% | 0% | 0% | 0% |
Test suite run success
865 tests passing in 40 suites.
Report generated by 🧪jest coverage report action from 7a7c311
Contributor
There was a problem hiding this comment.
Pull request overview
Migrates the vfolder-related notification item UI from the legacy VirtualFolderNode GraphQL type to Strawberry V2’s VFolder type.
Changes:
- Updated
BAIVFolderNotificationItemto read vfolder name fromVFolder.metadata.nameand to navigate usingtoLocalId(VFolder.id)in the/data?folder=...query param. - Updated
BAINodeNotificationItemfragment/type-switching to use... on VFolderand render the updated notification item component.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| react/src/components/BAIVFolderNotificationItem.tsx | Switches fragment from VirtualFolderNode → VFolder, uses metadata.name, and derives the folder query param from toLocalId(id). |
| react/src/components/BAINodeNotificationItem.tsx | Updates Node fragment and rendering logic to handle VFolder and pass the new fragment prop. |
Comments suppressed due to low confidence (1)
react/src/components/BAIVFolderNotificationItem.tsx:14
- The PR description still contains placeholders (e.g.,
resolves #NNN (FR-MMM)and unchecked template checklist items). Please replace these with the actual issue/Jira IDs and relevant validation/testing notes so the migration can be tracked and reviewed properly.
0a1150d to
00cf91a
Compare
1b1afab to
367890c
Compare
00cf91a to
3b0bc91
Compare
367890c to
25bbf35
Compare
3b0bc91 to
a61d9ad
Compare
25bbf35 to
4282f19
Compare
5 tasks
4282f19 to
e5290d8
Compare
24ada4a to
3eb2f5d
Compare
e5290d8 to
0a342fb
Compare
3eb2f5d to
9695c20
Compare
0a342fb to
5ae9335
Compare
5 tasks
5ae9335 to
46ee67e
Compare
05c1b1d to
fe08926
Compare
f06f603 to
77b09ac
Compare
77b09ac to
f6d48a0
Compare
0381546 to
2ab8da8
Compare
f6d48a0 to
35d9e6c
Compare
2ab8da8 to
fd60446
Compare
35d9e6c to
7a7c311
Compare
fd60446 to
e7a4aca
Compare
2dcc90f to
d05aa9e
Compare
e7a4aca to
45b447c
Compare
d05aa9e to
94c01ea
Compare
45b447c to
bbab28e
Compare
94c01ea to
c3f2778
Compare
bbab28e to
497ad1e
Compare
Merge activity
|
…Strawberry V2 (#6934) Resolves #6932 (FR-2688) ## Summary - Migrates `... on VirtualFolderNode` branch in `BAINodeNotificationItem` to `... on VFolder` (Strawberry V2). - Renames `BAIVirtualFolderNodeNotificationItem` -> `BAIVFolderNotificationItem` and adapts field access (`metadata.name`, `toLocalId(id)` replacing V1 `row_id`). ## Part of Epic FR-2572 - Migrate WebUI to Strawberry V2 GraphQL API. ## Notes - No backend change required; both `VirtualFolderNode` and `VFolder` implement `Node`. - No existing producer currently supplies a VFolder node ref into notifications (only `useStartSession.tsx` for sessions), so this PR is preparatory - it aligns the branch with the V2 schema for future consumers. - The unused `status` field selection was dropped from both the parent `BAINodeNotificationItemFragment` (V2 `VFolder.status` is `VFolderOperationStatus!`, which conflicted with sibling fragments where `status` is `String`) and the child fragment, because neither the original nor the migrated component actually read `node.status`. ## Verification - `bash scripts/verify.sh` -> ALL PASS ## Test plan - [ ] Existing session notifications continue to render correctly (regression check). - [ ] (Smoke) Add a temporary producer feeding a VFolder id through the Node fragment and confirm the branch resolves - not strictly required for merge, but confirms correctness.
497ad1e to
cd0ca53
Compare
c3f2778 to
2a84fd4
Compare
Base automatically changed from
04-24-feat_fr-2696_create_project_admin_data_page
to
main
April 30, 2026 03:14
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.

Resolves #6932 (FR-2688)
Summary
... on VirtualFolderNodebranch inBAINodeNotificationItemto... on VFolder(Strawberry V2).BAIVirtualFolderNodeNotificationItem->BAIVFolderNotificationItemand adapts field access (metadata.name,toLocalId(id)replacing V1row_id).Part of
Epic FR-2572 - Migrate WebUI to Strawberry V2 GraphQL API.
Notes
VirtualFolderNodeandVFolderimplementNode.useStartSession.tsxfor sessions), so this PR is preparatory - it aligns the branch with the V2 schema for future consumers.statusfield selection was dropped from both the parentBAINodeNotificationItemFragment(V2VFolder.statusisVFolderOperationStatus!, which conflicted with sibling fragments wherestatusisString) and the child fragment, because neither the original nor the migrated component actually readnode.status.Verification
bash scripts/verify.sh-> ALL PASSTest plan