Add BiomeJS for Linting and Formatting JavaScript relates to #1295 #1299
Reference in New Issue
Block a user
Delete Branch "change-chore-add-linting-and-formatting-for-js-code"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary:
Why BiomeJS:
Open Points:
@@ -0,0 +1,34 @@{Currently, our
.editorconfighas:Will this conflict since it's using tabs?
@oxdev03 thanks for the comprehensive integration here! Haven't used Biome yet, but seems like an overall good fit for the project regarding simplicity and performance.
Just jotting down the steps I took to get my local environment setup with VSCode for others:
npm installto install dev dependencies@@ -52,6 +52,26 @@ jobs:- name: Lint code for consistent styleTo keep this as low-overhead as possible, I think we should just enforce the linting:
The formatting is a nice addition that I'll be using locally, but don't want that to be a requirement for new contributors and also for pushing hot fixes directly to
main(our internal team does this occasionally to fix tiny bugs)@@ -0,0 +1,34 @@{good point, indentStyle overrides the imported editorconfig. I removed it, so its consistent across all files.
@@ -52,6 +52,26 @@ jobs:- name: Lint code for consistent stylechanged it, even if its not a best practice.
yes , the contributor would also need to have nodejs installed. I added the autosave to the vscode/settings.json file to the project.
If the DevContainer is used no additional steps are required.
@@ -52,6 +52,26 @@ jobs:- name: Lint code for consistent style@oxdev03 correct, not best practice and that's 100% fine at our stage/size
Looks good! Thanks for setting this up!