Rework pre-commit prettier to biome

[CoMPaTech]

Wrt comment @bouwew in plugwise/plugwise_usb-beta#143 and status of pre-commit/prettier

Summary by CodeRabbit

• New Features

  • Transitioned to using Biome for code formatting and linting, enhancing code quality management.
  • Added support for additional dependencies for improved functionality.

• Bug Fixes

  • Updated the Prettier hook configuration to reflect the new repository and ID, ensuring proper integration and functionality.

[coderabbitai]

Walkthrough

The pre-commit hooks in the project have been updated to utilize the Biome tool instead of Prettier, enhancing code formatting and linting capabilities. This change includes updating the repository source, modifying the hook ID, and introducing a new dependency on the Biome package. These adjustments signify a strategic move towards improved code quality management.

Changes

Files	Change Summary
.pre-commit-config.yaml	Updated Prettier to Biome (https://github.com/biomejs/pre-commit), changed hook ID from prettier to biome-lint, modified name to reflect Biome's capabilities, and added dependency on @biomejs/biome@1.8.3.

Poem

🐰 In the code garden, changes bloom,
Biome's magic sweeps the gloom.
From Prettier's dust, we take flight,
Formatting brightens, a joyful sight!
With each commit, our style refined,
A happy rabbit, code aligned! ✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[CoMPaTech]

Half-expecting pre-commit.ci to fail now :)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[CoMPaTech]

Half-expecting pre-commit.ci to fail now :)

And biome just works on pre-commit.ci :P

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 360a363 and e6582e1.

Files selected for processing (1)

• .pre-commit-config.yaml (1 hunks)

Additional comments not posted (4)

.pre-commit-config.yaml (4)

61-61: Verify the repository change.

The repository URL has been updated from Prettier to Biome. Ensure that Biome meets all the project's formatting and linting requirements.

---

64-64: Verify the hook ID change.

The hook ID has been updated from prettier to biome-lint. Ensure that the new hook ID is correctly configured and functions as expected.

---

66-66: Verify the hook name change.

The hook name has been updated to reflect the use of Biome instead of Prettier. Ensure that Biome provides the expected improvements and functionality.

---

65-65: Verify the additional dependency.

The new dependency @biomejs/biome@1.8.3 has been added. Ensure that this dependency is correctly specified and compatible with the project.