Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Task #221910 : React JS Coding Standards Conventions #1

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

rushi-tekdi
Copy link

@rushi-tekdi rushi-tekdi commented Jun 24, 2024

Pull Request Description

Description:

This PR introduces a comprehensive set of coding standards and conventions for our React JS codebase. The goal is to ensure consistency, maintainability, and high quality across the project by adhering to established best practices and guidelines.

Summary of Changes:

  1. Code Style Guide

    • Added a detailed .md documents outlining the coding standards and conventions for React JS.
    • Includes guidelines on component structure, naming conventions, state management, hooks usage, and JSX syntax.
  2. Linter and Formatter Configurations

    • Configured ESLint with relevant plugins and rules tailored for React JS.
    • Configured Prettier for consistent code formatting.
    • Added configuration files .eslintrc.json and .prettierrc.
  3. NPM Scripts

    • Added scripts to package.json for running linters and formatters locally:
      {
        "scripts": {
          "lint": "eslint 'src/**/*.{js,jsx}'",
          "lint:fix": "eslint 'src/**/*.{js,jsx}' --fix",
          "format": "prettier --write 'src/**/*.{js,jsx,json,css,md}'"
        }
      }
  4. Documentation

    • Included detailed instructions on setting up and using ESLint and Prettier in the .md document.
    • Provided examples and best practices to help developers adhere to the standards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant