eslint-plugin-jest upgraded

[akathedeveloper]

What kind of change does this PR introduce?

This PR introduces a dependency update for ESLint and TypeScript linting tools, upgrading them to the latest stable versions for better code quality and support.

Issue Number:

Fixes #2180

Did you add tests for your changes?

No, this PR involves dependency updates. No new functionality or changes that require unit tests.

Snapshots/Videos:

N/A

If relevant, did you update the documentation?

No documentation updates were necessary.

Summary

This PR updates the following dependencies:

Updated @typescript-eslint/eslint-plugin from ^5.9.0 to ^8.5.0
Updated @typescript-eslint/parser from ^5.9.0 to ^8.5.0
Upgraded eslint-plugin-jest@^28.8.0

This resolves issues where @typescript-eslint/ban-types and other rules were not being found, improving overall code quality and adherence to TypeScript best practices.

Does this PR introduce a breaking change?

No, the changes only affect development dependencies and do not introduce breaking changes to the codebase.

Other information
These dependency updates will ensure proper linting and help in adhering to the latest TypeScript rules.
After merging, please run npm install or yarn install to update the dependencies locally.

Have you read the contributing guide?

Yes

Summary by CodeRabbit

• New Features
  • Upgraded dependencies for TypeScript ESLint tooling and Jest testing, enhancing development capabilities and performance.
• Bug Fixes
  • Improvements and bug fixes included in the updated versions of the dependencies.

[coderabbitai]

Walkthrough

The pull request introduces updates to the package.json file, specifically upgrading the versions of several dependencies, including @typescript-eslint/eslint-plugin, @typescript-eslint/parser, and eslint-plugin-jest. These updates aim to align the project with more recent versions of these packages, which may include enhancements, new features, and bug fixes.

Changes

File	Change Summary
package.json	Updated dependencies: @typescript-eslint/eslint-plugin to ^8.5.0, @typescript-eslint/parser to ^8.5.0, and eslint-plugin-jest to ^28.8.0.

Assessment against linked issues

Objective	Addressed	Explanation
Upgrade eslint-plugin-jest from 25.7.0 to 28.8.0 (##2180)	✅
Resolve previous failures in automated upgrade attempts (##2180)	✅
Review and potentially refactor files for compatibility (##2180)	❓	Unclear if all necessary files were reviewed.
Ensure documentation reflects changes made during upgrade (##2180)	❌	No documentation updates noted.

Possibly related issues

• Upgrade package eslint-plugin-jest from 25.7.0 to 28.6.0 #2135: The PR addresses the upgrade of eslint-plugin-jest, which aligns with the objectives of this issue.
• Upgrade jest and @types/jest #1942: The changes may relate to the need for upgrading ESLint packages as part of the broader dependency management.
• Upgrade package typescript from 4.9.5 to 5.4.5 #2016: The dependency updates may contribute to resolving issues related to previous failed attempts to upgrade TypeScript.

Poem

🐰 In the garden, changes bloom,
Dependencies shed their gloom.
Upgrades hop with joyful cheer,
New features dance, the path is clear.
With every version, we grow and play,
A brighter codebase, come what may! 🌼

Tip

Announcements

• The review status is no longer posted as a separate comment when there are no actionable or nitpick comments. In such cases, the review status is included in the walkthrough comment.
• We have updated our review workflow to use the Anthropic's Claude family of models. Please share any feedback in the discussion post on our Discord.
• Possibly related PRs: Walkthrough comment now includes a list of potentially related PRs to help you recall past context. Please share any feedback in the discussion post on our Discord.
• Suggested labels: CodeRabbit can now suggest labels by learning from your past PRs in the walkthrough comment. You can also provide custom labeling instructions in the UI or configuration file.
• Possibly related PRs, automatic label suggestions based on past PRs, learnings, and possibly related issues require data opt-in (enabled by default).

---

Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 478a142 and e97e446.

Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

Files selected for processing (1)

• package.json (1 hunks)

Additional comments not posted (3)

package.json (3)

115-115: Provide more context for the @typescript-eslint/eslint-plugin update.

The version of @typescript-eslint/eslint-plugin has been updated from ^5.9.0 to ^8.5.0, which is a major version bump.

Please provide more information about:

• The motivation behind this update
• Any specific issues or limitations with the previous version that this update addresses
• Any potential breaking changes or new features introduced by this update
• The impact of this update on the codebase and any necessary refactoring or changes in linting rules

---

116-116: Provide more context for the @typescript-eslint/parser update.

The version of @typescript-eslint/parser has been updated from ^5.9.0 to ^8.5.0, which is a major version bump.

Please provide more information about:

• The motivation behind this update
• Any specific issues or limitations with the previous version that this update addresses
• Any potential breaking changes or new features introduced by this update
• The impact of this update on the codebase and any necessary refactoring or changes in parsing rules
• The relationship between this update and the @typescript-eslint/eslint-plugin update, and if they need to be updated together

---

120-120: The eslint-plugin-jest update looks good!

The version of eslint-plugin-jest has been updated from ^25.3.4 to ^28.8.0, which is a major version bump. This update aligns with the primary objectives outlined in the PR:

• Leveraging new features and improvements in eslint-plugin-jest
• Resolving failures encountered during the previous automated upgrade attempt
• Refactoring the codebase to accommodate changes in the new major version
• Evaluating the necessity and usage of eslint-plugin-jest in the project

The linked issue provides good context and rationale for this update. Ensure that any relevant documentation is updated to reflect the changes.

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

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.

[github-actions]

Our Pull Request Approval Process

We have these basic policies to make the approval process smoother for our volunteer team.

Testing Your Code

Please make sure your code passes all tests. Our test code coverage system will fail if these conditions occur:

1. The overall code coverage drops below the target threshold of the repository
2. Any file in the pull request has code coverage levels below the repository threshold
3. Merge conflicts

The process helps maintain the overall reliability of the code base and is a prerequisite for getting your PR approved. Assigned reviewers regularly review the PR queue and tend to focus on PRs that are passing.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

1. comments in this PR or
2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

1. arbitrators of future discussions with other contributors about the validity of your changes
2. point of contact for evaluating the validity of your work
3. person who verifies matching issues by others that should be closed.
4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

1. PRs with issues not assigned to you will be closed by the reviewer
2. Fix the first comment in the PR so that each issue listed automatically closes

Other

1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
2. Read the CONTRIBUTING.md file make

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.45%. Comparing base (478a142) to head (e97e446).
Report is 1 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #2261   +/-   ##
========================================
  Coverage    97.45%   97.45%           
========================================
  Files          241      241           
  Lines         6882     6882           
  Branches      2000     2000           
========================================
  Hits          6707     6707           
  Misses         161      161           
  Partials        14       14           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[akathedeveloper]

@palisadoes Please review this.