Eslint compatible with different react version in eslint-plugin-react settings

[aralovelace]

Jira Ticket Link / Motivation

Fix the warning while running yarn lint

Warning: React version not specified in eslint-plugin-react settings. See https://github.com/jsx-eslint/eslint-plugin-react#configuration .

Summary of changes

This pull request includes a configuration change to the ESLint settings in the .eslintrc.cjs file. The change automatically detects the React version being used in the project.

• .eslintrc.cjs: Added a settings section to automatically detect the React version.

How do you manually test this?

Reviewer Tasks (optional)

Merge/Deploy Checklist

• Written automated tests for implemented features/fixed bugs
• Rebased and squashed commits
• Commits have clear descriptions of their changes
• Checked for any performance regressions

Frontend Checklist

• No frontend changes in this PR
• Added before/after screenshots for changes
• Tested on different platforms/browsers with Browserstack
• Compared with the initial design / our brand guidelines
• Checked the code for accessibility issues (VoiceOver User Guide)?

Summary by CodeRabbit

• Chores
  • Updated ESLint configuration to automatically detect React version
  • Improved project linting setup

[coderabbitai]

Walkthrough

The pull request modifies the ESLint configuration file by adding a new settings section that enables automatic React version detection. This enhancement allows the ESLint plugin to dynamically identify the React version used in the project, ensuring more accurate and adaptive linting rules without changing the existing configuration.

Changes

File	Change Summary
.eslintrc.cjs	Added settings configuration with react.version set to "detect"

Suggested Reviewers

• jamiehenson

🐰 A Linting Rabbit's Delight

With version detect so bright,
ESLint now sees React's might
Configuration clean and neat
Making code review a treat!

Hop, hop, hooray! 🎉

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7d11ce2 and 4a68bb0.

📒 Files selected for processing (1)

• .eslintrc.cjs (1 hunks)

🔇 Additional comments (1)

.eslintrc.cjs (1)

30-34: LGTM! The changes correctly implement automatic React version detection.

The addition of the settings section with react.version: "detect" follows ESLint's recommended approach and should resolve the warning about unspecified React version.

Let's verify that the warning is resolved by running ESLint:

✅ Verification successful

✅ React version warning has been resolved

The ESLint configuration is working correctly with react.version: "detect", and no React-related warnings are present in the output.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify that the ESLint warning about React version is resolved
# Expected: No warnings about unspecified React version

# Install dependencies
npm install --save-dev eslint-plugin-react

# Run ESLint and check for React version warnings
npx eslint . 2>&1 | grep -i "Warning.*React.*version"

# Exit code of the grep command will be 1 if no warnings are found (expected result)
if [ $? -eq 1 ]; then
  echo "✅ No warnings about React version detected"
else
  echo "❌ Warning about React version still present"
fi

Length of output: 608

---

Script:

#!/bin/bash
# Install all necessary dependencies
npm install --save-dev eslint eslint-plugin-react react

# Show ESLint version and loaded configuration
echo "ESLint version and config:"
npx eslint --version
npx eslint --print-config .eslintrc.cjs

# Run ESLint with detailed output
echo -e "\nESLint execution results:"
npx eslint . --no-ignore 2>&1 || true

# Specifically check for React-related messages
echo -e "\nChecking for React-related messages:"
npx eslint . --no-ignore 2>&1 | grep -i "react" || echo "No React-related messages found"

Length of output: 27980

---

🪧 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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.

[kennethkalmer]

Nice! Can confirm the warning is gone