feat(files): folders, multiselect, vfs update#4572
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
PR SummaryMedium Risk Overview Updates existing file upload/manage flows to be folder-aware (folder metadata on presigned/register/formdata upload; Refactors several existing endpoints (credentials, folders, workflows, schedules, tables/knowledge restores, MCP server/tool routes, workspace API key create, v1 file delete) to call Reviewed by Cursor Bugbot for commit a3d1010. Configure here. |
Greptile SummaryThis PR adds folder support, multi-select, and drag-and-drop to the workspace files view, alongside a comprehensive VFS update. It introduces new API routes, a new
Confidence Score: 5/5Safe to merge — all critical concerns from earlier review rounds are fully addressed in the latest commit. All previously flagged issues (advisory-lock placement, 23505 mapping to clean 409s, restoreWorkspaceFileFolder nulling out parentId when parent is still archived, VFS folderPath field separation, download-route error leak) have been resolved. Remaining feedback is performance and UX polish that does not block correctness for normal usage paths. workspace-file-folder-manager.ts — updateWorkspaceFileFolder still resolves the return path via per-ancestor SELECTs; files.tsx — stale folderId URL shows an empty table without redirecting Important Files Changed
Reviews (16): Last reviewed commit: "improve error codes" | Re-trigger Greptile |
|
@greptile |
|
bugbot run |
|
@greptile |
|
bugbot run |
|
@greptile |
|
bugbot run |
|
bugbot run |
|
@greptile |
|
bugbot run |
|
@greptile |
|
bugbot run |
|
@greptile |
|
@cursor review |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 90a6050. Configure here.
|
@greptile |
|
bugbot run |
|
bugbot run |
|
@greptile |
|
bugbot run |
|
@greptile |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit a3d1010. Configure here.
| return NextResponse.json( | ||
| { success: false, error: result.error }, | ||
| { status: result.errorCode === 'conflict' ? 409 : 400 } | ||
| ) |
There was a problem hiding this comment.
Folder endpoints return 400 for internal server errors
Medium Severity
The workspace file folder error-status mapping defaults to 400 for unknown or internal errorCode values, unlike the sibling file endpoints (e.g. performRenameWorkspaceFile) that correctly default to 500. If the orchestration layer returns an unexpected internal error, the client receives a 400 Bad Request instead of 500 Internal Server Error, misattributing the fault to the client and making debugging harder.
Additional Locations (2)
Reviewed by Cursor Bugbot for commit a3d1010. Configure here.


Summary
Add folders, multiselect for files, update VFS to work with this.
Type of Change
Testing
Tested manually
Checklist