feat: Add project frontend API with tests and fix backend project API…

[Sma1lboy]

… (#25)

Summary by CodeRabbit

• New Features

  • Introduced a comprehensive setup for a Next.js application with TypeScript, including configuration files for ESLint, PostCSS, Tailwind CSS, and TypeScript.
  • Added a new layout and home page component with responsive design and optimized image handling.
  • Implemented a utility function for managing Tailwind CSS class names.
  • Created a JSON configuration file for component imports and Tailwind CSS settings.

• Documentation

  • Created a README file outlining project setup, development instructions, and deployment information.

• Chores

  • Added .gitignore to maintain a clean repository by excluding unnecessary files.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request introduces several new configuration and setup files for a React TypeScript project using Next.js. Key additions include ESLint and PostCSS configurations, a Tailwind CSS setup, and a TypeScript configuration file. Additionally, a README file provides essential project instructions, while various utility functions and components are defined to enhance the application's functionality and styling. Overall, these changes establish a foundational structure for the project, ensuring adherence to best practices and modern development standards.

Changes

File Path	Change Summary
backend/react-ts-template/.eslintrc.json	New ESLint configuration extending next/core-web-vitals and next/typescript.
backend/react-ts-template/.gitignore	New .gitignore file specifying files and directories to ignore, including node_modules and build outputs.
backend/react-ts-template/README.md	New README file with project setup instructions, usage of next/font, and deployment guidance.
backend/react-ts-template/components.json	New JSON configuration for React TypeScript template, defining style, server components, and Tailwind CSS settings.
backend/react-ts-template/next.config.ts	New Next.js configuration file with a placeholder for configuration options.
backend/react-ts-template/package.json	New package.json file specifying project metadata, scripts, dependencies, and devDependencies.
backend/react-ts-template/postcss.config.mjs	New PostCSS configuration file using Tailwind CSS plugin.
backend/react-ts-template/src/app/globals.css	New CSS file importing Tailwind's layers and defining CSS custom properties for theming.
backend/react-ts-template/src/app/layout.tsx	New root layout component for the Next.js application, defining metadata and rendering structure.
backend/react-ts-template/src/app/page.tsx	New Home component with layout and links for project documentation and deployment.
backend/react-ts-template/src/lib/utils.ts	New utility function cn for managing class names with clsx and tailwind-merge.
backend/react-ts-template/tailwind.config.ts	New Tailwind CSS configuration enabling dark mode and custom theme colors.
backend/react-ts-template/tsconfig.json	New TypeScript configuration file defining compiler options and module resolution.

Poem

In the land of code where rabbits play,
New configs and files have come our way!
With Tailwind and TypeScript, we hop with glee,
Building a project as bright as can be.
So let’s code and create, with joy in our hearts,
For every new change is where magic starts! 🐇✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 eslint (1.23.1)

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

backend/react-ts-template/next.config.ts

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the config "next/core-web-vitals" to extend from. Please check that the name of the config is correct.

The config "next/core-web-vitals" was referenced from the config file in "/backend/react-ts-template/.eslintrc.json".

If you still have problems, please stop by https://eslint.org/chat/help to chat with the team.

---

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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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 using 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.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.