Refactor : src/components/AgendaItems/AgendaItemsCreateModal from Jest to Vitest #2489

[Ramneet04]

Refactored src/components/AgendaItems/AgendaItemsCreateModal.test.tsx to src/components/AgendaItems/AgendaItemsCreateModal.spec.tsx

Issue: #2489 : #2489

Changes Implemented:

Refactored the testing framework from Jest to Vitest in AgendaItemsCreateModal.test.tsx.
Updated import statements, mocking methods, and assertions to align with Vitest conventions.
Verified compatibility with the existing codebase using Vitest.

• Renamed the test file:
  From AgendaItemsCreateModal.test.tsx → AgendaItemsCreateModal.spec.tsx to follow the naming convention for Vitest.
• Ran all tests successfully under the Vitest environment.
  Refactor : src/components/AgendaItems/AgendaItemsCreateModal.test.tsx from Jest to Vitest #2489

Other information
I have read the previous refactor PR and tried to keep things as uniform as possible.
Please suggest any other changes if required.

Summary by CodeRabbit

Release Notes

• New Features

  • Introduced a new configuration file for YAML language server settings.
  • Added a template for environment variables necessary for local development.
  • Implemented a new README for GitHub workflows outlining contribution guidelines.
  • Created a comprehensive code style guide and updated the contribution documentation.
  • Added localization support with new JSON files for multiple languages (English, French, Hindi, Spanish, Chinese).
  • Introduced a setup script for initializing environment variables and configurations.

• Bug Fixes

  • Enhanced error handling in various scripts and components.

• Documentation

  • Updated multiple documentation files for better clarity and navigation.
  • Added tables of contents to several guides for easier access.

• Chores

  • Updated project dependencies and configuration files to align with modern practices.
  • Introduced new scripts for automated tasks and checks during development.

• Tests

  • Added new test cases for various functionalities to ensure robust error handling and performance.

[coderabbitai]

Walkthrough

The pull request introduces multiple changes across various files, including the addition of configuration files for YAML language servers, environment variables, ESLint settings, and GitHub workflows. It also includes new localization JSON files for multiple languages and updates to documentation files. Additionally, several test files are refactored to transition from Jest to Vitest, enhancing the testing framework used in the project. The changes aim to improve configuration management, localization support, and testing practices.

Changes

File Path	Change Summary
.coderabbit.yaml	New configuration file for YAML language server settings.
.env.example	New template for environment variables for local development.
.eslintignore	Added exclusion for src/components/CheckIn/tagTemplate.ts.
.eslintrc.json	Updated ESLint configuration to enhance TypeScript support and integrate Prettier.
.github/ISSUE_TEMPLATE/bug-report.md	Updated metadata and added sections for additional details and internship candidates.
.github/ISSUE_TEMPLATE/feature-request.md	Updated metadata and added section for internship candidates.
.github/dependabot.yaml	New configuration file for automated dependency updates.
.github/pull_request_template.md	Modified pull request template to clarify branching strategy and include new fields.
.github/workflows/README.md	New README file outlining guidelines for GitHub workflows.
.github/workflows/auto-label.json5	New configuration for label synonyms and default labels.
.github/workflows/check-tsdoc.js	New script to validate TypeScript files for TSDoc comments.
.github/workflows/codeql-codescan.yml	New CodeQL analysis workflow for automated code analysis.
.github/workflows/pull-request.yml	New workflow for handling pull requests with various checks.
public/locales/en/common.json	New localization file for English UI strings.
public/locales/fr/common.json	New localization file for French UI strings.
public/locales/hi/common.json	New localization file for Hindi UI strings.
public/locales/sp/common.json	New localization file for Spanish UI strings.
public/locales/zh/common.json	New localization file for Chinese UI strings.
package.json	Updated project name, version, and dependencies; added new scripts for Vite.
setup.ts	New setup script for configuring environment variables.
Various test files	Refactored from Jest to Vitest, including tests for components in the src/components directory.

Possibly related issues

• Refactor : src/components/AgendaItems/AgendaItemsCreateModal.test.tsx from Jest to Vitest #2489: Refactoring agenda items tests to Vitest aligns with the migration efforts in this PR.
• Refactor : src/components/AgendaItems/AgendaItemsPreviewModal.test.tsx from Jest to Vitest #2490: Similar refactoring of tests for agenda items preview modal, relevant to the overall migration to Vitest.
• Refactor : src/components/AgendaItems/AgendaItemsUpdateModal.test.tsx from Jest to Vitest #2491: Refactoring tests for agenda items update modal, part of the migration to Vitest.
• Refactor : src/components/AgendaItems/AgendaItemsContainer.test.tsx from Jest to Vitest #2488: Refactoring tests for agenda items container, relevant to the migration efforts.
• Refactor : src/components/CheckIn/CheckInModal.test.tsx from Jest to Vitest #2494: Refactoring tests for check-in modal, part of the Jest to Vitest migration.
• Refactor : src/components/CheckIn/CheckInWrapper.test.tsx from Jest to Vitest #2495: Refactoring check-in wrapper tests, relevant to the overall migration strategy.
• Refactor : src/components/CheckIn/TableRow.test.tsx from Jest to Vitest #2496: Refactoring check-in table row tests, part of the migration to Vitest.
• Refactor: src/screens/EventManagement from Jest to Vitest #2546: Refactoring event management tests, relevant to the migration to Vitest.

Possibly related PRs

• coderabbit yaml file #1991: Introduces a new .coderabbit.yaml configuration file, related to the main PR.
• develop branch - coderabbit yaml file #1997: Adds a .coderabbit.yaml file with settings for the YAML language server, relevant to the main PR.
• Fixes: Translations Are Not Correctly Tested in Our PR Workflow  #2263: Involves changes to translation files, which may relate to the main PR's localization efforts.
• feat: Workflow changes which will label issues automatically as per #2256 #2390: Introduces automatic labeling based on keywords, which could relate to review settings in the main PR.
• fix: pull-request.yml to ignore actions on ignore-sensitive-files-pr and Introspection workflow #2391: Modifies workflow to check for sensitive files, relevant to review processes outlined in the main PR.
• Updated pr template with checklist #2454: Updates the pull request template to include checklists, aligning with review-related settings in the main PR.
• Updated pr template for develop-postgress branch #2458: Updates the pull request template for the develop-postgres branch, relevant to review processes in the main PR.

Suggested labels

refactor

Suggested reviewers

• varshith257
• pranshugupta54
• AVtheking

🐰 "In the code we hop and play,
New configs brighten up the day!
From Jest to Vitest, we take a leap,
With translations in a colorful heap!
Join us now, let's make it right,
Together we'll code, in pure delight!" 🐇✨

---

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. (Experiment)
• @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

[coderabbitai]

Actionable comments posted: 48

🧹 Outside diff range and nitpick comments (59)

.github/workflows/stale.yml (4)

1-11: Remove trailing spaces in documentation header

The documentation header is well-structured, but contains trailing spaces that should be removed.

-# Please read the README.md file in this directory that defines what should 
+# Please read the README.md file in this directory that defines what should

🧰 Tools

🪛 yamllint (1.35.1)

[error] 6-6: trailing spaces

(trailing-spaces)

---

18-21: Remove trailing spaces in permissions section

Clean up the formatting by removing trailing spaces.

permissions:
  issues: write
-  pull-requests: write  
-  
+  pull-requests: write

🧰 Tools

🪛 yamllint (1.35.1)

[error] 20-20: trailing spaces

(trailing-spaces)

---

[error] 21-21: trailing spaces

(trailing-spaces)

---

14-16: Consider reducing the frequency of stale checks

The workflow runs daily at midnight ("0 0 * * *"), which might be more frequent than necessary for checking stale items, especially since the stale threshold is 10 days. Consider running it less frequently, such as weekly, to reduce GitHub Actions usage.

on:
  schedule:
-  - cron: "0 0 * * *"
+  - cron: "0 0 * * 0"  # Run weekly on Sundays at midnight

---

41-42: Consider additional exemption labels

While 'wip' is exempted, consider adding more common labels that indicate active work or deliberate long-term open status.

        exempt-pr-labels: 'wip'
-        exempt-issue-labels: 'wip'
+        exempt-issue-labels: 'wip,help wanted,good first issue,documentation'

public/locales/en/errors.json (2)

2-2: Simplify error message and fix punctuation

The current message has redundant punctuation and an unnecessary question.

-  "talawaApiUnavailable": "Talawa-API service is unavailable!. Is it running? Check your network connectivity too.",
+  "talawaApiUnavailable": "Talawa-API service is unavailable. Please check your network connectivity."

---

5-5: Fix spelling consistency

Use American English spelling to maintain consistency.

-  "notAuthorised": "Sorry! you are not Authorised!",
+  "notAuthorized": "Sorry, you are not authorized!"

public/locales/fr/errors.json (1)

4-4: Remove extra space before placeholder

There's an unnecessary space before the {{msg}} placeholder.

-  "unknownError": "Une erreur inconnue est survenue.  {{msg}}",
+  "unknownError": "Une erreur inconnue est survenue. {{msg}}",

public/locales/en/translation.json (3)

164-164: Fix typos in messages

There are typos in some messages:

• "enale" should be "enable" (line 164)
• "can't" should be consistent with other contractions

Apply this diff to fix the typos:

-    "manageFeaturesInfo": "Creation Successful ! Please select features that you want to enale for this organization from the plugin store.",
+    "manageFeaturesInfo": "Creation Successful! Please select features that you want to enable for this organization from the plugin store.",
-    "passCantBeEmpty": "Password can't be empty",
-    "passNoMatch": "New and Confirm password do not match.",
+    "passCantBeEmpty": "Password cannot be empty",
+    "passNoMatch": "New and confirm password do not match.",

Also applies to: 876-876, 877-877

---

1-1483: Consider organizing translations by feature modules

The translation file is quite large and contains all translations in a single file. Consider splitting it into smaller feature-based modules for better maintainability.

Suggested structure:

locales/
  en/
    common.json       # Common/shared translations
    auth.json        # Authentication related translations
    events.json      # Event related translations
    organizations.json # Organization related translations
    ...

This would make it easier to:

1. Maintain translations for specific features
2. Load translations on demand
3. Work on translations in parallel
4. Review changes to specific features

---

38-38: Ensure consistent message casing and punctuation

There are inconsistencies in message casing and punctuation throughout the file:

• Some messages start with capital letters while others don't
• Some messages end with periods while others don't
• Some messages use different quotation marks

Consider establishing and following these conventions:

1. Start all error messages with capital letters
2. End all error messages with periods
3. Don't end UI labels with periods
4. Use consistent quotation marks (preferably none unless part of the message)

Also applies to: 71-71, 228-228, 229-229, 230-230, 876-876, 877-877

public/locales/zh/common.json (3)

7-7: Remove trailing whitespace in translation value

The translation for "noResultsFoundFor" contains a trailing space which might cause UI alignment issues.

-  "noResultsFoundFor": "没有找到结果 ",
+  "noResultsFoundFor": "没有找到结果",

---

32-32: Consider removing duplicate description key

The keys "description" and "desc" serve the same purpose. Consider using only "description" for consistency.

  "description": "描述",
-  "desc": "描述",

Also applies to: 40-40

---

54-67: Standardize key casing format

Some keys use spaces while others don't. Consider standardizing to camelCase or using consistent separators.

Example standardization:

-  "My Organizations": "我的组织",
+  "myOrganizations": "我的组织",
-  "Action Items": "行动项目",
+  "actionItems": "行动项目",

public/locales/hi/common.json (3)

7-7: Remove trailing whitespace in translation value

The translation for "noResultsFoundFor" contains a trailing space which might cause UI alignment issues.

-  "noResultsFoundFor": "का कोई परिणाम नहीं मिला ",
+  "noResultsFoundFor": "का कोई परिणाम नहीं मिला",

---

41-41: Fix inconsistent spacing in password text

The Hindi translation for "enterPassword" contains inconsistent spacing in "पास वर्ड".

-  "enterPassword": "पास वर्ड दर्ज करें",
+  "enterPassword": "पासवर्ड दर्ज करें",

---

1-98: Consider implementing localization validation tools

To maintain consistency across language files and prevent common issues, consider:

1. Implementing a JSON schema for validation
2. Adding automated checks for:
   • Trailing whitespaces
   • Consistent key naming
   • Placeholder usage
   • Duplicate keys
3. Creating a localization style guide

This will help maintain quality as more languages are added.

.github/workflows/compare_translations.py (2)

1-49: Simplify the module docstring for clarity

The module docstring is overly verbose and contains redundant information. According to PEP 257, module docstrings should be concise summaries of the module's purpose.

Consider simplifying the docstring as follows:

-"""Script to encourage more efficient coding practices.
-Methodology:
-
-    Utility for comparing translations between default and other languages.
-
-    This module defines a function to compare two translations
-    and print any missing keys in the other language's translation.
-Attributes:
-
-    FileTranslation : Named tuple to represent a combination
-                        of file and missing translations.
-
-        Fields:
-            - file (str): The file name.
-            - missing_translations (list): List of missing translations.
-
-Functions:
-    compare_translations(default_translation, other_translation):
-        Compare two translations and print missing keys.
-
-     load_translation(filepath):
-        Load translation from a file.
-
-    check_translations():
-        Load the default translation and compare it with other translations.
-
-     main():
-        The main function to run the script.
-        Parses command-line arguments, checks for the
-        existence of the specified directory, and then
-        calls check_translations with the provided or default directory.
-
-
-Usage:
-    This script can be executed to check and print missing
-    translations in other languages based on the default English translation.
-
-Example:
-    python compare_translations.py
-NOTE:
-    This script complies with our python3 coding and documentation standards
-    and should be used as a reference guide. It complies with:
-
-        1) Pylint
-        2) Pydocstyle
-        3) Pycodestyle
-        4) Flake8
-
-"""
+"""Utility script to compare translations between the default language and others.

This module provides functions to identify missing or mismatched keys in translation files.

Example:
    python compare_translations.py
"""

---

80-88: Optimize key comparison using set operations

Using set operations can improve the efficiency of comparing keys between dictionaries.

Consider refactoring the compare_translations function as follows:

         errors = []
-        # Check for missing keys in other_translation
-        for key in default_translation:
-            if key not in other_translation:
-                error_msg = f"Missing Key: '{key}' - This key from '{default_file}' is missing in '{other_file}'."
-                errors.append(error_msg)
-        # Check for keys in other_translation that don't match any in default_translation
-        for key in other_translation:
-            if key not in default_translation:
-                error_msg = f"Error Key: '{key}' - This key in '{other_file}' does not match any key in '{default_file}'."
-                errors.append(error_msg)
+        default_keys = set(default_translation.keys())
+        other_keys = set(other_translation.keys())
+
+        missing_keys = default_keys - other_keys
+        extra_keys = other_keys - default_keys
+
+        for key in missing_keys:
+            error_msg = f"Missing Key: '{key}' - This key from '{default_file}' is missing in '{other_file}'."
+            errors.append(error_msg)
+
+        for key in extra_keys:
+            error_msg = f"Extra Key: '{key}' - This key in '{other_file}' does not exist in '{default_file}'."
+            errors.append(error_msg)

.github/workflows/eslint_disable_check.py (2)

61-61: Rename unused variable dirs to _

The variable dirs is assigned but not used in the loop. Renaming it to _ clarifies that it's intentionally unused.

Apply this diff to rename the variable:

-    for root, dirs, files in os.walk(os.path.join(directory, 'src')):
+    for root, _, files in os.walk(os.path.join(directory, 'src')):

🧰 Tools

🪛 Ruff (0.8.2)

61-61: Loop control variable dirs not used within loop body

Rename unused dirs to _dirs

(B007)

---

76-81: Update docstring return description

The docstring mentions result in the Returns section, but the function returns parser.parse_args() directly without assigning it to result. Consider updating the docstring for clarity.

Apply this diff to correct the docstring:

     """Resolve the CLI arguments provided by the user.

-    Returns:
-        result: Parsed argument object
+    Returns:
+        argparse.Namespace: Parsed argument object
     """

setup.ts (1)

13-19: Simplify .env file initialization

You can streamline the creation of the .env file by copying .env.example directly, which reduces complexity and improves readability.

Apply this diff to simplify the code:

      if (!fs.existsSync('.env')) {
-        fs.openSync('.env', 'w');
-        const config = dotenv.parse(fs.readFileSync('.env.example'));
-        for (const key in config) {
-          fs.appendFileSync('.env', `${key}=${config[key]}\n`);
-        }
+        fs.copyFileSync('.env.example', '.env');
      } else {
        checkEnvFile();
      }

.husky/post-merge (1)

4-4: Consider enhancing the package.json change detection

The current implementation might miss changes if the merge involves multiple commits. Consider using a more robust approach.

-git diff HEAD^ HEAD --exit-code -- ./package.json || npm install
+changed_files=$(git diff-tree -r --name-only --no-commit-id ORIG_HEAD HEAD)
+echo "$changed_files" | grep --quiet "^package.json$" && npm install

Also consider adding error handling:

-git diff HEAD^ HEAD --exit-code -- ./package.json || npm install
+if ! git diff HEAD^ HEAD --exit-code -- ./package.json; then
+  echo "📦 package.json changes detected"
+  if npm install; then
+    echo "✅ Dependencies updated successfully"
+  else
+    echo "❌ Failed to update dependencies"
+    exit 1
+  fi
+fi

.lintstagedrc.json (1)

2-4: Consider optimizing lint-staged configuration

The current setup processes TypeScript files multiple times. Consider consolidating commands and adding specific handling for test files.

{
-  "**/*.{ts,tsx,yml}": "eslint --fix",
-  "**/*.{ts,tsx,json,scss,css,yml}": "prettier --write",
-  "**/*.{ts,tsx}": "node scripts/githooks/check-localstorage-usage.js"
+  "**/*.{ts,tsx}": [
+    "eslint --fix",
+    "prettier --write",
+    "node scripts/githooks/check-localstorage-usage.js"
+  ],
+  "**/*.{json,scss,css,yml}": "prettier --write",
+  "**/*.spec.{ts,tsx}": [
+    "eslint --fix",
+    "prettier --write"
+  ]
}

This optimization:

1. Reduces multiple passes over TypeScript files
2. Adds specific handling for test files
3. Separates non-TypeScript files for formatting only

.husky/pre-commit (1)

5-5: Clarify the commented out lint:fix command

The presence of a commented out lint:fix command suggests uncertainty about its inclusion. Consider either removing it entirely or documenting why it's disabled.

scripts/githooks/update-toc.js (1)

8-12: Consider making the script more configurable

The script has hard-coded values for the path and bullet style. Consider making these configurable.

+const CONFIG = {
+  directory: process.env.TOC_DIR || './',
+  bullet: process.env.TOC_BULLET || '-'
+};
+
 markdownFiles.forEach((file) => {
-  const command = `markdown-toc -i "${file}" --bullets "-"`;
+  const command = `markdown-toc -i "${file}" --bullets "${CONFIG.bullet}"`;
   execSync(command, { stdio: 'inherit' });
-  
 });

🧰 Tools

🪛 eslint

[error] 11-12: Delete ··⏎

(prettier/prettier)

scripts/custom-test-env.js (1)

4-7: Fix JSDoc documentation

The JSDoc comment contains an undefined tag and could be more descriptive.

 /**
- * A custom environment to set the TextEncoder and TextDecoder variables, that is required by @pdfme during testing.
- * Providing a polyfill to the environment for the same
+ * A custom environment to set the TextEncoder and TextDecoder variables.
+ * These polyfills are required for PDF manipulation libraries during testing.
+ * @see https://www.npmjs.com/package/@pdfme
  */

🧰 Tools

🪛 eslint

[error] 5-5: tsdoc-undefined-tag: The TSDoc tag "@pdfme" is not defined in this configuration

(tsdoc/syntax)

config/vite.config.ts (2)

27-28: Fix misleading comment about default port

The comment states the port is set to 3000, but the actual configuration uses 4321.

-    // this sets a default port to 3000
+    // this sets a default port to 4321

---

8-12: Consider documenting the empty base URL choice

While the comment mentions base can be "/", it doesn't explain why an empty string was chosen. This could affect asset loading and routing behavior.

Consider adding a comment explaining the implications of using an empty base URL.

scripts/__mocks__/@pdfme/generator.ts (2)

11-11: Remove commented out console.log statement

Debug logging statements should be removed rather than commented out.

-    // console.log('pdf error: length : ', template, inputs, inputs.length);

---

17-20: Consider more realistic mock data generation

The current implementation uses random bytes for content, which might not be ideal for testing PDF structure.

Consider implementing a more structured mock that better represents actual PDF content:

-  const contentSize = Math.min(template.schemas.length, inputs.length) * 10;
-  const mockContent = Array.from({ length: contentSize }, () =>
-    Math.floor(Math.random() * 256),
-  );
+  const mockContent = inputs.flatMap(input => {
+    // Create structured mock data based on template schemas
+    return Object.entries(input).flatMap(([key, value]) => 
+      new TextEncoder().encode(`${key}: ${value}\n`));
+  });

.github/workflows/codeql-codescan.yml (1)

14-20: Consider limiting workflow triggers

The workflow currently runs on all branches. Consider limiting it to specific branches to avoid unnecessary runs.

 on:
   pull_request:
     branches:
-      - '**'  
+      - 'main'
+      - 'develop'
   push:
     branches:
-      - '**'   
+      - 'main'
+      - 'develop'

🧰 Tools

🪛 yamllint (1.35.1)

[error] 17-17: trailing spaces

(trailing-spaces)

---

[error] 20-20: trailing spaces

(trailing-spaces)

scripts/__mocks__/@pdfme/generator.test.ts (1)

21-46: Refactor similar test cases using test.each

The three error test cases have similar structure and assertions. Consider using Vitest's test.each to make the tests more maintainable and concise.

-  it('should throw an error when template is empty', async () => {
-    const emptyTemplate = { schemas: [] } as Template;
-    const validInputs = [{ field1: 'value1' }];
-
-    await expect(
-      generate({ template: emptyTemplate, inputs: validInputs }),
-    ).rejects.toThrow('Template or inputs cannot be empty.');
-  });
-
-  it('should throw an error when inputs are empty', async () => {
-    const validTemplate = { schemas: [{ name: 'field1' }] } as Template;
-    const emptyInputs: Record<string, string>[] = [];
-
-    await expect(
-      generate({ template: validTemplate, inputs: emptyInputs }),
-    ).rejects.toThrow('Template or inputs cannot be empty.');
-  });
-
-  it('should throw an error when both template and inputs are empty', async () => {
-    const emptyTemplate = { schemas: [] } as Template;
-    const emptyInputs: Record<string, string>[] = [];
-
-    await expect(
-      generate({ template: emptyTemplate, inputs: emptyInputs }),
-    ).rejects.toThrow('Template or inputs cannot be empty.');
-  });
+  test.each([
+    {
+      scenario: 'empty template',
+      template: { schemas: [] } as Template,
+      inputs: [{ field1: 'value1' }],
+    },
+    {
+      scenario: 'empty inputs',
+      template: { schemas: [{ name: 'field1' }] } as Template,
+      inputs: [],
+    },
+    {
+      scenario: 'both empty',
+      template: { schemas: [] } as Template,
+      inputs: [],
+    },
+  ])('should throw an error when $scenario', async ({ template, inputs }) => {
+    await expect(
+      generate({ template, inputs }),
+    ).rejects.toThrow('Template or inputs cannot be empty.');
+  });

.github/pull_request_template.md (1)

22-25: Improve issue reference formatting

The issue reference section could be more clearly formatted to ensure consistent PR submissions.

-**Issue Number:**
-
-Fixes #<!--Add related issue number here.-->
+**Issue Reference:**
+
+Fixes #[Issue Number] <!-- Replace [Issue Number] with the actual issue number -->
+
+<!-- If this PR addresses multiple issues, list them all:
+- Fixes #[Issue Number 1]
+- Related to #[Issue Number 2]
+-->

DOCUMENTATION.md (2)

22-25: Fix grammatical and formatting issues

There are several minor issues in this section that should be addressed.

-The process in easy:
+The process is easy:
 1. Install `talawa-docs` on your system
-1. Launch docusaurus on your system according to the `talawa-docs`documentation. 
+1. Launch Docusaurus on your system according to the `talawa-docs` documentation.
-    - A local version of `docs.talawa.io` should automatically launched in your browser at http://localhost:3000/
+    - A local version of `docs.talawa.io` will automatically launch in your browser at `http://localhost:3000/`

🧰 Tools

🪛 Markdownlint (0.37.0)

25-25: null
Bare URL used

(MD034, no-bare-urls)

🪛 LanguageTool

[grammar] ~25-~25: The modal verb ‘should’ requires the verb’s base form.
Context: ...f docs.talawa.io should automatically launched in your browser at http://localhost:300...

(MD_BASEFORM)

---

26-29: Improve Markdown formatting consistency

The documentation should maintain consistent capitalization and formatting for technical terms.

-1. Add/modify the markdown documents to the `docs/` directory of the `talawa-docs` repository
+1. Add/modify the Markdown documents to the `docs/` directory of the `talawa-docs` repository
 1. If adding a file, then you will also need to edit the `sidebars.js` which is used to generate the [docs.talawa.io](https://docs.talawa.io/) menus.
-1. Always monitor the local website in your brower to make sure the changes are acceptable. 
+1. Always monitor the local website in your browser to make sure the changes are acceptable.

🧰 Tools

🪛 LanguageTool

[grammar] ~26-~26: Did you mean the formatting language “Markdown” (= proper noun)?
Context: ...ttp://localhost:3000/ 1. Add/modify the markdown documents to the docs/ directory of t...

(MARKDOWN_NNP)

scripts/githooks/check-localstorage-usage.js (2)

10-18: Consider enhancing error handling in containsSkipComment function

While the basic error handling is present, consider being more specific about what could go wrong:

1. File permissions
2. File encoding issues
3. Invalid file path

 const containsSkipComment = (file) => {
   try {
     const content = readFileSync(file, 'utf-8');
     return content.includes('// SKIP_LOCALSTORAGE_CHECK');
   } catch (error) {
-    console.error(`Error reading file ${file}:`, error.message);
+    console.error(`Error reading file ${file}: ${error.code === 'ENOENT' ? 'File not found' : 
+      error.code === 'EACCES' ? 'Permission denied' : 
+      error.code === 'EISDIR' ? 'Path is a directory' : 
+      error.message}`);
     return false;
   }
 };

🧰 Tools

🪛 eslint

[error] 10-10: Missing return type on function.

(@typescript-eslint/explicit-function-return-type)

---

43-78: Consider improving the checkLocalStorageUsage function

The function could benefit from some improvements in terms of robustness and maintainability:

1. The list of files to skip could be moved to a configuration
2. The localStorage methods to check could be defined as a constant array
3. The file existence check could be moved before content reading

+const SKIP_FILES = [
+  'check-localstorage-usage.js',
+  'useLocalstorage.test.ts',
+  'useLocalstorage.ts'
+];
+
+const LOCALSTORAGE_METHODS = [
+  'localStorage.getItem',
+  'localStorage.setItem',
+  'localStorage.removeItem'
+];
+
 const checkLocalStorageUsage = (file) => {
   if (!file) {
     return;
   }

   const fileName = path.basename(file);

-  // Skip files with specific names or containing a skip comment
   if (
-    fileName === 'check-localstorage-usage.js' ||
-    fileName === 'useLocalstorage.test.ts' ||
-    fileName === 'useLocalstorage.ts' ||
+    SKIP_FILES.includes(fileName) ||
     containsSkipComment(file)
   ) {
     console.log(`Skipping file: ${file}`);
     return;
   }

   try {
     if (existsSync(file)) {
       const content = readFileSync(file, 'utf-8');

-      if (
-        content.includes('localStorage.getItem') ||
-        content.includes('localStorage.setItem') ||
-        content.includes('localStorage.removeItem')
-      ) {
+      if (LOCALSTORAGE_METHODS.some(method => content.includes(method))) {
         filesWithLocalStorage.push(file);
       }
     } else {
       console.log(`File ${file} does not exist.`);
     }
   } catch (error) {
     console.error(`Error reading file ${file}:`, error.message);
   }
 };

🧰 Tools

🪛 eslint

[error] 43-43: Missing return type on function.

(@typescript-eslint/explicit-function-return-type)

.github/workflows/issue.yml (2)

33-56: Consider refactoring the github-script for better maintainability

The inline script could be improved by:

1. Extracting repeated code into reusable functions
2. Using constants for label lists
3. Improving the readability of the reduce function

 script: |
+  const LABEL_CONFIGS = {
+    dependencies: ['good first issue', 'security'],
+    security: ['good first issue'],
+    'ui/ux': ['good first issue']
+  };
+
+  const hasLabel = (labels, targetLabels) => 
+    labels.some(label => targetLabels.includes(label.name));
+
   const { owner, repo } = context.repo;
   const issue_number = context.issue.number;
   const apiParams = {
     owner,
     repo,
     issue_number
   };
   const labels = await github.rest.issues.listLabelsOnIssue(apiParams);
-  if(labels.data.reduce((a, c)=>a||["dependencies"].includes(c.name), false))
-    await github.rest.issues.addLabels({
-      owner: context.repo.owner,
-      repo: context.repo.repo,
-      issue_number: context.issue.number,
-      labels: ["good first issue", "security"]
-    });
-  else if(labels.data.reduce((a, c)=>a||["security", "ui/ux"].includes(c.name), false))
-    await github.rest.issues.addLabels({
-      owner: context.repo.owner,
-      repo: context.repo.repo,
-      issue_number: context.issue.number,
-      labels: ["good first issue"]
-    });
+
+  const currentLabels = labels.data.map(label => label.name);
+  
+  for (const [triggerLabel, labelsToAdd] of Object.entries(LABEL_CONFIGS)) {
+    if (currentLabels.includes(triggerLabel)) {
+      await github.rest.issues.addLabels({
+        owner,
+        repo,
+        issue_number,
+        labels: labelsToAdd
+      });
+      break;
+    }
+  }

---

62-65: Consider adding a timeout for the first-interaction action

To prevent potential hanging in CI, consider adding a timeout for the first-interaction check.

       - uses: actions/first-interaction@v1
+        timeout-minutes: 5
         with:
           repo-token: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/talawa_admin_md_mdx_format_adjuster.py (1)

89-94: Consider adding progress reporting for large directories

When processing many files, it would be helpful to show progress to the user.

     # Process each Markdown file in the directory
+    markdown_files = []
     for root, _, files in os.walk(args.directory):
         for file in files:
             if file.lower().endswith(".md"):
-                process_file(os.path.join(root, file))
+                markdown_files.append(os.path.join(root, file))
+    
+    total_files = len(markdown_files)
+    print(f"Found {total_files} Markdown files to process")
+    
+    for i, filepath in enumerate(markdown_files, 1):
+        print(f"Processing file {i}/{total_files}: {filepath}")
+        process_file(filepath)
+    
+    print("Processing complete!")

ISSUE_GUIDELINES.md (3)

5-5: Fix grammatical error in the introduction

Change "a issues reports" to "issue reports" for better grammar.

-In order to give everyone a chance to submit a issues reports and contribute to the Talawa project
+In order to give everyone a chance to submit issue reports and contribute to the Talawa project

🧰 Tools

🪛 LanguageTool

[misspelling] ~5-~5: Use “an” instead of ‘a’ if the following word starts with a vowel sound, e.g. ‘an article’, ‘an hour’.
Context: ...der to give everyone a chance to submit a issues reports and contribute to the Ta...

(EN_A_VS_AN)

---

29-29: Fix sentence structure in search instructions

The sentence has redundant parts and unclear structure.

-Your issue may have already been created. Search for duplicate open issues before submitting yours.for similar deficiencies in the code.duplicate issues are created.
+Your issue may have already been created. Search for duplicate open issues before submitting yours to avoid redundancy.

---

44-44: Capitalize "Slack" as it's a proper noun

Slack should be capitalized when referring to the communication platform.

-Ask our contributors to assign it to you in `#talawa` slack channel.
+Ask our contributors to assign it to you in `#talawa` Slack channel.

-Join our `#talawa-github` slack channel for automatic issue and pull request updates.
+Join our `#talawa-github` Slack channel for automatic issue and pull request updates.

-Discuss issues in our various slack channels when necessary
+Discuss issues in our various Slack channels when necessary

Also applies to: 53-53, 57-57

🧰 Tools

🪛 LanguageTool

[grammar] ~44-~44: Did you mean the communication tool “Slack” (= proper noun, capitalized)?
Context: ...butors to assign it to you in #talawa slack channel. Working on these types of exi...

(ON_SKYPE)

.github/workflows/pull-request-target.yml (1)

1-77: Remove trailing spaces throughout the file

Multiple lines contain trailing spaces which should be removed according to YAML best practices.

Use your editor's trailing space removal feature to clean up the file.

🧰 Tools

🪛 yamllint (1.35.1)

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 13-13: trailing spaces

(trailing-spaces)

---

[error] 15-15: trailing spaces

(trailing-spaces)

---

[error] 27-27: trailing spaces

(trailing-spaces)

---

[error] 28-28: trailing spaces

(trailing-spaces)

---

[error] 29-29: trailing spaces

(trailing-spaces)

---

[error] 31-31: trailing spaces

(trailing-spaces)

---

[error] 33-33: trailing spaces

(trailing-spaces)

---

[error] 34-34: trailing spaces

(trailing-spaces)

---

[error] 36-36: trailing spaces

(trailing-spaces)

---

[error] 41-41: trailing spaces

(trailing-spaces)

---

[error] 46-46: trailing spaces

(trailing-spaces)

---

[error] 71-71: trailing spaces

(trailing-spaces)

.eslintrc.json (1)

14-16: Consider adding stricter TypeScript configurations.

While the TypeScript and Prettier configurations are good additions, consider also adding "plugin:@typescript-eslint/strict" for stricter type checking.

  "extends": [
    "plugin:react/recommended",
    "eslint:recommended",
    "plugin:jest/recommended",
    "plugin:prettier/recommended",
    "plugin:@typescript-eslint/recommended",
+   "plugin:@typescript-eslint/strict",
    "eslint-config-prettier",
    "prettier"
  ],

PR_GUIDELINES.md (2)

31-34: Add language identifiers to code blocks.

The fenced code blocks should specify the shell language for better syntax highlighting.

-```
+```shell
npm run lint:fix
npm run format:fix

Also applies to: 39-42

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 Markdownlint (0.37.0)</summary>

31-31: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

</details>

</details>

---

`56-56`: **Improve sentence structure.**

The sentence can be improved for clarity and conciseness.

```diff
-The quality of our code is very important to us. Therefore we make experienced maintainers of our code base review your code.
+Code quality is crucial to us. Therefore, we ensure experienced maintainers review your code.

🧰 Tools

🪛 LanguageTool

[style] ~56-~56: As an alternative to the over-used intensifier ‘very’, consider replacing this phrase.
Context: ...o be closed. The quality of our code is very important to us. Therefore we make experienced ma...

(EN_WEAK_ADJECTIVE)

---

[uncategorized] ~56-~56: A comma may be missing after the conjunctive/linking adverb ‘Therefore’.
Context: ...ty of our code is very important to us. Therefore we make experienced maintainers of our ...

(SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)

CODE_STYLE.md (2)

47-69: Consider adding TypeScript-specific naming conventions.

The code style section would benefit from additional guidelines specific to TypeScript, such as:

• Interface naming (IMyInterface vs MyInterface)
• Type naming conventions
• Enum naming conventions

🧰 Tools

🪛 Markdownlint (0.37.0)

57-57: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

58-58: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

65-65: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

185-189: Add examples of Bootstrap variable customization.

Consider adding examples of how to override Bootstrap variables in the _variables.scss file, as this is a common customization need.

.github/workflows/pull-request.yml (1)

223-226: Consider documenting coverage thresholds.

The minimum coverage threshold of 95% is quite high. Consider adding a comment explaining the rationale and any plans for adjusting this threshold over time.

CONTRIBUTING.md (1)

66-69: Add branch protection information.

Consider adding information about branch protection rules, such as:

• Required reviews before merging
• Status checks that must pass
• Restrictions on force pushing

🧰 Tools

🪛 LanguageTool

[uncategorized] ~68-~68: Loose punctuation mark.
Context: ...ushed to the main branch: - develop: For unstable code and bug fixing - `mai...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~69-~69: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...d bug fixing - main: Where the stable production ready code lies. This is our default branch. ...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

INSTALLATION.md (3)

321-321: Fix document structure inconsistencies

• The heading "pre-commit hook" and "post-merge hook" should use ### instead of #### to maintain proper heading hierarchy
• The list items under the table of contents should maintain consistent indentation (4 spaces instead of 6)

-      - [pre-commit hook](#pre-commit-hook)
-      - [post-merge hook](#post-merge-hook)
+    - [pre-commit hook](#pre-commit-hook)
+    - [post-merge hook](#post-merge-hook)

Also applies to: 33-34

🧰 Tools

🪛 Markdownlint (0.37.0)

321-321: Expected: h3; Actual: h4
Heading levels should only increment by one level at a time

(MD001, heading-increment)

---

142-144: Improve code block formatting

• Add language specifiers to code blocks (e.g., bash for shell commands)
• Use fenced code blocks consistently instead of indented style

For example:

-```
+```bash
 npm install

•    git commit -m "commit message" --no-verify
  

+bash +git commit -m "commit message" --no-verify +

Also applies to: 327-328, 335-336

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 Markdownlint (0.37.0)</summary>

142-142: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

</details>

</details>

---

`67-68`: **Improve content accuracy and clarity**

- Use "set up" (verb) instead of "setup" (noun) consistently
- Use correct OS naming: "macOS" instead of "MacOS"
- Format bare URLs as markdown links

```diff
-navigate to the folder where you want to setup the repository
+navigate to the folder where you want to set up the repository

-`cmd` (Windows) or `terminal` (Linux or MacOS)
+`cmd` (Windows) or `terminal` (Linux or macOS)

-You may not want to setup reCAPTCHA
+You may not want to set up reCAPTCHA

Also applies to: 102-102, 119-119, 228-232

🧰 Tools

🪛 LanguageTool

[grammar] ~67-~67: The word “setup” is a noun. The verb is spelled with a space.
Context: ...avigate to the folder where you want to setup the repository. 2. Open a cmd (Window...

(NOUN_VERB_CONFUSION)

---

[grammar] ~68-~68: The operating system from Apple is written “macOS”.
Context: ...cmd (Windows) or terminal (Linux or MacOS) session in this folder. 1. An easy ...

(MAC_OS)

.github/ISSUE_TEMPLATE/bug-report.md (1)

33-36: Improve markdown formatting in the internship section

• Use proper heading syntax instead of bold emphasis
• Format the URL as a markdown link

-**Potential internship candidates**
+### Potential internship candidates

-Please read this if you are planning to apply for a Palisadoes Foundation internship 
-- https://github.com/PalisadoesFoundation/talawa/issues/359
+Please read this if you are planning to apply for a Palisadoes Foundation internship:
+- [Internship Information](https://github.com/PalisadoesFoundation/talawa/issues/359)

🧰 Tools

🪛 Markdownlint (0.37.0)

36-36: null
Bare URL used

(MD034, no-bare-urls)

---

33-33: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

.github/ISSUE_TEMPLATE/feature-request.md (1)

25-28: Apply same formatting improvements as bug report template

• Use proper heading syntax instead of bold emphasis
• Format the URL as a markdown link

-**Potential internship candidates**
+### Potential internship candidates

-Please read this if you are planning to apply for a Palisadoes Foundation internship 
-- https://github.com/PalisadoesFoundation/talawa/issues/359
+Please read this if you are planning to apply for a Palisadoes Foundation internship:
+- [Internship Information](https://github.com/PalisadoesFoundation/talawa/issues/359)

🧰 Tools

🪛 Markdownlint (0.37.0)

28-28: null
Bare URL used

(MD034, no-bare-urls)

---

25-25: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

.github/workflows/README.md (3)

13-14: Fix grammatical issues in the introduction

Add a comma after "possible" for better readability.

-Whenever possible you must ensure that:
+Whenever possible, you must ensure that:

🧰 Tools

🪛 LanguageTool

[uncategorized] ~13-~13: Possible missing comma found.
Context: ...ding on the type of workflow. Whenever possible you must ensure that: 1. The file roles...

(AI_HYDRA_LEO_MISSING_COMMA)

---

24-24: Fix typo in workflow description

Remove the duplicate "to".

-Place all actions related to to this in the `pull-request-target.yml` file.
+Place all actions related to this in the `pull-request-target.yml` file.

🧰 Tools

🪛 LanguageTool

[duplication] ~24-~24: Possible typo: you repeated a word
Context: ...ors: 1. Place all actions related to to this in the pull-request-target.yml f...

(ENGLISH_WORD_REPEAT_RULE)

---

35-35: Fix abbreviation format

Use proper format for the abbreviation "e.g.".

-Jobs only work correctly if they have a dedicated file (eg. `CodeQL`)
+Jobs only work correctly if they have a dedicated file (e.g., `CodeQL`)

🧰 Tools

🪛 LanguageTool

[uncategorized] ~35-~35: The abbreviation “e.g.” (= for example) requires two periods.
Context: ...orrectly if they have a dedicated file (eg. CodeQL) ## Scripts Follow these gui...

(E_G)

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4bef093 and dda3b82.

⛔ Files ignored due to path filters (75)

• package-lock.json is excluded by !**/package-lock.json
• public/favicon.ico is excluded by !**/*.ico
• public/favicon_palisadoes.ico is excluded by !**/*.ico
• public/images/logo512.png is excluded by !**/*.png
• public/images/svg/angleDown.svg is excluded by !**/*.svg
• public/images/svg/arrow-left.svg is excluded by !**/*.svg
• public/images/svg/arrow-right.svg is excluded by !**/*.svg
• public/images/svg/attendees.svg is excluded by !**/*.svg
• public/images/svg/feedback.svg is excluded by !**/*.svg
• public/images/svg/profiledefault.svg is excluded by !**/*.svg
• public/images/svg/up-down.svg is excluded by !**/*.svg
• public/logo192.png is excluded by !**/*.png
• public/markdown/images/install1.png is excluded by !**/*.png
• public/markdown/images/install2.png is excluded by !**/*.png
• src/assets/css/app.css.map is excluded by !**/*.map
• src/assets/images/blank.png is excluded by !**/*.png
• src/assets/images/bronze.png is excluded by !**/*.png
• src/assets/images/defaultImg.png is excluded by !**/*.png
• src/assets/images/gold.png is excluded by !**/*.png
• src/assets/images/palisadoes_logo.png is excluded by !**/*.png
• src/assets/images/silver.png is excluded by !**/*.png
• src/assets/images/talawa-logo-600x600.png is excluded by !**/*.png
• src/assets/images/talawa-logo-dark-200x200.png is excluded by !**/*.png
• src/assets/images/talawa-logo-lite-200x200.png is excluded by !**/*.png
• src/assets/svgs/Attendance.svg is excluded by !**/*.svg
• src/assets/svgs/actionItem.svg is excluded by !**/*.svg
• src/assets/svgs/admin.svg is excluded by !**/*.svg
• src/assets/svgs/agenda-category-icon.svg is excluded by !**/*.svg
• src/assets/svgs/agenda-items.svg is excluded by !**/*.svg
• src/assets/svgs/angleRight.svg is excluded by !**/*.svg
• src/assets/svgs/article.svg is excluded by !**/*.svg
• src/assets/svgs/blockUser.svg is excluded by !**/*.svg
• src/assets/svgs/blockedUser.svg is excluded by !**/*.svg
• src/assets/svgs/cardItemDate.svg is excluded by !**/*.svg
• src/assets/svgs/cardItemEvent.svg is excluded by !**/*.svg
• src/assets/svgs/cardItemLocation.svg is excluded by !**/*.svg
• src/assets/svgs/chat.svg is excluded by !**/*.svg
• src/assets/svgs/checkInRegistrants.svg is excluded by !**/*.svg
• src/assets/svgs/dashboard.svg is excluded by !**/*.svg
• src/assets/svgs/date.svg is excluded by !**/*.svg
• src/assets/svgs/event.svg is excluded by !**/*.svg
• src/assets/svgs/events.svg is excluded by !**/*.svg
• src/assets/svgs/flask.svg is excluded by !**/*.svg
• src/assets/svgs/funds.svg is excluded by !**/*.svg
• src/assets/svgs/key.svg is excluded by !**/*.svg
• src/assets/svgs/listEventRegistrants.svg is excluded by !**/*.svg
• src/assets/svgs/location.svg is excluded by !**/*.svg
• src/assets/svgs/logout.svg is excluded by !**/*.svg
• src/assets/svgs/media.svg is excluded by !**/*.svg
• src/assets/svgs/newChat.svg is excluded by !**/*.svg
• src/assets/svgs/organizations.svg is excluded by !**/*.svg
• src/assets/svgs/palisadoes.svg is excluded by !**/*.svg
• src/assets/svgs/people.svg is excluded by !**/*.svg
• src/assets/svgs/plugins.svg is excluded by !**/*.svg
• src/assets/svgs/post.svg is excluded by !**/*.svg
• src/assets/svgs/posts.svg is excluded by !**/*.svg
• src/assets/svgs/requests.svg is excluded by !**/*.svg
• src/assets/svgs/roles.svg is excluded by !**/*.svg
• src/assets/svgs/settings.svg is excluded by !**/*.svg
• src/assets/svgs/social-icons/Facebook-Logo.svg is excluded by !**/*.svg
• src/assets/svgs/social-icons/Github-Logo.svg is excluded by !**/*.svg
• src/assets/svgs/social-icons/Instagram-Logo.svg is excluded by !**/*.svg
• src/assets/svgs/social-icons/Linkedin-Logo.svg is excluded by !**/*.svg
• src/assets/svgs/social-icons/Reddit-Logo.svg is excluded by !**/*.svg
• src/assets/svgs/social-icons/Slack-Logo.svg is excluded by !**/*.svg
• src/assets/svgs/social-icons/X-Logo.svg is excluded by !**/*.svg
• src/assets/svgs/social-icons/Youtube-Logo.svg is excluded by !**/*.svg
• src/assets/svgs/tag.svg is excluded by !**/*.svg
• src/assets/svgs/tags.svg is excluded by !**/*.svg
• src/assets/svgs/talawa.svg is excluded by !**/*.svg
• src/assets/svgs/user.svg is excluded by !**/*.svg
• src/assets/svgs/userEvent.svg is excluded by !**/*.svg
• src/assets/svgs/users.svg is excluded by !**/*.svg
• src/assets/svgs/venues.svg is excluded by !**/*.svg
• src/assets/talawa-logo-lite-200x200.png is excluded by !**/*.png

📒 Files selected for processing (82)

• .coderabbit.yaml (1 hunks)
• .env.example (1 hunks)
• .eslintignore (1 hunks)
• .eslintrc.json (4 hunks)
• .github/ISSUE_TEMPLATE/bug-report.md (2 hunks)
• .github/ISSUE_TEMPLATE/feature-request.md (2 hunks)
• .github/dependabot.yaml (1 hunks)
• .github/pull_request_template.md (2 hunks)
• .github/workflows/README.md (1 hunks)
• .github/workflows/auto-label.json5 (1 hunks)
• .github/workflows/check-tsdoc.js (1 hunks)
• .github/workflows/ci.yml (0 hunks)
• .github/workflows/codeql-analysis.yml (0 hunks)
• .github/workflows/codeql-codescan.yml (1 hunks)
• .github/workflows/compare_translations.py (1 hunks)
• .github/workflows/countline.py (1 hunks)
• .github/workflows/eslint_disable_check.py (1 hunks)
• .github/workflows/issue.yml (1 hunks)
• .github/workflows/linter.yml (0 hunks)
• .github/workflows/npm-publish.yml (0 hunks)
• .github/workflows/pull-request-target.yml (1 hunks)
• .github/workflows/pull-request.yml (1 hunks)
• .github/workflows/push.yml (1 hunks)
• .github/workflows/stale.yml (1 hunks)
• .github/workflows/talawa_admin_md_mdx_format_adjuster.py (1 hunks)
• .gitignore (2 hunks)
• .husky/post-merge (1 hunks)
• .husky/pre-commit (1 hunks)
• .lintstagedrc.json (1 hunks)
• .node-version (1 hunks)
• .prettierignore (1 hunks)
• .prettierrc (1 hunks)
• CODEOWNERS (1 hunks)
• CODE_OF_CONDUCT.md (1 hunks)
• CODE_STYLE.md (1 hunks)
• CONTRIBUTING.md (2 hunks)
• DOCUMENTATION.md (1 hunks)
• Docker_Container/.dockerignore (0 hunks)
• Docker_Container/README.md (0 hunks)
• Docker_Container/docker-compose.yml (0 hunks)
• Docker_Container/dockerfile (0 hunks)
• INSTALLATION.md (1 hunks)
• ISSUE_GUIDELINES.md (1 hunks)
• ISSUE_TEMPLATE.md (0 hunks)
• PR-guidelines.md (0 hunks)
• PR_GUIDELINES.md (1 hunks)
• PULL_REQUEST_TEMPLATE.md (0 hunks)
• README.md (3 hunks)
• config/babel.config.cjs (1 hunks)
• config/vite.config.ts (1 hunks)
• index.html (1 hunks)
• issue-guidelines.md (0 hunks)
• jest-preview.config.ts (1 hunks)
• jest.config.js (1 hunks)
• package.json (2 hunks)
• public/index.html (0 hunks)
• public/locales/en/common.json (1 hunks)
• public/locales/en/errors.json (1 hunks)
• public/locales/en/translation.json (1 hunks)
• public/locales/fr/common.json (1 hunks)
• public/locales/fr/errors.json (1 hunks)
• public/locales/fr/translation.json (1 hunks)
• public/locales/hi/common.json (1 hunks)
• public/locales/hi/errors.json (1 hunks)
• public/locales/hi/translation.json (1 hunks)
• public/locales/sp/common.json (1 hunks)
• public/locales/sp/errors.json (1 hunks)
• public/locales/sp/translation.json (1 hunks)
• public/locales/zh/common.json (1 hunks)
• public/locales/zh/errors.json (1 hunks)
• public/locales/zh/translation.json (1 hunks)
• public/manifest.json (1 hunks)
• schema.graphql (1 hunks)
• scripts/__mocks__/@dicebear/collection.ts (1 hunks)
• scripts/__mocks__/@dicebear/core.ts (1 hunks)
• scripts/__mocks__/@pdfme/generator.test.ts (1 hunks)
• scripts/__mocks__/@pdfme/generator.ts (1 hunks)
• scripts/__mocks__/fileMock.js (1 hunks)
• scripts/custom-test-env.js (1 hunks)
• scripts/githooks/check-localstorage-usage.js (1 hunks)
• scripts/githooks/update-toc.js (1 hunks)
• setup.ts (1 hunks)

⛔ Files not processed due to max files limit (28)

• src/App.test.tsx
• src/App.tsx
• src/Constant/constant.spec.ts
• src/Constant/constant.ts
• src/GraphQl/Mutations/ActionItemCategoryMutations.ts
• src/GraphQl/Mutations/ActionItemMutations.ts
• src/GraphQl/Mutations/AgendaCategoryMutations.ts
• src/GraphQl/Mutations/AgendaItemMutations.ts
• src/GraphQl/Mutations/CampaignMutation.ts
• src/GraphQl/Mutations/CommentMutations.ts
• src/GraphQl/Mutations/EventAttendeeMutations.ts
• src/GraphQl/Mutations/EventVolunteerMutation.ts
• src/GraphQl/Mutations/FundMutation.ts
• src/GraphQl/Mutations/OrganizationMutations.ts
• src/GraphQl/Mutations/PledgeMutation.ts
• src/GraphQl/Mutations/TagMutations.ts
• src/GraphQl/Mutations/VenueMutations.ts
• src/GraphQl/Mutations/mutations.ts
• src/GraphQl/Queries/ActionItemCategoryQueries.ts
• src/GraphQl/Queries/ActionItemQueries.ts
• src/GraphQl/Queries/AgendaCategoryQueries.ts
• src/GraphQl/Queries/AgendaItemQueries.ts
• src/GraphQl/Queries/EventVolunteerQueries.ts
• src/GraphQl/Queries/OrganizationQueries.ts
• src/GraphQl/Queries/PlugInQueries.ts
• src/GraphQl/Queries/Queries.ts
• src/GraphQl/Queries/fundQueries.ts
• src/GraphQl/Queries/userTagQueries.ts

💤 Files with no reviewable changes (13)

• issue-guidelines.md
• ISSUE_TEMPLATE.md
• Docker_Container/dockerfile
• .github/workflows/codeql-analysis.yml
• Docker_Container/docker-compose.yml
• public/index.html
• .github/workflows/linter.yml
• .github/workflows/ci.yml
• PR-guidelines.md
• Docker_Container/.dockerignore
• PULL_REQUEST_TEMPLATE.md
• Docker_Container/README.md
• .github/workflows/npm-publish.yml

✅ Files skipped from review due to trivial changes (24)

• .eslintignore
• scripts/mocks/@dicebear/collection.ts
• .node-version
• .prettierignore
• scripts/mocks/fileMock.js
• .prettierrc
• CODEOWNERS
• jest-preview.config.ts
• .coderabbit.yaml
• config/babel.config.cjs
• .github/dependabot.yaml
• .github/workflows/auto-label.json5
• public/locales/zh/errors.json
• public/locales/en/common.json
• public/locales/sp/translation.json
• public/locales/fr/common.json
• public/locales/fr/translation.json
• index.html
• public/locales/zh/translation.json
• public/locales/sp/errors.json
• .gitignore
• .env.example
• public/locales/hi/translation.json
• public/locales/sp/common.json

🧰 Additional context used

📓 Learnings (1)

scripts/githooks/check-localstorage-usage.js (1)

Learnt from: MayankJha014
PR: PalisadoesFoundation/talawa-admin#2612
File: scripts/githooks/check-localstorage-usage.js:10-18
Timestamp: 2024-12-07T14:25:09.928Z
Learning: TypeScript type annotations should not be added to JavaScript (`.js`) files in this project. Type annotations can only be used in TypeScript (`.ts` or `.tsx`) files.

🪛 eslint

scripts/githooks/update-toc.js

[error] 11-12: Delete ··⏎

(prettier/prettier)

scripts/githooks/check-localstorage-usage.js

[error] 10-10: Missing return type on function.

(@typescript-eslint/explicit-function-return-type)

---

[error] 20-20: Missing return type on function.

(@typescript-eslint/explicit-function-return-type)

---

[error] 43-43: Missing return type on function.

(@typescript-eslint/explicit-function-return-type)

---

[error] 89-89: Insert ,

(prettier/prettier)

---

[error] 92-92: Insert ,

(prettier/prettier)

jest.config.js

[error] 33-33: Delete ·

(prettier/prettier)

---

[error] 34-34: Insert ,

(prettier/prettier)

scripts/custom-test-env.js

[error] 5-5: tsdoc-undefined-tag: The TSDoc tag "@pdfme" is not defined in this configuration

(tsdoc/syntax)

---

[error] 9-9: Missing return type on function.

(@typescript-eslint/explicit-function-return-type)

---

[error] 9-9: Missing return type on function.

(@typescript-eslint/explicit-module-boundary-types)

🪛 yamllint (1.35.1)

.github/workflows/push.yml

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 17-17: trailing spaces

(trailing-spaces)

---

[error] 18-18: trailing spaces

(trailing-spaces)

---

[warning] 20-20: wrong indentation: expected 2 but found 4

(indentation)

---

[error] 21-21: trailing spaces

(trailing-spaces)

---

[error] 50-50: trailing spaces

(trailing-spaces)

---

[warning] 62-62: too many blank lines

(1 > 0) (empty-lines)

.github/workflows/codeql-codescan.yml

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 17-17: trailing spaces

(trailing-spaces)

---

[error] 20-20: trailing spaces

(trailing-spaces)

---

[warning] 31-31: wrong indentation: expected 6 but found 7

(indentation)

---

[warning] 37-37: wrong indentation: expected 11 but found 10

(indentation)

.github/workflows/stale.yml

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 20-20: trailing spaces

(trailing-spaces)

---

[error] 21-21: trailing spaces

(trailing-spaces)

.github/workflows/pull-request-target.yml

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 13-13: trailing spaces

(trailing-spaces)

---

[error] 15-15: trailing spaces

(trailing-spaces)

---

[error] 27-27: trailing spaces

(trailing-spaces)

---

[error] 28-28: trailing spaces

(trailing-spaces)

---

[error] 29-29: trailing spaces

(trailing-spaces)

---

[error] 31-31: trailing spaces

(trailing-spaces)

---

[error] 33-33: trailing spaces

(trailing-spaces)

---

[error] 34-34: trailing spaces

(trailing-spaces)

---

[error] 36-36: trailing spaces

(trailing-spaces)

---

[error] 41-41: trailing spaces

(trailing-spaces)

---

[error] 46-46: trailing spaces

(trailing-spaces)

---

[error] 71-71: trailing spaces

(trailing-spaces)

.github/workflows/issue.yml

[error] 6-6: trailing spaces

(trailing-spaces)

---

[warning] 15-15: wrong indentation: expected 4 but found 6

(indentation)

---

[warning] 66-66: too many blank lines

(1 > 0) (empty-lines)

.github/workflows/pull-request.yml

[error] 49-49: trailing spaces

(trailing-spaces)

---

[error] 60-60: trailing spaces

(trailing-spaces)

---

[error] 63-63: trailing spaces

(trailing-spaces)

---

[error] 92-92: trailing spaces

(trailing-spaces)

---

[error] 126-126: trailing spaces

(trailing-spaces)

---

[error] 129-129: trailing spaces

(trailing-spaces)

---

[error] 150-150: trailing spaces

(trailing-spaces)

---

[error] 157-157: trailing spaces

(trailing-spaces)

---

[error] 197-197: trailing spaces

(trailing-spaces)

---

[error] 201-201: trailing spaces

(trailing-spaces)

---

[error] 204-204: trailing spaces

(trailing-spaces)

---

[error] 205-205: trailing spaces

(trailing-spaces)

---

[error] 213-213: trailing spaces

(trailing-spaces)

---

[error] 243-243: trailing spaces

(trailing-spaces)

---

[error] 249-249: trailing spaces

(trailing-spaces)

---

[error] 251-251: trailing spaces

(trailing-spaces)

🪛 actionlint (1.7.4)

.github/workflows/codeql-codescan.yml

35-35: the runner of "github/codeql-action/init@v2" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

---

41-41: the runner of "github/codeql-action/autobuild@v2" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

---

44-44: the runner of "github/codeql-action/analyze@v2" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

.github/workflows/stale.yml

28-28: the runner of "actions/stale@v8" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

.github/workflows/issue.yml

29-29: the runner of "actions/github-script@v6" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

.github/workflows/pull-request.yml

61-61: property "changed_files" is not defined in object type {changed-files: {conclusion: string; outcome: string; outputs: {string => string}}}

(expression)

---

62-62: shellcheck reported issue in this script: SC2086:info:1:12: Double quote to prevent globbing and word splitting

(shellcheck)

---

79-79: "github.event.pull_request.head.ref" is potentially untrusted. avoid using it directly in inline scripts. instead, pass it through an environment variable. see https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions for more details

(expression)

🪛 LanguageTool

ISSUE_GUIDELINES.md

[uncategorized] ~2-~2: Loose punctuation mark.
Context: # Issue Report Guidelines 👍🎉 First off, thanks for taking t...

(UNLIKELY_OPENING_PUNCTUATION)

---

[style] ~4-~4: Consider a shorter alternative to avoid wordiness.
Context: ...ing the time to contribute! 🎉👍 In order to give everyone a chance to submit a issu...

(IN_ORDER_TO_PREMIUM)

---

[misspelling] ~5-~5: Use “an” instead of ‘a’ if the following word starts with a vowel sound, e.g. ‘an article’, ‘an hour’.
Context: ...der to give everyone a chance to submit a issues reports and contribute to the Ta...

(EN_A_VS_AN)

---

[typographical] ~24-~24: Consider adding a comma here.
Context: ...> ___ ## Issue Management In all cases please use the [GitHub open issue search](http...

(PLEASE_COMMA)

---

[style] ~30-~30: Consider using a different verb for a more formal wording.
Context: .... 1. Verify whether the issue has been fixed by trying to reproduce it using the lat...

(FIX_RESOLVE)

---

[style] ~35-~35: The wording of this phrase can be improved.
Context: ...lcome contributors who find new ways to make the code better. ### Existing Issues You can also be ...

(MAKE_STYLE_BETTER)

---

[grammar] ~44-~44: Did you mean the communication tool “Slack” (= proper noun, capitalized)?
Context: ...butors to assign it to you in #talawa slack channel. Working on these types of exi...

(ON_SKYPE)

---

[grammar] ~53-~53: Did you mean the communication tool “Slack” (= proper noun, capitalized)?
Context: ...ew Issues 1. Join our #talawa-github slack channel for automatic issue and pull re...

(ON_SKYPE)

---

[grammar] ~57-~57: Did you mean the communication tool “Slack” (= proper noun, capitalized)?
Context: ...lines 1. Discuss issues in our various slack channels when necessary 2. Please do no...

(ON_SKYPE)

---

[typographical] ~57-~57: Consider adding a comma here.
Context: ...ur various slack channels when necessary 2. Please do not derail or troll issues. 3. Keep...

(PLEASE_COMMA)

DOCUMENTATION.md

[grammar] ~25-~25: The modal verb ‘should’ requires the verb’s base form.
Context: ...f docs.talawa.io should automatically launched in your browser at http://localhost:300...

(MD_BASEFORM)

---

[grammar] ~26-~26: Did you mean the formatting language “Markdown” (= proper noun)?
Context: ...ttp://localhost:3000/ 1. Add/modify the markdown documents to the docs/ directory of t...

(MARKDOWN_NNP)

PR_GUIDELINES.md

[uncategorized] ~2-~2: Loose punctuation mark.
Context: # Pull Request Guidelines 👍🎉 First off, thanks for taking t...

(UNLIKELY_OPENING_PUNCTUATION)

---

[style] ~4-~4: Consider a shorter alternative to avoid wordiness.
Context: ...ing the time to contribute! 🎉👍 In order to give everyone a chance to submit a pull...

(IN_ORDER_TO_PREMIUM)

---

[style] ~46-~46: Style-wise, it’s not ideal to insert an adverb (‘manually’) in the middle of an infinitive construction (‘to test’). Try moving the adverb to avoid split infinitives.
Context: ..., you'll need to tell us what steps you followed to manually test your changes. 1. Please read our [CONTRIBUTING.md](C...

(SPLIT_INFINITIVE)

---

[style] ~56-~56: As an alternative to the over-used intensifier ‘very’, consider replacing this phrase.
Context: ...o be closed. The quality of our code is very important to us. Therefore we make experienced ma...

(EN_WEAK_ADJECTIVE)

---

[uncategorized] ~56-~56: A comma may be missing after the conjunctive/linking adverb ‘Therefore’.
Context: ...ty of our code is very important to us. Therefore we make experienced maintainers of our ...

(SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)

---

[style] ~59-~59: Consider using a different verb for a more formal wording.
Context: ...check if all tests are passing; if not, fix the issues and then create a pull reque...

(FIX_RESOLVE)

---

[style] ~64-~64: This expression is wordy and overused. Consider replacing it with a more concise and formal alternative.
Context: ...wer your questions, but we'll get to it sooner or later. @mentioning someone just adds to the p...

(SOONER_OR_LATER)

---

[uncategorized] ~64-~64: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...adds to the pile of notifications we get and it won't make us look at your issue fas...

(COMMA_COMPOUND_SENTENCE)

---

[style] ~65-~65: Consider shortening or rephrasing this to strengthen your wording.
Context: ...ue faster. 1. Do not force push. If you make changes to your pull request, please simply add a ...

(MAKE_CHANGES)

README.md

[uncategorized] ~56-~56: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...)" videos are extremely helpful for new open source contributors.

(EN_COMPOUND_ADJECTIVE_INTERNAL)

INSTALLATION.md

[duplication] ~25-~25: Possible typo: you repeated a word
Context: ...](#running-talawa-admin) - Accessing Talawa-Admin - [Talawa-Admin Registration](#talawa-admin-registratio...

(ENGLISH_WORD_REPEAT_RULE)

---

[typographical] ~55-~55: It appears that a comma is missing.
Context: ... that follow. # Prerequisites In this section we'll explain how to set up all the pre...

(DURING_THAT_TIME_COMMA)

---

[uncategorized] ~61-~61: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: .... Basic git knowledge is required for open source contribution so make sure you're comfor...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[grammar] ~67-~67: The word “setup” is a noun. The verb is spelled with a space.
Context: ...avigate to the folder where you want to setup the repository. 2. Open a cmd (Window...

(NOUN_VERB_CONFUSION)

---

[grammar] ~68-~68: The operating system from Apple is written “macOS”.
Context: ...cmd (Windows) or terminal (Linux or MacOS) session in this folder. 1. An easy ...

(MAC_OS)

---

[uncategorized] ~70-~70: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...e option based on your OS. 3. For Our Open Source Contributor Software Developers: ...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[grammar] ~102-~102: The operating system from Apple is written “macOS”.
Context: ...node.jspackages in Windows, Linux and MacOS. 1. For Windows: 1. first install...

(MAC_OS)

---

[duplication] ~116-~116: Possible typo: you repeated a word
Context: ... 5. Save the document. 6. Exit notepad 7. Exit PowerShell 8. This will ensure...

(ENGLISH_WORD_REPEAT_RULE)

---

[grammar] ~119-~119: The operating system from Apple is written “macOS”.
Context: ...t version of node.js 2. For Linux and MacOS, use the terminal window. 1. install...

(MAC_OS)

---

[grammar] ~123-~123: The word “setup” is a noun. The verb is spelled with a white space.
Context: ... the respective recommended commands to setup your node environment 3. This wil...

(NOUN_VERB_CONFUSION)

---

[uncategorized] ~162-~162: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...at runtime. It is not a part of the repo and you will have to create it. For a sampl...

(COMMA_COMPOUND_SENTENCE)

---

[grammar] ~228-~228: The word “setup” is a noun. The verb is spelled with a space.
Context: ...E_KEY in .env file You may not want to setup reCAPTCHA since the project will still ...

(NOUN_VERB_CONFUSION)

---

[grammar] ~232-~232: The word “setup” is a noun. The verb is spelled with a space.
Context: ...ad the following steps. If you want to setup Google reCAPTCHA now, you may refer to ...

(NOUN_VERB_CONFUSION)

---

[typographical] ~246-~246: Except for inverted sentences, ‘need them’ requires a question mark at the end of the sentence.
Context: ...t need them or want to keep the console clean # Post Configuration Steps It's now t...

(MD_PRP_QUESTION_MARK)

---

[uncategorized] ~261-~261: Did you mean: “By default,”?
Context: ...n serve ``` ## Accessing Talawa-Admin By default talawa-admin runs on port `4321` on y...

(BY_DEFAULT_COMMA)

---

[grammar] ~311-~311: The word ‘lint’ is a noun or an adjective. A verb or adverb is missing or misspelled here, or maybe a comma is missing.
Context: ...w.webp) ## Linting code files You can lint your code files using this command: ``...

(PRP_MD_NN)

CONTRIBUTING.md

[style] ~27-~27: This expression usually appears with a “please” in front of it.
Context: ...DUCT.md) to understand what this means. Let us know immediately if you have unacceptable ex...

(INSERT_PLEASE)

---

[uncategorized] ~34-~34: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...)" videos are extremely helpful for new open source contributors. ## Ways to Contribute I...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[grammar] ~62-~62: A determiner may be missing.
Context: ...l Request guidelines](PR_GUIDELINES.md) is best resource to follow to start working on ...

(THE_SUPERLATIVE)

---

[uncategorized] ~68-~68: Loose punctuation mark.
Context: ...ushed to the main branch: - develop: For unstable code and bug fixing - `mai...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~69-~69: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...d bug fixing - main: Where the stable production ready code lies. This is our default branch. ...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[typographical] ~73-~73: Consider adding a comma.
Context: ...ultiple developers are working on issues there is bound to be a conflict of interest (...

(IF_THERE_COMMA)

---

[typographical] ~73-~73: Consider adding a comma after ‘Usually’ for more clarity.
Context: ...licts) among issues, PRs or even ideas. Usually these conflicts are resolved in a **Fir...

(RB_LY_COMMA)

---

[grammar] ~73-~73: Did you mean “served” (as in the idiom ‘first come, first served’)?
Context: ...ts are resolved in a First Come First Serve basis however there are certain excep...

(FIRST_SERVED)

---

[uncategorized] ~75-~75: Possible missing comma found.
Context: ... an extension or in conflict with other PRs it is important to ask the author of th...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[grammar] ~75-~75: Did you mean the communication tool “Slack” (= proper noun, capitalized)?
Context: ...tant to ask the author of the PR in the slack channel or in their PRs or issues thems...

(ON_SKYPE)

---

[style] ~77-~77: ‘Last but not the least’ might be wordy. Consider a shorter alternative.
Context: ...y and test that function when needed. - Last but not the least, communication is important make sure t...

(EN_WORDINESS_PREMIUM_LAST_BUT_NOT_THE_LEAST)

---

[grammar] ~77-~77: It seems that “to” is missing before the verb.
Context: ...t the least, communication is important make sure to talk to other contributors, in ...

(MISSING_TO_BETWEEN_BE_AND_VB)

---

[grammar] ~77-~77: Did you mean the communication tool “Slack” (= proper noun, capitalized)?
Context: ... other contributors, in these cases, in slack channel or in a issue/PR thread. - As a...

(ON_SKYPE)

---

[misspelling] ~77-~77: Use “an” instead of ‘a’ if the following word starts with a vowel sound, e.g. ‘an article’, ‘an hour’.
Context: ... in these cases, in slack channel or in a issue/PR thread. - As a last resort the...

(EN_A_VS_AN)

---

[typographical] ~78-~78: It appears that a comma is missing.
Context: ...el or in a issue/PR thread. - As a last resort the Admins would be responsible for dec...

(DURING_THAT_TIME_COMMA)

---

[grammar] ~135-~135: The operating system from Apple is written “macOS”.
Context: ...r packages can be found for Windows and MacOS. 6. The currently acceptable c...

(MAC_OS)

---

[uncategorized] ~165-~165: Possible missing comma found.
Context: ...using: git push origin <branch_name>.(Here branch name must be name of the branch ...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[uncategorized] ~165-~165: Possible missing article found.
Context: ...: git push origin <branch_name>.(Here branch name must be name of the branch you wan...

(AI_HYDRA_LEO_MISSING_THE)

---

[uncategorized] ~165-~165: Possible missing article found.
Context: ...branch_name>`.(Here branch name must be name of the branch you want to push the chan...

(AI_HYDRA_LEO_MISSING_THE)

---

[grammar] ~178-~178: Did you mean the communication tool “Slack” (= proper noun, capitalized)?
Context: ...dation/talawa) for the link to join our slack channel. 1. We also have a technical em...

(ON_SKYPE)

CODE_STYLE.md

[style] ~127-~127: Consider removing “of” to be more concise
Context: ...tories of src assets - This houses all of the static assets used in the project - `...

(ALL_OF_THE)

---

[style] ~128-~128: Consider removing “of” to be more concise
Context: ... in the project - css - This houses all of the css files used in the project - `imag...

(ALL_OF_THE)

---

[style] ~129-~129: Consider removing “of” to be more concise
Context: ... the project - images - This houses all of the images used in the project - scss -...

(ALL_OF_THE)

---

[style] ~130-~130: Consider removing “of” to be more concise
Context: ...in the project - scss - This houses all of the scss files used in the project - `c...

(ALL_OF_THE)

---

[grammar] ~134-~134: The singular proper name ‘Sass’ must be used with a third-person or a past tense verb.
Context: ...rms - _talawa.scss - Partial Sass file for Talawa - _utilities.scss - Pa...

(HE_VERB_AGR)

---

[grammar] ~135-~135: The singular proper name ‘Sass’ must be used with a third-person or a past tense verb.
Context: ... - _utilities.scss - Partial Sass file for utilities - _variables.scss -...

(HE_VERB_AGR)

---

[grammar] ~136-~136: The singular proper name ‘Sass’ must be used with a third-person or a past tense verb.
Context: ... - _variables.scss - Partial Sass file for variables - app.scss - Main S...

(HE_VERB_AGR)

---

[style] ~141-~141: Consider removing “of” to be more concise
Context: ...views/screens Constant - This houses all of the constants used in the project `GraphQl...

(ALL_OF_THE)

---

[style] ~143-~143: Consider removing “of” to be more concise
Context: ...in the project GraphQl - This houses all of the GraphQL queries and mutations used in t...

(ALL_OF_THE)

---

[style] ~145-~145: Consider removing “of” to be more concise
Context: ...in the project screens - This houses all of the views/screens to be navigated through i...

(ALL_OF_THE)

---

[style] ~147-~147: Consider removing “of” to be more concise
Context: ... in Talawa-Admin state - This houses all of the state management code for the project ...

(ALL_OF_THE)

---

[uncategorized] ~165-~165: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...following order: - React imports - Third party imports - Local imports If there is...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

.github/workflows/README.md

[uncategorized] ~13-~13: Possible missing comma found.
Context: ...ding on the type of workflow. Whenever possible you must ensure that: 1. The file roles...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[duplication] ~24-~24: Possible typo: you repeated a word
Context: ...ors: 1. Place all actions related to to this in the pull-request-target.yml f...

(ENGLISH_WORD_REPEAT_RULE)

---

[uncategorized] ~35-~35: The abbreviation “e.g.” (= for example) requires two periods.
Context: ...orrectly if they have a dedicated file (eg. CodeQL) ## Scripts Follow these gui...

(E_G)

CODE_OF_CONDUCT.md

[duplication] ~11-~11: Possible typo: you repeated a word
Context: ...-responsibilities) - Scope - Enforcement - Enforcement Guidelines ...

(ENGLISH_WORD_REPEAT_RULE)

🪛 Markdownlint (0.37.0)

DOCUMENTATION.md

25-25: null
Bare URL used

(MD034, no-bare-urls)

PR_GUIDELINES.md

31-31: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

39-39: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

README.md

53-53: null
Multiple spaces after hash on atx style heading

(MD019, no-multiple-space-atx)

INSTALLATION.md

321-321: Expected: h3; Actual: h4
Heading levels should only increment by one level at a time

(MD001, heading-increment)

---

33-33: Expected: 4; Actual: 6
Unordered list indentation

(MD007, ul-indent)

---

34-34: Expected: 4; Actual: 6
Unordered list indentation

(MD007, ul-indent)

---

95-95: null
Dollar signs used before commands without showing output

(MD014, commands-show-output)

---

105-105: null
Bare URL used

(MD034, no-bare-urls)

---

142-142: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

154-154: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

164-164: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

188-188: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

194-194: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

200-200: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

208-208: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

214-214: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

220-220: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

240-240: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

256-256: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

264-264: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

270-270: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

292-292: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

300-300: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

313-313: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

327-327: Expected: fenced; Actual: indented
Code block style

(MD046, code-block-style)

---

335-335: Expected: fenced; Actual: indented
Code block style

(MD046, code-block-style)

---

178-178: Expected: #setting-up-react_app_talawa_url-in-env-file; Actual: #setting-up-REACT_APP_TALAWA_URL-in-env-file
Link fragments should be valid

(MD051, link-fragments)

---

178-178: Expected: #setting-up-react_app_recaptcha_site_key-in-env-file; Actual: #setting-up-REACT_APP_RECAPTCHA_SITE_KEY-in-env-file
Link fragments should be valid

(MD051, link-fragments)

CONTRIBUTING.md

104-104: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

113-113: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

128-128: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

139-139: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

143-143: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

158-158: null
No empty links

(MD042, no-empty-links)

---

159-159: null
No empty links

(MD042, no-empty-links)

---

161-161: null
No empty links

(MD042, no-empty-links)

CODE_STYLE.md

128-128: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)

---

129-129: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)

---

130-130: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)

---

131-131: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)

---

132-132: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)

---

133-133: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)

---

134-134: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)

---

135-135: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)

---

136-136: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)

---

137-137: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)

---

164-164: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)

---

165-165: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)

---

166-166: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)

---

57-57: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

73-73: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

75-75: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

92-92: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

190-190: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

230-230: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

58-58: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

65-65: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

78-78: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

95-95: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

158-158: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

173-173: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

181-181: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

239-239: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

245-245: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

251-251: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

.github/ISSUE_TEMPLATE/bug-report.md

36-36: null
Bare URL used

(MD034, no-bare-urls)

---

33-33: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

.github/ISSUE_TEMPLATE/feature-request.md

28-28: null
Bare URL used

(MD034, no-bare-urls)

---

25-25: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

🪛 Ruff (0.8.2)

.github/workflows/eslint_disable_check.py

61-61: Loop control variable dirs not used within loop body

Rename unused dirs to _dirs

(B007)

.github/workflows/compare_translations.py

135-135: Within an except clause, raise exceptions with raise ... from err or raise ... from None to distinguish them from errors in exception handling

(B904)

🔇 Additional comments (11)

public/manifest.json (1)

16-16: Verify the new image path structure

The icon path has been updated to include the "images/" directory. Let's verify this change.

✅ Verification successful

Image path structure is correctly implemented ✓

The verification confirms that:

• The image exists at the new location public/images/logo512.png
• The manifest.json correctly references the new path images/logo512.png
• No other files reference the old path
• The old location public/logo512.png doesn't exist

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the existence of the logo file in the new location
# and check if any other files still reference the old path

# Check if the new image path exists
if [ -f "public/images/logo512.png" ]; then
    echo "✓ Image exists at new location"
else
    echo "✗ Image not found at public/images/logo512.png"
fi

# Check if the old location still exists (might indicate incomplete move)
if [ -f "public/logo512.png" ]; then
    echo "! Warning: Image still exists at old location"
fi

# Search for any references to the old path in the codebase
echo "Checking for references to old path:"
rg "logo512\.png" --type ts --type tsx --type js --type jsx --type json

Length of output: 326

---

Script:

#!/bin/bash
# Let's try a more comprehensive search without file type restrictions
# and also check the manifest file specifically

# Check manifest.json for all icon references
echo "=== Checking manifest.json ==="
cat public/manifest.json

# Search for any references to logo512.png in the entire codebase
echo -e "\n=== Searching for logo512.png references ==="
rg "logo512\.png"

# List all png files in the repository to verify image locations
echo -e "\n=== Listing all PNG files ==="
fd -e png

Length of output: 1280

public/locales/hi/errors.json (1)

1-11: Verify translations with native speakers

To ensure accuracy and cultural appropriateness of the Hindi translations, please have them reviewed by native speakers.

public/locales/hi/common.json (1)

79-79: Verify placeholder consistency across translations

The file uses different placeholder patterns ({{text}} and {{item}}). Ensure these are used consistently across all language files and correspond to the actual variables being passed.

Also applies to: 83-85, 97-97

✅ Verification successful

Placeholders are consistently used across all language files

After checking all language files (en, fr, hi, sp, zh), the placeholders {{text}} and {{item}} are used consistently for the same messages across all translations:

• {{text}} is used in "searchResultsFor"
• {{item}} is used in "addedSuccessfully", "updatedSuccessfully", "removedSuccessfully", and "searchBy"

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for placeholder consistency across language files
echo "Checking placeholder usage across language files..."
rg -g 'public/locales/*/common.json' '{{.*?}}' -A 1 -B 1

Length of output: 254

---

Script:

#!/bin/bash
# Check for placeholder consistency across language files
echo "Checking placeholder usage across language files..."
rg -g 'public/locales/*/common.json' '\{\{[^}]+\}\}' -A 1 -B 1

Length of output: 3821

config/vite.config.ts (1)

13-23: LGTM: Plugin configuration is comprehensive

The plugin setup includes all necessary components for React development with TypeScript, SVG support, and environment variables.

.eslintrc.json (2)

4-4: LGTM: Node.js environment addition is appropriate.

Adding the Node.js environment enables ESLint to recognize Node.js globals, which is necessary for the build tools and scripts.

---

139-141: Review the component definition rule.

The react/function-component-definition rule is disabled (set to 0). Consider enforcing a consistent component definition style.

✅ Verification successful

Consider keeping the current component definition rule setting.

Based on the codebase analysis, the project consistently uses arrow function components with TypeScript's React.FC type annotations. The current eslint rule setting (value: 0) allows this established pattern to continue while remaining flexible for any exceptions. Enforcing a strict function-declaration style would conflict with the project's existing conventions.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check current component definition styles in the codebase
ast-grep --pattern 'function $name() {
  return $$$
}'

ast-grep --pattern 'const $name = () => {
  return $$$
}'

Length of output: 116

---

Script:

#!/bin/bash
# Let's try a more comprehensive search for React components
# Search for function declarations
ast-grep --pattern 'function $name($$$) {
  $$$
  return $$$
}'

# Search for arrow function components
ast-grep --pattern 'const $name = ($$$) => {
  $$$
  return $$$
}'

# Search for files with .jsx or .tsx extension to understand the codebase better
fd '\.(jsx|tsx)$'

Length of output: 20811

---

Script:

#!/bin/bash
# Let's examine the actual React component implementations in a few key files
rg -U "^(function.*\{|const.*=.*=>.*\{).*return.*\}" --type tsx "src/components/" -A 1

Length of output: 114

---

Script:

#!/bin/bash
# Let's try a simpler approach to find component definitions
rg "^(function|const) \w+(\s*:\s*React|\s*=\s*\(.*\)\s*=>)" "src/components/"

Length of output: 2713

package.json (2)

73-76: LGTM: Vite configuration setup.

The Vite configuration setup with TypeScript and environment-specific settings is well structured.

---

2-3: Verify semantic versioning jump.

The version change from 0.1.0 to 3.0.0 is significant. Please ensure this follows semantic versioning principles and is documented in the changelog.

.github/workflows/README.md (1)

1-47: Verify scope of documentation changes

This new workflow documentation file appears to be outside the scope of the PR's stated objective of refactoring tests from Jest to Vitest. Consider submitting these documentation improvements as a separate PR to maintain focused changes.

🧰 Tools

🪛 LanguageTool

[uncategorized] ~13-~13: Possible missing comma found.
Context: ...ding on the type of workflow. Whenever possible you must ensure that: 1. The file roles...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[duplication] ~24-~24: Possible typo: you repeated a word
Context: ...ors: 1. Place all actions related to to this in the pull-request-target.yml f...

(ENGLISH_WORD_REPEAT_RULE)

---

[uncategorized] ~35-~35: The abbreviation “e.g.” (= for example) requires two periods.
Context: ...orrectly if they have a dedicated file (eg. CodeQL) ## Scripts Follow these gui...

(E_G)

CODE_OF_CONDUCT.md (2)

3-20: Well-structured table of contents implementation

The addition of a table of contents with proper HTML markers and consistent formatting improves document navigation.

🧰 Tools

🪛 LanguageTool

[duplication] ~11-~11: Possible typo: you repeated a word
Context: ...-responsibilities) - Scope - Enforcement - Enforcement Guidelines ...

(ENGLISH_WORD_REPEAT_RULE)

---

Line range hint 1-47: Verify scope of documentation changes

The addition of a table of contents to the Code of Conduct, while beneficial, appears to be outside the scope of the PR's stated objective of refactoring tests from Jest to Vitest. Consider submitting these documentation improvements as a separate PR to maintain focused changes.

🧰 Tools

🪛 LanguageTool

[duplication] ~11-~11: Possible typo: you repeated a word
Context: ...-responsibilities) - Scope - Enforcement - Enforcement Guidelines ...

(ENGLISH_WORD_REPEAT_RULE)

[coderabbitai]

⚠️ Potential issue

Critical: Icon size mismatch with filename

The size "16x16" is inconsistent with the filename logo192.png which suggests a 192x192 image. This mismatch will cause scaling issues and poor image quality when the app is installed.

Apply this diff to fix the size:

-      "sizes": "16x16"
+      "sizes": "192x192"

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	"sizes": "16x16"
	"sizes": "192x192"

[coderabbitai]

⚠️ Potential issue

Update stale action version for better compatibility

The current version of the action might have compatibility issues with the GitHub Actions runner.

-    - uses: actions/stale@v8
+    - uses: actions/stale@v9

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	- uses: actions/stale@v8
	with:
	- uses: actions/stale@v9
	with:

🧰 Tools

🪛 actionlint (1.7.4)

28-28: the runner of "actions/stale@v8" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

[coderabbitai]

💡 Codebase verification

Consider increasing operations-per-run limit to handle ~150 open items

With 154 open issues and PRs, the current limit of 30 operations per run means it would take about 5-6 days to process all stale items. Consider increasing this limit to 50-75 operations per run for more efficient stale item processing while still maintaining reasonable API usage.

🔗 Analysis chain

Verify operations-per-run limit

The current limit of 30 operations per run might be too low depending on your repository's size and activity level. This could result in stale items being processed over multiple days.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check repository statistics to determine if the operations limit is sufficient

# Get total open issues and PRs
gh api graphql -f query='
{
  repository(owner: "PalisadoesFoundation", name: "talawa-admin") {
    openIssues: issues(states: OPEN) {
      totalCount
    }
    openPRs: pullRequests(states: OPEN) {
      totalCount
    }
  }
}' | jq '.data.repository | .openIssues.totalCount + .openPRs.totalCount'

Length of output: 306

[coderabbitai]

⚠️ Potential issue

Fix typo in error message

Correct the spelling of "occurred".

-  "errorLoading": "Error occured while loading {{entity}} data"
+  "errorLoading": "Error occurred while loading {{entity}} data"

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	"errorLoading": "Error occured while loading {{entity}} data"
	"errorLoading": "Error occurred while loading {{entity}} data"

[coderabbitai]

⚠️ Potential issue

Complete truncated French translations

Several messages appear incomplete compared to their English counterparts.

-  "talawaApiUnavailable": "Le service Talawa-API n'est pas disponible !. ",
+  "talawaApiUnavailable": "Le service Talawa-API n'est pas disponible. Veuillez vérifier votre connectivité réseau.",
-  "notAuthorised": "Désolé! ",
+  "notAuthorised": "Désolé, vous n'êtes pas autorisé !",
-  "notFoundMsg": "Oops! ",
+  "notFoundMsg": "Oops ! La page que vous avez demandée n'a pas été trouvée !"

Also applies to: 5-5, 8-8

[coderabbitai]

⚠️ Potential issue

Update testing framework in tech stack section.

The tech stack section mentions "Jest & React Testing Library" but according to the PR objectives, the project is transitioning to Vitest. This should be updated to maintain consistency.

-Jest & React Testing Library for testing
+Vitest & React Testing Library for testing

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	- Jest & React Testing Library for testing
	- Vitest & React Testing Library for testing

[coderabbitai]

⚠️ Potential issue

Fix Node.js version specification.

Node.js v22.x is not yet released. Consider using a stable LTS version like v20.x.

-          node-version: '22.x'
+          node-version: '20.x'

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	node-version: '22.x'
	node-version: '20.x'

[coderabbitai]

⚠️ Potential issue

Fix shell command security issue.

The shell command needs proper quoting to prevent word splitting and injection vulnerabilities.

-        run: npx eslint ${CHANGED_FILES} && python .github/workflows/eslint_disable_check.py
+        run: npx eslint "${CHANGED_FILES}" && python .github/workflows/eslint_disable_check.py

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	run: npx eslint ${CHANGED_FILES} && python .github/workflows/eslint_disable_check.py
	run: npx eslint "${CHANGED_FILES}" && python .github/workflows/eslint_disable_check.py

🧰 Tools

🪛 actionlint (1.7.4)

62-62: shellcheck reported issue in this script: SC2086:info:1:12: Double quote to prevent globbing and word splitting

(shellcheck)

[coderabbitai]

⚠️ Potential issue

Fix broken image links.

The image links for CodeCov setup are using empty markdown links which won't render correctly.

-[![Code-cov-token.jpg](/public/images/codecov/Code-cov-token.jpg)]()
-[![addd-your-key.jpg](/public/images/codecov/addd-your-key.jpg)]()
-[![results.jpg](/public/images/codecov/results.jpg)]()
+![Code-cov-token.jpg](/public/images/codecov/Code-cov-token.jpg)
+![addd-your-key.jpg](/public/images/codecov/addd-your-key.jpg)
+![results.jpg](/public/images/codecov/results.jpg)

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	[]()
	[]()
	6. You will see your code coverage reports with every push to your repo after following these steps
	[]()
	
	
	6. You will see your code coverage reports with every push to your repo after following these steps
	

🧰 Tools

🪛 Markdownlint (0.37.0)

158-158: null
No empty links

(MD042, no-empty-links)

---

159-159: null
No empty links

(MD042, no-empty-links)

---

161-161: null
No empty links

(MD042, no-empty-links)

[coderabbitai]

⚠️ Potential issue

Update test command for Vitest.

The test command needs to be updated to use Vitest instead of Jest.

-         npm run test --watchAll=false --coverage
+         npm run vitest run --coverage

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	npm run test --watchAll=false --coverage
	npm run vitest run --coverage

[Ramneet04]

Could anyone tell me why I'm getting so many files changed? I just added one file change?? what wrong I did, I'm new to open source.

[Cioppolo14]

@Ramneet04 Something doesn't seem right here, there are over 1000 changed files. I am going to close this PR.

[Ramneet04]

I'll try again. I apologise for all that thing.