chore: use biome to format code #567
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
That's fantastic, thank you @ematipico ! |
micheleriva
approved these changes
Dec 7, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi peeps, how are you? 👋
I am proposing an alternative to Prettier, Biome. https://biomejs.dev/formatter/
My idea is to slowly adopt the tool, and slowly adopt also linter (alongside eslint for the time being) and import sorting.
The PR only applies changes to
plugin-vitepressas a starting point. I am happy to guide the migration to the rest of the code base.While I was replacing it, I realized that prettier isn't used in the code base, so I changed the biome options to meet
ts-standard- the library that Michele uses. However, there are still some differences due to some inconsistencies in the code.Let me know what you guys think. If the change is welcomed, we could use this PR to decide the formatting style of the code base.
Thank you :)