project selector fixes

[Dhravya]

No description provided.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	supermemory-app	3e507df	Sep 19 2025, 07:25 PM

[Dhravya]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• project selector fixes #431 👈 (View in Graphite)
• formatting #430
• refetching logic change #429
• format browser extension #428
• newish get started page #427
• main

---

How to use the Graphite Merge Queue

Add the label Main to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[claude]

Code Review Feedback

Thank you for the pull request! I've reviewed the changes and have the following feedback:

✅ Code Quality & Style

• Excellent formatting consistency: The changes properly align with the Biome configuration, converting from semicolons to the "asNeeded" style (removing unnecessary semicolons)
• Clean formatting: All import statements and variable declarations now follow the consistent no-semicolon pattern
• Proper adherence to project conventions: The changes match the repository's Biome configuration which specifies "semicolons": "asNeeded"

🔍 Analysis Summary

This PR appears to be a pure formatting change that:

• Removes semicolons from import statements and variable declarations
• Maintains identical functional logic
• Improves code consistency across the project selector components

⚠️ Minor Observations

1. Import path inconsistency (apps/web/hooks/use-project-mutations.ts:3):

   • Uses @lib/api instead of @repo/lib/api
   • Consider standardizing import paths across the monorepo for consistency

2. Type safety consideration:

   • The queryClient.getQueryData<any[]> usage on line 65-67 in the mutations file could benefit from proper typing instead of any[]

🎯 Recommendations

1. Consider running the formatter command: After this PR, run bun run format-lint to ensure all files in the repository follow the same formatting standards
2. Batch formatting changes: For future formatting updates, consider applying them repository-wide to maintain consistency

🛡️ Security & Performance

• ✅ No security concerns identified
• ✅ No performance impact from these formatting changes
• ✅ No functional changes that could introduce bugs

📝 Test Coverage

• Since these are purely formatting changes with no functional modifications, existing test coverage should remain adequate
• No additional tests required for this change

💡 Overall Assessment

This is a clean, well-executed formatting improvement that enhances code consistency. The changes align perfectly with the project's Biome configuration and maintain all existing functionality.

Status: ✅ Approved - Ready to merge once any import path inconsistencies are addressed if desired.