Changed the OrgContribution Code from Jest to Vitest

[Akshat76845]

What kind of change does this PR introduce?
Changed the code from Jest to Vitest

Issue Number:

Fixes #2564

If relevant, did you update the documentation?

Summary
This PR addresses the following issues:
Changed the code from Jest to Vitest

Does this PR introduce a breaking change?
No

Have you read the contributing guide?
Yes

Summary by CodeRabbit

• New Features

  • Introduced new configuration files for various tools and workflows, enhancing project structure and automation.
  • Added comprehensive localization support for multiple languages including English, French, Hindi, Spanish, and Chinese.
  • Implemented a detailed GraphQL schema for managing action items, events, and users with robust error handling and authorization mechanisms.

• Documentation

  • Added new documentation files including installation guides, contribution guidelines, and style guides to improve clarity for contributors and users.

• Bug Fixes

  • Updated various files to improve linting, formatting, and error handling across the project.

• Chores

  • Removed obsolete files and configurations to streamline the project structure and enhance maintainability.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request introduces comprehensive configuration and documentation updates for the Talawa Admin project. The changes include setting up new configuration files for various tools like CodeRabbit, Docker, ESLint, and Vite, adding localization files for multiple languages, updating GitHub workflows, and enhancing project documentation. The modifications aim to improve development workflows, testing processes, and internationalization support.

Changes

File/Directory	Change Summary
.coderabbit.yaml	New configuration file for CodeRabbit AI review settings
.dockerignore	New file to exclude unnecessary files from Docker builds
.env.example	Added environment variable template for local development
.eslintignore	Updated to exclude specific files from linting
.eslintrc.json	Enhanced ESLint configuration with new plugins and rules
.github/workflows/	Multiple new and updated workflow files for CI/CD processes
Dockerfile	New Docker configuration for application deployment
public/locales/	Added localization files for English, French, Hindi, Spanish, and Chinese
package.json	Significant updates to dependencies, scripts, and project configuration
Configuration files	Added babel.config.cjs, vite.config.ts, jest.config.js
Documentation	Updated README.md, CONTRIBUTING.md, INSTALLATION.md, and added new documentation files

Assessment against linked issues

Objective	Addressed	Explanation
Refactor src/screens/OrgContribution from Jest to Vitest [#2564]	❓	Partial configuration changes made, but specific test refactoring not visible in this PR

Possibly related issues

• Refactor: src/screens/UserPortal/Organizations from Jest to Vitest #2575: Refactoring src/screens/UserPortal/Organizations from Jest to Vitest
• Refactor: src/screens/OrgSettings from Jest to Vitest #2567: Refactoring src/screens/OrgSettings from Jest to Vitest
• Refactor: src/screens/UserPortal/Donate from Jest to Vitest #2573: Refactoring src/screens/UserPortal/Donate from Jest to Vitest

Possibly related PRs

• Refactor: src/screens/UserPortal/Volunteer/Actions from Jest to Vitest #2619: Refactoring tests from Jest to Vitest
• Refactor Tests: Migrate src/screens/UserPortal/UserScreen/UserScreen.tsx from Jest to Vitest #2632: Migrating tests to Vitest
• github worflow format fix #2650: GitHub workflow format fixes
• Refactor: src/screens/OrganizationDashboard from Jest to Vitest #2678: Refactoring OrganizationDashboard component tests

Suggested reviewers

• @palisadoes

Poem

🐰 A Rabbit's Configuration Delight 🚀

Configs dance, workflows sing bright,
Locales bloom in languages light,
Docker builds with elegant might,
Vitest and Jest in testing's flight,
CodeRabbit watches with pure delight!

- Whiskers the DevOps Rabbit 🌈

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.

---

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 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.

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

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

1. We don't merge PRs with poor code quality.
   1. Follow coding best practices such that CodeRabbit.ai approves your PR.
2. We don't merge PRs with failed tests.
   1. When tests fail, click on the Details link to learn more.
   2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
   3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

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