Conversation
Signed-off-by: rohan-019 <rohan18126@gmail.com>
Summary of ChangesHello @rohan-019, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request resolves a linter error by transitioning the project's JSON formatting from a custom Python script to the Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
|
cc @jbampton |
There was a problem hiding this comment.
Code Review
This pull request replaces a manual JSON formatting implementation with a call to the biome tool. This is a good change for standardization. However, the new implementation has a flaw in its error handling: a failure in the optional formatting step will cause the entire script to exit. My review includes a suggestion to fix this by handling formatting errors gracefully, ensuring the script can continue even if biome fails to format a file.
jbampton
left a comment
There was a problem hiding this comment.
https://biomejs.dev/recipes/git-hooks/#pre-commit
Can we integrate all this with pre-commit ?
hey @jbampton, |
Signed-off-by: rohan-019 <rohan18126@gmail.com>
Co-authored-by: John Bampton <jbampton@users.noreply.github.com>
Co-authored-by: John Bampton <jbampton@users.noreply.github.com>
|
Good improvement replacing the custom JSON formatter with Biome for consistency. One concern: the current implementation exits if Biome fails, which makes the whole script stop. It would be better to handle errors gracefully (log a warning, continue execution). Also nice to see the pre-commit integration being added. |
Signed-off-by: rohan-019 <rohan18126@gmail.com>
Description
fixes super linter error that found in biome_formate
Related Issue
Fixes: #1078
Proposed Changes
Outline the changes made in this pull request and explain their purpose.
Checklist