AgendaItemsContainer tests from Jest to vitest

[Kanishk-tiwari-045]

Refracting /src/components/AgendaItems/AgendaItemsContainer.test.tsx from Jest to Vitest

Issue Number:

Fixes #2488

---

Did you add tests for your changes?

No.

---

Snapshots/Videos:

---

If relevant, did you update the documentation?

No.

---

Does this PR introduce a breaking change?

No.

---

Other information:

No.

---

Have you read the contributing guide?

Yes.

---

Summary

Chores:

• Updated the test suite for the AgendaItemsContainer component from Jest to Vitest.
• Replaced Jest-specific functions with Vitest equivalents.

Summary by CodeRabbit

Release Notes

• Configuration

  • Added configuration files for project setup, including Babel, Vite, Jest, and ESLint
  • Updated environment configuration with new .env.example

• Localization

  • Added comprehensive localization support for English, French, Hindi, Spanish, and Chinese
  • Included translations for common UI elements, error messages, and system notifications

• Documentation

  • Updated README, INSTALLATION, CONTRIBUTING, and other documentation files
  • Added detailed guidelines for issue reporting and pull request submissions

• Workflows

  • Enhanced GitHub Actions workflows for CI/CD, including code quality checks, testing, and dependency management
  • Added scripts for linting, formatting, and pre-commit hooks

• Internationalization

  • Implemented multi-language support with detailed translation files
  • Added language-specific common and error message translations

• Development Tools

  • Updated package management configuration
  • Added new scripts for setup, testing, and code quality checks

[coderabbitai]

Walkthrough

This pull request introduces a comprehensive set of changes to the Talawa Admin project, focusing on configuration, testing infrastructure, localization, and project structure. The modifications span across multiple files and directories, including workflow configurations, testing scripts, localization files, and project-level configuration files. The changes aim to enhance the project's development environment, testing capabilities, and internationalization support.

Changes

File/Directory	Change Summary
.coderabbit.yaml	Added new configuration for CodeRabbit AI with review and auto-review settings
.env.example	Added environment variables for development configuration
.eslintrc.json	Updated ESLint configuration with new rules and plugins
.github/workflows/	Added and modified multiple workflow files for CI/CD, code quality, and testing
public/locales/	Added localization files for English, French, Hindi, Spanish, and Chinese
scripts/	Added new scripts for testing, Git hooks, and project setup
config/	Added Vite and Babel configuration files
package.json	Updated project dependencies, scripts, and configuration

Assessment against linked issues

Objective	Addressed	Explanation
Refactor AgendaItemsContainer.test.tsx to Vitest	❓	Partial configuration changes made, but specific test refactoring not visible in this PR

Possibly related issues

• Refactor : src/components/AgendaItems/AgendaItemsUpdateModal.test.tsx from Jest to Vitest #2491: Refactoring AgendaItemsUpdateModal.test.tsx to Vitest
• Refactor : src/components/AgendaItems/AgendaItemsPreviewModal.test.tsx from Jest to Vitest #2490: Refactoring AgendaItemsPreviewModal.test.tsx to Vitest
• Refactor : src/components/AgendaItems/AgendaItemsCreateModal.test.tsx from Jest to Vitest #2489: Refactoring AgendaItemsCreateModal.test.tsx to Vitest

Possibly related PRs

• Refactored src/components/AddOn/core/AddOnEntry/AddOnEntry.test.tsx from Jest to Vitest #2501: Refactoring tests from Jest to Vitest
• Refactor: src/screens/BlockUser from Jest to Vitest  #2606: Adding testing-related dependencies
• PR_1 - Streamline scripts in .github/workflows  #3114: Streamlining workflow scripts

Suggested labels

refactor, configuration, testing, localization

Suggested reviewers

• pranshugupta54
• varshith257
• mandeepnh5

Poem

🐰 A Rabbit's Code Odyssey 🌈

Config files dance, workflows sing,
Vitest and locales take wing.
From Jest to new, we boldly stride,
With CodeRabbit's wisdom as our guide!

Hop, hop, hurrah! 🎉

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

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

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

Our policies make our code better.

Reviewers

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

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

Reviewing Your Code

Your reviewer(s) will have the following roles:

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

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

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

Other

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

[coderabbitai]

Actionable comments posted: 25

🧹 Nitpick comments (61)

.github/workflows/stale.yml (4)

1-11: Enhance header documentation

The header references a README.md file but doesn't specify its exact location or content. Consider adding:

1. The full path to the referenced README.md
2. A brief summary of the workflow's purpose directly in the header

 ##############################################################################
 ##############################################################################
 #
 # NOTE!
 #
-# Please read the README.md file in this directory that defines what should 
+# Please read .github/workflows/README.md that defines workflow file guidelines
+# Purpose: This workflow automatically manages stale issues and pull requests
+# by marking and eventually closing them after periods of inactivity.
 # be placed in this file
 #
 ##############################################################################
 ##############################################################################

🧰 Tools

🪛 yamllint (1.35.1)

[error] 6-6: trailing spaces

(trailing-spaces)

---

14-16: Add comment explaining cron schedule

Consider adding a comment to explain the cron schedule for better maintainability.

 on:
   schedule:
+  # Runs at 00:00 UTC every day
   - cron: "0 0 * * *"

---

18-21: Remove trailing spaces

Fix YAML 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)

---

30-43: Consider using YAML anchors for message templates

The configuration could be more maintainable by using YAML anchors for common message parts and by organizing related configurations together.

+# Define common message parts using YAML anchors
+x-messages: &activity-notice
+  "Please check the develop branch for updates. Create a new issue if the problem persists."
+
 with:
   repo-token: ${{ secrets.GITHUB_TOKEN }}
+  # Issue messages
   stale-issue-message: 'This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.'
-  stale-pr-message: 'This pull request did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please verify it has no conflicts with the develop branch and rebase if needed. Mention it now if you need help or give permission to other people to finish your work.'
   close-issue-message: 'This issue did not get any activity in the past 180 days and thus has been closed. Please check if the newest release or develop branch has it fixed. Please, create a new issue if the issue is not fixed.'
+  # PR messages
+  stale-pr-message: 'This pull request did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please verify it has no conflicts with the develop branch and rebase if needed. Mention it now if you need help or give permission to other people to finish your work.'
   close-pr-message: 'This pull request did not get any activity in the past 180 days and thus has been closed.'
+  # Labels
   stale-issue-label: 'no-issue-activity'
   stale-pr-label: 'no-pr-activity'
+  # Timeframes
   days-before-stale: 10
   days-before-close: 180
+  # Behavior
   remove-stale-when-updated: true
   exempt-all-milestones: true
   exempt-pr-labels: 'wip'
   exempt-issue-labels: 'wip'
   operations-per-run: 30

Additionally, consider:

1. Adding exemptions for other common labels like 'blocked' or 'help wanted'
2. Adjusting the operations-per-run limit based on repository activity

.github/workflows/eslint_disable_check.py (3)

29-48: Ensure robust exception reporting in has_eslint_disable

While the current exception handling prints an error message, consider logging the specific error type (e.g., FileNotFoundError vs. PermissionError) to facilitate debugging and to differentiate among error conditions.

---

61-61: Apply static analysis hint to rename unused variable

The dirs variable in this loop is not used. Renaming it to _dirs indicates it is intentionally unused, aligning with Python best practices.

-for root, dirs, files in os.walk(os.path.join(directory, 'src')):
+for root, _dirs, 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)

---

49-73: Consider checking additional file types

The script only checks .tsx files (excluding .test.tsx) and setup.ts. If .jsx or plain .ts files can also include ESLint rules, you might expand checks to these or explicitly confirm they are not part of your project's structure.

🧰 Tools

🪛 Ruff (0.8.2)

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

Rename unused dirs to _dirs

(B007)

.husky/pre-commit (1)

4-5: Revisit commented out lint:fix command

The npm run lint:fix command is commented out. If your team’s process still requires automated lint fixes before committing, re-enable this command to ensure code consistency and avoid manual errors.

 npm run format:fix
-# npm run lint:fix
+npm run lint:fix
 npm run lint-staged

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

10-12: Remove extra blank line for consistency

There appears to be an extraneous line break after executing the command. Removing it maintains clean code formatting.

  execSync(command, { stdio: 'inherit' });
-  
+
});

🧰 Tools

🪛 eslint

[error] 11-12: Delete ··⏎

(prettier/prettier)

config/vite.config.ts (1)

27-28: Update comment to reflect the correct default port

The inline comment still references port 3000, while the assigned port is 4321. Aligning the comment with the actual configuration avoids confusion.

     // this ensures that the browser opens upon server start
-    // this sets a default port to 3000
+    // this sets a default port to 4321
    port: 4321,

.github/workflows/check-tsdoc.js (3)

13-35: Consider ignoring test/helper files by default or adding an allowlist.
This recursive file traversal picks up all .tsx files and then excludes some by name or .test.tsx. You might want to exclude test or helper files by pattern, rather than by explicit name, to avoid future maintenance overhead.

---

38-46: Be cautious with the regex approach to checking TSDoc.
Scanning for /** ... */ comments can produce false positives if a multiline block comment looks like TSDoc but isn’t intended as such. You might enhance the pattern to verify the presence of a @ tag like @param or @returns.

---

60-66: Parallel exit in case of missing TSDoc.
When you encounter missing TSDoc in multiple files, the script exits after listing them. That’s appropriate. However, if you decide to continue partial checks for other validations, consider collecting results rather than an immediate exit.

jest.config.js (1)

20-22: Check transform ignore patterns for uniform coverage.
You’re excluding node_modules but might need to exclude other system or build directories if you no longer plan to test with Jest.

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

43-59: Consider additional logging for clarity.
When skipping files because of the skip comment or name, you log the file name and reason. That’s helpful, but you might also log whether it was explicitly in the skip list or if it has the skip comment present.

🧰 Tools

🪛 eslint

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

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

.github/workflows/talawa_admin_md_mdx_format_adjuster.py (1)

45-65: Make file writes conditional but also track changes.
You only write back if new_content !== content, which is good. Additionally, consider reporting the changed lines or the number of changes made for better visibility in logs.

setup.ts (2)

13-19: Consider error handling if .env.example is missing

Creating .env based on .env.example is a nice approach. However, there's no handling for when .env.example itself is absent or unreadable. Consider adding a safety check or fallback in case this file is unavailable.

---

135-145: Consider validating user input for reCAPTCHA site key more robustly

The current validation logic calls validateRecaptcha(input) but lacks deeper checks or error messages beyond "Please try again." For broader user clarity, consider providing detailed reasons for invalid input or referencing a format specification.

.github/workflows/compare_translations.py (1)

134-135: Re-raise JSON errors with context

When re-raising exceptions, consider using Python's raise ... from e to preserve the original error context. For example:

-    raise ValueError(f"Error decoding JSON from file {filepath}: {e}")
+    raise ValueError(f"Error decoding JSON from file {filepath}: {e}") from e

This helps maintain a clearer traceback for debugging.

🧰 Tools

🪛 Ruff (0.8.2)

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)

.github/workflows/countline.py (2)

198-201: Update docstring to accurately reflect file extension checks

The docstring says “Analyze dart files” even though the script checks for various extensions. Consider updating it to reflect the actual usage or rename references to Dart if it’s no longer language-specific.

---

255-264: Use UTF-8 encoding for file reads if feasible

Currently, files are opened with 'latin-1'. If the repository’s default encoding is UTF-8, consider switching to 'utf-8' to avoid incorrectly reading multi-byte characters and to align with popular modern standards.

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

2-2: Fix punctuation in error message

The message has incorrect double punctuation "!."

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

---

5-5: Maintain consistent capitalization

"Authorised" should follow the American English spelling and not be capitalized mid-sentence.

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

---

10-10: Fix typo in error message

"occured" should be "occurred"

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

---

1-11: Standardize error message formatting

The error messages have inconsistent formatting:

• Some end with exclamation marks, others with periods
• Inconsistent capitalization of sentence starts
• Mixed use of contractions

Consider standardizing the format across all messages. Would you like me to propose a consistent format for all messages?

.env.example (1)

29-31: Improve clarity of ALLOW_LOGS description

The description of ALLOW_LOGS could be more precise about the logging levels and their impact.

Consider this improvement:

-# If you want to logs Compiletime and Runtime error , warning and info write YES or if u want to  
-# keep the console clean leave it blank
-ALLOW_LOGS=
+# Controls application logging (YES/NO)
+# YES: Enables all logs (errors, warnings, info)
+# NO or blank: Minimal logging for production
+ALLOW_LOGS=

.github/pull_request_template.md (2)

22-25: Improve issue reference formatting.

The issue reference section could be more consistent with markdown formatting.

-**Issue Number:**
-
-Fixes #<!--Add related issue number here.-->
+**Issue Number:** #<!--Add related issue number here.-->

---

30-33: Enhance snapshots/videos section clarity.

Consider providing more specific guidance about when screenshots or videos are required.

-**Snapshots/Videos:**
-
-<!--Add snapshots or videos wherever possible.-->
+**Snapshots/Videos:**
+<!--
+Add snapshots or videos to demonstrate:
+- UI changes
+- New features
+- Bug fixes with visual components
+-->

DOCUMENTATION.md (3)

22-23: Fix typo in process description.

There's a grammatical error in the process description.

-The process in easy:
+The process is easy:

---

25-25: Correct grammar in Docusaurus launch description.

The sentence contains a grammatical error with the modal verb 'should'.

-    - A local version of `docs.talawa.io` should automatically launched in your browser at http://localhost:3000/
+    - A local version of `docs.talawa.io` should 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)

---

28-29: Fix typo in monitoring instructions.

There's a typo in the word "browser".

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

.github/workflows/push.yml (3)

29-29: Consider supporting multiple Node.js versions.

Currently, the workflow only tests against Node.js 22.x. Consider adding more LTS versions for better compatibility testing.

-        node-version: [22.x]
+        node-version: [18.x, 20.x, 22.x]

---

54-54: Consider separating test and coverage commands.

Running tests with coverage in a single command might slow down the CI pipeline. Consider splitting these into separate steps for better visibility and control.

-      - run: npm run test -- --watchAll=false --coverage
+      - name: Run tests
+        run: npm run test -- --watchAll=false
+      - name: Generate coverage report
+        run: npm run test:coverage

---

1-62: Fix YAML formatting issues.

The file has several formatting issues including trailing spaces and incorrect indentation.

• Remove trailing spaces (lines 6, 17, 18, 21, 50)
• Fix indentation in the env section to use 2 spaces
• Remove extra blank line at the end of the file

🧰 Tools

🪛 yamllint (1.35.1)

[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/README.md (3)

13-15: Fix minor grammatical issues

Add a comma after "Whenever possible" and fix the list numbering format.

-Whenever possible you must ensure that:
-1. The file roles below are maintained
-1. The sequence of the jobs in the workflows are maintained using [GitHub Action dependencies](https://docs.github.com/en/actions/learn-github-actions/managing-complex-workflows). 
+Whenever possible, you must ensure that:
+1. The file roles below are maintained
+2. The sequence of the jobs in the workflows are maintained using [GitHub Action dependencies](https://docs.github.com/en/actions/learn-github-actions/managing-complex-workflows). 

🧰 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 word "to".

-      1. Place all actions related to to this in the `pull-request-target.yml` file.
+      1. 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

Correct the abbreviation format for "e.g.".

-1. Jobs only work correctly if they have a dedicated file (eg. `CodeQL`)
+1. 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)

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

7-7: Remove trailing space in translation string

The Chinese translation for "noResultsFoundFor" has an unnecessary trailing space.

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

---

54-67: Maintain consistent key naming convention

Some keys use Title Case while others use camelCase. Consider using camelCase consistently for all keys.

-  "My Organizations": "我的组织",
-  "Dashboard": "仪表板",
-  "People": "人们",
-  "Events": "事件",
-  "Venues": "场地",
-  "Action Items": "行动项目",
-  "Posts": "帖子",
-  "Block/Unblock": "封锁/解除封锁",
-  "Advertisement": "广告",
-  "Funds": "资金",
-  "Membership Requests": "会员请求",
-  "Plugins": "插件",
-  "Plugin Store": "插件商店",
-  "Settings": "设置",
+  "myOrganizations": "我的组织",
+  "dashboard": "仪表板",
+  "people": "人们",
+  "events": "事件",
+  "venues": "场地",
+  "actionItems": "行动项目",
+  "posts": "帖子",
+  "blockUnblock": "封锁/解除封锁",
+  "advertisement": "广告",
+  "funds": "资金",
+  "membershipRequests": "会员请求",
+  "plugins": "插件",
+  "pluginStore": "插件商店",
+  "settings": "设置",

.github/workflows/issue.yml (2)

42-48: Improve code readability in label checking logic

The label checking logic could be more readable using array methods.

-            if(labels.data.reduce((a, c)=>a||["dependencies"].includes(c.name), false))
+            const hasLabel = (labelNames) => labels.data.some(label => labelNames.includes(label.name));
+            if(hasLabel(["dependencies"]))

---

65-66: Remove excessive blank lines

Remove the extra blank line at the end of the file.

          issue-message: "Congratulations on making your first Issue! :confetti_ball: If you haven't already, check out our [Contributing Guidelines](https://github.com/PalisadoesFoundation/talawa-admin/blob/develop/CONTRIBUTING.md) and [Issue Reporting Guidelines](https://github.com/PalisadoesFoundation/talawa-admin/blob/develop/ISSUE_GUIDELINES.md) to ensure that you are following our guidelines for contributing and making issues."

-

🧰 Tools

🪛 yamllint (1.35.1)

[warning] 66-66: too many blank lines

(1 > 0) (empty-lines)

ISSUE_GUIDELINES.md (2)

5-5: Fix grammatical error in introduction.

Change "a issues reports" to "issue reports":

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

---

44-44: Capitalize Slack references.

Slack is a proper noun and should be capitalized:

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

PR_GUIDELINES.md (2)

31-34: Add language identifiers to code blocks

For better syntax highlighting and consistency, add language identifiers to the code blocks.

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

- +bash
npm run lint:check
npm run format:check

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-57`: **Improve clarity in guidelines**

Consider adding a comma after "Therefore" and "and" for better readability:

```diff
-Therefore we make experienced maintainers of our code base review your code.
+Therefore, we make experienced maintainers of our code base review your code.

-notifications we get and it won't make us look at your issue faster.
+notifications we get, and it won't make us look at your issue faster.

Also applies to: 64-65

🧰 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 (3)

26-38: Consider adding version requirements for tech stack components.

The tech stack section would be more helpful if it included minimum version requirements or version ranges for each technology, especially for TypeScript, React.js, and testing frameworks.

---

58-69: Add language identifiers to code blocks.

Add syntax highlighting to the code blocks by specifying the language:

-```
+```jsx
<div className="myCustomClass">...</div>

🧰 Tools

🪛 Markdownlint (0.37.0)

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-115: Enhance code examples with TypeScript types.

Since the project uses TypeScript, consider updating the React-Bootstrap example to include type annotations:

-function BasicExample() {
+interface DropdownProps {
+  // Add relevant props
+}
+
+const BasicExample: React.FC<DropdownProps> = () => {
   return (
     <Dropdown>

🧰 Tools

🪛 Markdownlint (0.37.0)

92-92: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

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)

CONTRIBUTING.md (2)

104-107: Add language identifiers to code blocks.

Add syntax highlighting to the code blocks by specifying the language (e.g., bash or shell).

Also applies to: 113-117, 128-132, 139-141, 143-145

🧰 Tools

🪛 Markdownlint (0.37.0)

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

(MD040, fenced-code-language)

---

75-75: Fix capitalization of "Slack".

"Slack" is a proper noun and should be capitalized consistently throughout the document.

-slack channel
+Slack channel

Also applies to: 77-77, 178-178

🧰 Tools

🪛 LanguageTool

[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)

INSTALLATION.md (2)

33-34: Fix markdown heading hierarchy and list indentation.

The document has inconsistent heading levels and list indentation:

• Heading "pre-commit hook" should be h3 instead of h4
• List items under shell setup are over-indented (6 spaces instead of 4)

-      - pre-commit hook
+### pre-commit hook

-      1. All the commands...
+    1. All the commands...

Also applies to: 321-321

🧰 Tools

🪛 Markdownlint (0.37.0)

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

142-144: Add language hints to code blocks.

For better syntax highlighting and documentation clarity, specify the language for code blocks:

-```
+```bash
npm install

- +bash
npm run setup

-```
+```bash
cp .env.example .env

Also applies to: 154-156, 164-166

🧰 Tools

🪛 Markdownlint (0.37.0)

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

(MD040, fenced-code-language)

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

18-19: Standardize string format for consistency.

Some translation strings have inconsistent formats:

• Inconsistent use of "Atleast" vs "At least"
• Inconsistent capitalization in error messages

-    "atleast_8_char_long": "Atleast 8 Character long",
-    "atleast_6_char_long": "Atleast 6 Character long",
+    "atleast_8_char_long": "At least 8 characters long",
+    "atleast_6_char_long": "At least 6 characters long",

-    "email_invalid": "Email should have atleast 8 characters",
-    "Password_and_Confirm_password_mismatches.": "Password and Confirm password mismatches.",
+    "email_invalid": "Email should have at least 8 characters",
+    "Password_and_Confirm_password_mismatches": "Password and confirm password mismatch",

Also applies to: 23-24, 61-62

public/locales/sp/translation.json (1)

1-1485: Consider renaming the Spanish locale folder

The Spanish locale folder is named 'sp' but the more common ISO language code for Spanish is 'es'.

Consider renaming the folder from 'sp' to 'es' to follow ISO language code conventions.

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

33-36: Improve markdown formatting.

The new internship section has some markdown formatting issues:

1. Use proper heading syntax instead of bold text
2. Format the URL as a proper 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
+[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: Maintain consistent markdown formatting.

Apply the same markdown improvements as the bug report template:

-**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
+[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)

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

5-7: Optional: Remove or reconfigure the @pdfme TSDoc tag.

A static analysis hint flagged usage of @pdfme as an undefined tag. If this is a false positive, you can safely ignore it. Otherwise, consider adding a custom TSDoc configuration or removing the unknown tag.

🧰 Tools

🪛 eslint

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

(tsdoc/syntax)

---

9-9: Optional: Add explicit return type if you switch to TypeScript.

Static analysis might flag missing return types. Currently this file is .js, so you can ignore it if you aren’t using TypeScript. Alternatively, add annotations to align with TypeScript best practices.

🧰 Tools

🪛 eslint

[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)

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

14-21: Optimize workflow trigger configuration

The current trigger configuration runs on all branches, which could waste CI resources. Consider limiting it to specific branches or adding path filters to run only when relevant files change.

 on:
   pull_request:
     branches:
-      - '**'
+      - 'develop'
+      - 'main'
+    paths-ignore:
+      - '**.md'
+      - 'docs/**'
+      - '.github/*.md'

---

97-125: Externalize sensitive file patterns

Consider moving the list of sensitive files to a separate configuration file for better maintainability.

Create a new file .github/workflows/config/sensitive-files.yml:

sensitive_files:
  - .github/**
  - env.example
  # ... rest of the files

Then modify the workflow:

       with:
-         files: |
-           .github/**
-           env.example
-           # ... rest of the files
+         files: ${{ fromYaml(readFile('.github/workflows/config/sensitive-files.yml')).sensitive_files }}

---

22-265: Consider using reusable workflows

The current implementation has several jobs that could be extracted into reusable workflows for better maintainability and consistency across repositories.

Consider:

1. Moving common jobs like code quality checks and testing into reusable workflows
2. Creating a shared configuration for common settings like Node.js version and coverage thresholds
3. Using composite actions for repeated steps like Node.js setup

Example structure:

# .github/workflows/reusable/code-quality.yml
name: Code Quality
on:
  workflow_call:
    inputs:
      node-version:
        required: false
        default: '20.x'
        type: string
# ... rest of the implementation

This would simplify the main workflow and promote code reuse across repositories.

🧰 Tools

🪛 actionlint (1.7.4)

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)

🪛 yamllint (1.35.1)

[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)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 5550711 and f64ae5b.

⛔ 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)

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

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

• CODEOWNERS
• .eslintignore
• .node-version
• .prettierrc
• config/babel.config.cjs
• public/locales/zh/errors.json
• .github/dependabot.yaml
• public/locales/fr/common.json
• jest-preview.config.ts
• .github/workflows/auto-label.json5
• .prettierignore
• .lintstagedrc.json
• public/locales/zh/translation.json
• scripts/mocks/fileMock.js
• public/locales/hi/errors.json
• scripts/mocks/@dicebear/core.ts
• index.html
• public/locales/fr/errors.json
• public/locales/en/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.

🪛 Markdownlint (0.37.0)

DOCUMENTATION.md

25-25: null
Bare URL used

(MD034, no-bare-urls)

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)

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)

README.md

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

(MD019, no-multiple-space-atx)

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)

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)

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

🪛 LanguageTool

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)

---

[uncategorized] ~32-~32: The preposition “to” seems more likely in this position.
Context: ... PLEASE do not add markdown files in this repository. Add them to `talawa-do...

(AI_EN_LECTOR_REPLACEMENT_PREPOSITION)

CODE_OF_CONDUCT.md

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

(ENGLISH_WORD_REPEAT_RULE)

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

INSTALLATION.md

[uncategorized] ~3-~3: Possible missing comma found.
Context: ...tructions are written to be followed in sequence so make sure to go through each of them...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[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)

---

[uncategorized] ~61-~61: Possible missing comma found.
Context: ...` knowledge is required for open source contribution so make sure you're comfortable with it...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[uncategorized] ~64-~64: Possible missing comma found.
Context: ...ithub. ## Setting up this repository First you need a local copy of talawa-admin`...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[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] ~69-~69: Possible missing article found.
Context: ...to do this is to right-click and choose appropriate option based on your OS. 3. **For Our O...

(AI_HYDRA_LEO_MISSING_THE)

---

[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)

---

[uncategorized] ~118-~118: Possible missing comma found.
Context: ...ou are always using the correct version of node.js 2. For Linux and MacOS, use t...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[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] ~130-~130: Possible missing comma found.
Context: ...stall TypeScript, you can use the npm command which comes with node.js: ```bash np...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[uncategorized] ~158-~158: Possible missing comma found.
Context: ...ions in "setup" can be done manually as well and here's how to do it. - [Creating .e...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[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)

---

[uncategorized] ~162-~162: Possible missing comma found.
Context: ...ve to create it. For a sample of .env file there is a file named .env.example in...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[uncategorized] ~224-~224: Possible missing preposition found.
Context: ... For additional details, please refer theHow to Access the Talawa-API URL` sect...

(AI_HYDRA_LEO_MISSING_TO)

---

[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)

---

[uncategorized] ~234-~234: Possible missing comma found.
Context: ... service you set up during talawa-api installation as shown in this screenshot: ![reCAPTC...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[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)

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)

---

[uncategorized] ~27-~27: Possible missing comma found.
Context: ...reported. ### New Issues To create new issues follow these steps: 1. Your issue may ...

(AI_HYDRA_LEO_MISSING_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)

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)

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)

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)

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)

---

[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)

---

[grammar] ~165-~165: The past participle is required after “must be”.
Context: ...branch_name>`.(Here branch name must be name of the branch you want to push the chan...

(BE_VBP_IN)

---

[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)

🪛 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)

🪛 actionlint (1.7.4)

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

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

🪛 yamllint (1.35.1)

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

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

🪛 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 (21)

.github/workflows/eslint_disable_check.py (1)

91-120: Implementation looks straightforward and maintainable

The main function flow is clear, and the exit statuses are appropriately set for success or failure. No further concerns here.

.husky/post-merge (1)

1-4: Validate existence of previous commits in shallow clones

While git diff HEAD^ HEAD --exit-code works in most cases, certain CI/CD environments or fresh clones might lack the HEAD^ commit. Consider guarding against shallow clone scenarios, or explicitly handling the case where HEAD^ is not present.

jest.config.js (1)

1-71: Revisit the need for Jest configuration while migrating to Vitest.
Given the PR objective is to transition from Jest to Vitest, ensure that this Jest config isn’t contradicting or overlapping with your Vitest setup. If you are phasing out Jest entirely, consider removing or renaming this file to avoid confusion.

🧰 Tools

🪛 eslint

[error] 33-33: Delete ·

(prettier/prettier)

---

[error] 34-34: Insert ,

(prettier/prettier)

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

82-96: Review usage of localStorage across the entire codebase.
This script is great for preventing accidental direct usage of localStorage. You may also want to confirm any existing calls are replaced with your custom hook in older code.

🧰 Tools

🪛 eslint

[error] 89-89: Insert ,

(prettier/prettier)

---

[error] 92-92: Insert ,

(prettier/prettier)

setup.ts (1)

163-177: Include error handling for reading .env when logging errors is enabled

Similarly to prior file operations, the script reads .env without checking for err. Consider logging or throwing an error if file reading fails to help diagnose issues with environment variable updates.

Do you want me to generate a verification script to ensure that .env is properly handled if missing or locked?

.coderabbit.yaml (1)

1-17: LGTM!

Your .coderabbit.yaml configuration appears consistent and aligned with typical usage patterns. The auto-review and chat settings should streamline your review process effectively.

public/manifest.json (2)

13-13: Verify the icon size change

The size "16x16" seems incorrect for "logo192.png" as:

1. The filename suggests it's a 192x192 image
2. Small sizes (16x16) are already covered by favicon.ico

Please verify if this was an intentional change or if it should remain "192x192".

---

16-16: Verify the image path and file existence

The logo path has been updated to "images/logo512.png".

Run this script to verify the image exists in the new location:

✅ Verification successful

Image path in manifest.json is correctly configured

The verification confirms that the image file exists at the specified location public/images/logo512.png, which matches the path referenced in the manifest.json file. The configuration is correct and no further action is needed.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if the image exists in the new location
if [ -f "public/images/logo512.png" ]; then
    echo "✓ Image exists at new location"
else
    echo "✗ Image not found at public/images/logo512.png"
    echo "Searching for the image in other locations:"
    fd "logo512.png" public/
fi

Length of output: 109

.gitignore (1)

3-5: Reconsider ignoring lock files

While the comment suggests these files interfere with YARN, lock files are important for dependency consistency. Consider:

• Keep yarn.lock if using Yarn as the primary package manager
• Only ignore lock files from other package managers

Let's check which package manager is being used:

✅ Verification successful

Let me gather more information to determine the primary package manager.

---

Keep package-lock.json, remove other lock files from .gitignore

The repository is using npm as the primary package manager, evidenced by the presence of package-lock.json. The current .gitignore configuration should be adjusted:

• Remove yarn.lock from .gitignore as it's not the primary package manager
• Keep ignoring pnpm-lock.yaml to prevent lock file conflicts
• Add package-lock.json to .gitignore exceptions if it's currently ignored

This ensures dependency consistency while preventing conflicts from alternative package managers.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for package manager configuration
echo "Checking package manager configuration:"
if [ -f "package.json" ]; then
    echo "Package scripts:"
    jq '.scripts' package.json
fi

Length of output: 1261

---

Script:

#!/bin/bash
# Check for package manager configuration files
echo "Checking for package manager files:"
for file in package-lock.json yarn.lock pnpm-lock.yaml; do
    if [ -f "$file" ]; then
        echo "Found: $file"
    fi
done

# Check package.json for packageManager field
if [ -f "package.json" ]; then
    echo -e "\nChecking packageManager field:"
    jq '.packageManager' package.json
fi

# Look for any npm/yarn/pnpm config files
echo -e "\nChecking for config files:"
fd -H "^\.npm|\.yarn|\.pnpm"

Length of output: 634

.github/pull_request_template.md (1)

1-12: LGTM! Clear branching strategy guidance.

The added section effectively communicates the branching strategy and emphasizes the importance of submitting PRs against the develop branch.

.github/workflows/push.yml (1)

55-61: LGTM! Proper Codecov integration.

The Codecov integration is well configured with a unique name for each run and appropriate error handling.

package.json (1)

169-169: Verify Node.js version compatibility in CI/CD

The Node.js engine requirement of >=20.x is quite recent. Please ensure that all CI/CD pipelines are configured to use Node.js 20 or higher.

✅ Verification successful

Node.js version compatibility is properly configured in CI/CD

The CI/CD pipelines are already configured to use Node.js 22.x, which exceeds the required version of >=20.x specified in package.json. Both the push and pull request workflows are using Node.js 22.x, ensuring compatibility across all CI/CD operations.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check Node.js version in GitHub Actions workflows
rg "node-version:" .github/workflows/

Length of output: 369

CODE_OF_CONDUCT.md (1)

3-20: LGTM! Well-structured table of contents

The addition of a table of contents improves document navigation while maintaining the original content integrity.

🧰 Tools

🪛 LanguageTool

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

(ENGLISH_WORD_REPEAT_RULE)

schema.graphql (1)

1-1537: LGTM! Well-structured GraphQL schema.

The schema is comprehensive and follows GraphQL best practices:

• Clear type definitions with proper relationships
• Good use of interfaces for error handling
• Proper input type definitions for mutations

public/locales/hi/translation.json (2)

1053-1053: Verify date formatting placeholder

The translation string contains {{date}} placeholder for date formatting. Ensure the date format matches the locale's date format conventions.

✅ Verification successful

Date placeholder format is consistent across translations

The verification shows that all translation files consistently use the {{date}} placeholder in their respective "postedOn" strings, with appropriate positioning based on each language's grammar:

• Hindi (hi): {{date}} को पोस्ट किया गया (date at the beginning)
• English (en): Posted on {{date}} (date at the end)
• Spanish (sp): Publicado el {{date}} (date at the end)
• Chinese (zh): 发布于 {{date}} (date at the end)
• French (fr): Publié le {{date}} (date at the end)

The placeholder format is uniform, and its positioning respects each language's natural word order.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check date placeholder usage across translation files
rg -U "postedOn.*?\{.*?\}" public/locales/

Length of output: 409

---

229-230: Verify placeholder consistency in translation string

The translation string contains {{org}} and {{name}} placeholders. Please ensure these placeholders are consistently used across all language files and match the application's interpolation.

✅ Verification successful

Let me check the confirmation message placeholders as well to ensure complete consistency.

---

Placeholders are consistently used across all translation files

After checking both removeUserFrom and removeConfirmation strings across all language files (en, fr, hi, sp, zh), I can confirm that:

• The {{org}} placeholder is consistently used in the "removeUserFrom" string
• Both {{name}} and {{org}} placeholders are consistently used in the "removeConfirmation" string

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check placeholder consistency across translation files
rg -U "removeUserFrom.*?\{.*?\}" public/locales/

Length of output: 483

---

Script:

#!/bin/bash
# Check placeholder consistency in confirmation messages across translation files
rg -U "removeConfirmation.*?\{.*?\}" public/locales/

Length of output: 696

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

16-16: ⚠️ Potential issue

Fix capitalization in organization name

The word "palisados" should be capitalized as it's a proper noun referring to the Palisadoes Foundation.

-"fromPalisadoes": "Une application de code abierto de los voluntarios de la Fundación palisados",
+"fromPalisadoes": "Une application de code abierto de los voluntarios de la Fundación Palisadoes",

Likely invalid or redundant comment.

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

2-7: LGTM! Metadata changes follow conventions.

The changes to capitalization and label naming align with GitHub's conventions, where issue template titles are typically capitalized while labels use lowercase.

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

2-7: LGTM! Metadata changes are consistent.

The changes maintain consistency with the bug report template and follow GitHub's conventions.

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

1-1: Confirm the need for jest-environment-jsdom.

This file references jest-environment-jsdom. If you are fully migrating to Vitest, verify that you need this environment from Jest, or replace it with a suitable Vitest alternative if possible.

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

3-22: Implementation looks good.

This mock function properly checks for empty schemas or inputs and throws an appropriate error. The randomly generated content ensures variable output, mimicking PDF generation behavior.

[coderabbitai]

⚠️ Potential issue

Update actions/stale action version

The current version of the action may be outdated. Consider updating to the latest version.

-    - 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
	- uses: actions/stale@v9

🧰 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]

⚠️ Potential issue

Avoid absolute paths for local development.
Using an absolute path ('/Users/prathamesh/Desktop/Open-Source/palisadoes/talawa-admin/src') can break the config for other contributors. Consider relative paths or removing this entry if it’s non-essential.

-  modulePaths: [
-    '/Users/prathamesh/Desktop/Open-Source/palisadoes/talawa-admin/src',
-    '<rootDir>/src',
-  ],
+  modulePaths: [
+    '<rootDir>/src',
+  ],

📝 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

	modulePaths: [
	'/Users/prathamesh/Desktop/Open-Source/palisadoes/talawa-admin/src',
	'<rootDir>/src',
	],
	modulePaths: [
	'<rootDir>/src',
	],

[coderabbitai]

🛠️ Refactor suggestion

Consider special casing code blocks or HTML tags.
Escaping <, >, {, } might break code fences or legitimate HTML tags in Markdown. If your documentation uses inline HTML or code examples, you may need to skip specific fenced sections or tags to avoid unintended escapes.

[coderabbitai]

⚠️ Potential issue

Handle potential file read/write errors gracefully

Currently, the code does not handle or log errors if reading from or writing to .env fails (e.g., permission issues, file lock). Consider implementing basic error handling or fallback logic for better resilience.

[coderabbitai]

🛠️ Refactor suggestion

Validate connection checks for non-interactive environments

The script relies on checkConnection(url.origin) inside a loop. If this script is used in a non-interactive environment or the connection times out repeatedly, it could hang indefinitely. Consider adding retries or a timeout to avoid an infinite loop.

[coderabbitai]

⚠️ Potential issue

Await the promise before asserting its resolved value.

Currently, this test does not await the result, so result remains a Promise rather than a resolved Uint8Array. Update the test to ensure correct validation:

-  test('should resolve to a Uint8Array', async () => {
-    const result = generate({
-      template: { schemas: [] } as Template,
-      inputs: [],
-    });
-    expect(result).toBeInstanceOf(Uint8Array);
+  test('should resolve to a Uint8Array', async () => {
+    const resolvedValue = await generate({
+      template: { schemas: [] } as Template,
+      inputs: [],
+    });
+    expect(resolvedValue).toBeInstanceOf(Uint8Array);

📝 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

	test('should resolve to a Uint8Array', async () => {
	const result = generate({
	template: { schemas: [] } as Template,
	inputs: [],
	});
	expect(result).toBeInstanceOf(Uint8Array);
	});
	test('should resolve to a Uint8Array', async () => {
	const resolvedValue = await generate({
	template: { schemas: [] } as Template,
	inputs: [],
	});
	expect(resolvedValue).toBeInstanceOf(Uint8Array);
	});

[coderabbitai]

⚠️ Potential issue

Improve security of git operations

The current implementation may be vulnerable to command injection through the branch name.

       run: |
-        # Retrieve the complete branch name directly from the GitHub context
-        FULL_BRANCH_NAME=${{ github.base_ref }}
-        echo "FULL_Branch_NAME: $FULL_BRANCH_NAME"
-        
-        # Clone the specified repository using the extracted branch name
-        git clone --branch $FULL_BRANCH_NAME https://github.com/PalisadoesFoundation/talawa-api && ls -a 
+        # Validate branch name format
+        if [[ ! "${{ github.base_ref }}" =~ ^[a-zA-Z0-9_.-]+$ ]]; then
+          echo "Invalid branch name format"
+          exit 1
+        fi
+        
+        # Clone with validated branch name
+        git clone --depth 1 --branch "${{ github.base_ref }}" \
+          https://github.com/PalisadoesFoundation/talawa-api

📝 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

	- name: Clone API Repository
	run: |
	# Retrieve the complete branch name directly from the GitHub context
	FULL_BRANCH_NAME=${{ github.base_ref }}
	echo "FULL_Branch_NAME: $FULL_BRANCH_NAME"
	# Clone the specified repository using the extracted branch name
	git clone --branch $FULL_BRANCH_NAME https://github.com/PalisadoesFoundation/talawa-api && ls -a
	- name: Clone API Repository
	run: |
	# Validate branch name format
	if [[ ! "${{ github.base_ref }}" =~ ^[a-zA-Z0-9_.-]+$ ]]; then
	echo "Invalid branch name format"
	exit 1
	fi
	# Clone with validated branch name
	git clone --depth 1 --branch "${{ github.base_ref }}" \
	https://github.com/PalisadoesFoundation/talawa-api

🧰 Tools

🪛 yamllint (1.35.1)

[error] 249-249: trailing spaces

(trailing-spaces)

---

[error] 251-251: trailing spaces

(trailing-spaces)

[coderabbitai]

⚠️ Potential issue

Fix shell injection vulnerability in TypeScript compilation

The current implementation is vulnerable to shell injection attacks.

       run: |
-        for file in ${{ steps.changed-files.outputs.all_files }}; do
-          if [[ "$file" == *.ts || "$file" == *.tsx ]]; then
-            npx tsc --noEmit "$file"
-          fi
-        done
+        echo '${{ steps.changed-files.outputs.all_files }}' | tr ' ' '\n' | while read -r file; do
+          if [[ "$file" =~ \.(ts|tsx)$ ]]; then
+            npx tsc --noEmit "$file"
+          fi
+        done

📝 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

	- name: TypeScript compilation for changed files
	run: |
	for file in ${{ steps.changed-files.outputs.all_files }}; do
	if [[ "$file" == *.ts || "$file" == *.tsx ]]; then
	npx tsc --noEmit "$file"
	fi
	done
	- name: TypeScript compilation for changed files
	run: |
	echo '${{ steps.changed-files.outputs.all_files }}' | tr ' ' '\n' | while read -r file; do
	if [[ "$file" =~ \.(ts|tsx)$ ]]; then
	npx tsc --noEmit "$file"
	fi
	done

[coderabbitai]

⚠️ Potential issue

Use LTS version of Node.js

Node.js 22.x is not yet stable. Use an LTS version for better stability and security.

       uses: actions/setup-node@v4
       with:
-         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

	- name: Set up Node.js
	uses: actions/setup-node@v4
	with:
	node-version: '22.x'
	- name: Set up Node.js
	uses: actions/setup-node@v4
	with:
	node-version: '20.x'

[coderabbitai]

⚠️ Potential issue

Fix shell command security issues

The current implementation has potential shell injection vulnerabilities and globbing issues.

       env: 
-         CHANGED_FILES: ${{ steps.changed_files.outputs.all_changed_files }}
-       run: npx eslint ${CHANGED_FILES} && python .github/workflows/eslint_disable_check.py
+         CHANGED_FILES: ${{ steps.changed-files.outputs.all_changed_files }}
+       run: |
+         if [ -n "$CHANGED_FILES" ]; then
+           echo "$CHANGED_FILES" | tr ' ' '\n' | xargs npx eslint
+         fi
+         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

	CHANGED_FILES: ${{ steps.changed_files.outputs.all_changed_files }}
	run: npx eslint ${CHANGED_FILES} && python .github/workflows/eslint_disable_check.py
	env:
	CHANGED_FILES: ${{ steps.changed-files.outputs.all_changed_files }}
	run: |
	if [ -n "$CHANGED_FILES" ]; then
	echo "$CHANGED_FILES" | tr ' ' '\n' | xargs npx eslint
	fi
	python .github/workflows/eslint_disable_check.py

🧰 Tools

🪛 actionlint (1.7.4)

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)