chore: Configure linting and formatting tools for CI/CD

[NotYuSheng]

• Add Prettier and Stylelint to frontend with configuration files
• Add npm scripts for lint:fix, format, and lint:css:fix
• Add Spotless Maven plugin to backend for Google Java Format
• Configure auto-formatting for GitHub Actions workflows

[gemini-code-assist]

Summary of Changes

Hello @NotYuSheng, I'm Gemini Code Assist¹! 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 significantly enhances the project's code quality and consistency by implementing robust linting and formatting tools across both the backend and frontend. By integrating Spotless for Java and Prettier/Stylelint for JavaScript/CSS, the changes aim to standardize code style, reduce manual formatting efforts, and catch potential issues early in the development cycle. This setup is crucial for maintaining a clean codebase and facilitating automated checks within CI/CD pipelines, ultimately improving developer experience and project maintainability.

Highlights

• Backend Code Formatting: The Spotless Maven plugin has been integrated into the backend's pom.xml to enforce Google Java Format, ensuring consistent code style, automatic removal of unused imports, trimming of trailing whitespace, and newlines at the end of files.
• Frontend Code Formatting and Linting: Prettier has been added for automatic code formatting and Stylelint for CSS linting in the frontend. Dedicated configuration files (.prettierrc.json and .stylelintrc.json) have been introduced to define the specific formatting and linting rules.
• New Frontend npm Scripts: Several new npm scripts have been added to package.json to streamline frontend development workflows, including lint:fix for ESLint auto-fixing, format for Prettier, lint:css for Stylelint, and lint:css:fix for Stylelint auto-fixing.
• Dependency Updates: The package-lock.json file has been updated to include all new dependencies required by Prettier and Stylelint, along with their transitive dependencies.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces essential linting and formatting tools for both the frontend and backend, which is a fantastic improvement for code quality and consistency. The configurations for Prettier, Stylelint, and Spotless are well-implemented. My only suggestion is to integrate the Spotless plugin into the Maven build lifecycle to automatically enforce formatting checks, ensuring all code committed to the repository adheres to the defined style.

[gemini-code-assist]

To automatically enforce formatting during the build, consider binding Spotless to a build phase. This will fail the build if the code isn't formatted, ensuring consistency across the team. You can add an <executions> block after the <configuration> block to achieve this.

                </configuration>
                <executions>
                    <execution>
                        <id>spotless-check</id>
                        <phase>validate</phase>
                        <goals>
                            <goal>check</goal>
                        </goals>
                    </execution>
                </executions>