Implement format and linting ci/cd

[MartinBenediktBusch]

Description:

This pull request addresses the issue titled "Replicate the backend linter and format requirements in the frontend to ensure a minimum level of code consistency. Furthermore, implement .github/workflows for formatting and linting to have it checked at each commit."

Changes Made:

1. Linting and Formatting Setup:

   • Integrated ESLint and Prettier to enforce consistent code style and formatting in the frontend codebase.
   • Added .eslintrc.cjs configuration file to define linting rules using the @typescript-eslint plugin.
   • Configured rules to allow exceptions like @typescript-eslint/no-explicit-any and @typescript-eslint/no-var-requires as required.

2. GitHub Workflow Setup:

   • Implemented a GitHub Actions workflow check-formatting.yaml and lint.yaml to check code formatting and linting on each commit.
   • Workflow runs pnpm format (pnpm lint) command to ensure code adheres to formatting standards defined by Prettier.
   • Configured the workflow to run on pull requests targeting the develop and main branches to catch formatting issues before merging.

3. Fixed Linting and Formatting:

   • verified that the github actions catch the errors and solved them afterwards so that the tests pass.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
forum-frontend	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 8, 2024 8:35am