-
-
Notifications
You must be signed in to change notification settings - Fork 658
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
feat: biome lint frontend #4903
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
f36c0f4
to
66bf6cc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I love it. Does it work?
Some thoughts:
- No changes to package.json in frontend,
doesn't that mean that applyingyarn lint
in the frontend folder will still call eslint? - I see we're applying backend's preference for single quotes to frontend as well. Is React JSX/TSX fine with that?
15bc232
to
7334ed6
Compare
Thank you for those good questions @chriswk
Seems to work fine now and I finally fixed the failing tests. Mind testing locally on your machine just to be sure?
You're right. This was addressed in f0f33c1 It's not a big deal since it is super fast, but it would be great if we could drop these commands in frontend altogether and rely only on the top level ones, since those cover everything. It's also weird that they act differently in backend and frontend.
AFAIK it's totally fine. |
Ran tests locally, everything seems to be green. Don't worry about Codacy at the moment. I think we either need to have a close look at the config or just drop it. |
Tiny refactor that bubbles promises instead of using `return await`. Should be more consistent with the rest of the changes in #4903
Follows up on #4853 to add Biome to the frontend as well.
Added a few
biome-ignore
to speed up the process but we may want to check and fix them in the future.