-
Notifications
You must be signed in to change notification settings - Fork 131
style(fe): enable biome for frontend #3436
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
style(fe): enable biome for frontend #3436
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
How to use the Graphite Merge QueueAdd the label merge-queue 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. |
Code Review - PR #3436: Enable Biome for FrontendOverviewThis PR enables Biome linting/formatting for the frontend codebase, applying automated formatting across 27 files. The changes are primarily cosmetic improvements to code style and consistency. Positive Observations ✅
Issues & Concerns 🔍1. Missing Type Import (Minor Issue)Location: UseQueryOptions, // Should be: type UseQueryOptionsThis import is used as a type but doesn't have the 2. useEffect Dependency Array Warning (Potential Bug)Location: useEffect(() => {
// ...
}, deps);The 3. Biome Configuration Issue (Configuration)Location: "frontend/**/*.tsx",
"frontend/**/*.ts",
"!frontend/packages",The inclusion pattern seems redundant - the global patterns 4. Missing ESLint Rule for Import SortingThe PR sorts imports but doesn't show any Biome configuration for import sorting rules. Verify that Biome is configured to enforce this automatically, otherwise the formatting might diverge in future changes. Recommendations 📋
Security Considerations 🔒No security concerns identified. All changes are formatting-only. Performance Considerations ⚡No performance impact. The changes are purely cosmetic. Final AssessmentThis is a good PR that improves code consistency and maintainability. The changes are low-risk and align with modern TypeScript/React best practices. The main issues are minor and should be quick fixes:
Recommendation: Approve with minor changes requested. Note: This review was generated using the repository's coding standards from CLAUDE.md. |
More templates
@rivetkit/actor
@rivetkit/cloudflare-workers
@rivetkit/core
@rivetkit/db
@rivetkit/framework-base
@rivetkit/next-js
@rivetkit/react
rivetkit
@rivetkit/sql-loader
@rivetkit/engine-runner
@rivetkit/engine-runner-protocol
commit: |
Graphite Automations"Test" took an action on this PR • (11/10/25)1 assignee was added to this PR based on Kacper Wojciechowski's automation. |
34f4065
into
11-10-fix_fe_make_serverfull_serverless_switcher_working_again
* fix(fe): make serverfull/serverless switcher working again * fix(fe): persist ephemeral filters to local stroge (#3435) * style(fe): enable biome for frontend (#3436) * fix(fe): persist ephemeral filters to local stroge * style(fe): enable biome for frontend * feat(fe): add crash-loop status to actors (#3437) * fix(fe): persist ephemeral filters to local stroge * style(fe): enable biome for frontend * feat(fe): add crash-loop status to actors

No description provided.