feat!: Migrate Testing Framework from Jest to Vitest of src/components/TableLoader/TableLoader.test.tsx

[swastikCommits]

What kind of change does this PR introduce?

Migration of testing framework from Jest to Vitest of src/components/TableLoader/TableLoader.test.tsx

Issue Number:

Fixes #2822

Did you add tests for your changes?

Yes

Snapshots/Videos:

Does this PR introduce a breaking change?

No

Other information

Added vitest.config.js file and changed the required functions from jest to vitest syntax.

Have you read the contributing guide?

Yes

Summary by CodeRabbit

Based on the comprehensive summary of changes, here are the concise release notes:

• New Features

  • Added comprehensive localization support for multiple languages (English, French, Hindi, Spanish, Chinese)
  • Introduced new configuration files for build and development processes
  • Enhanced GitHub Actions workflows for CI/CD
  • Implemented new scripts for project setup and maintenance

• Documentation

  • Updated README, CONTRIBUTING, and other documentation files
  • Added detailed installation and contribution guidelines
  • Introduced code style and issue reporting guidelines

• Configuration

  • Updated ESLint, Prettier, and TypeScript configurations
  • Added new Vite and Babel configurations
  • Implemented environment variable management

• Localization

  • Added translation files for common UI elements and error messages
  • Supported multiple languages: English, French, Hindi, Spanish, Chinese

• Testing

  • Introduced new testing configurations and mock utilities
  • Added custom test environment and scripts

• Chores

  • Updated project dependencies
  • Restructured project file organization
  • Enhanced GitHub workflow configurations

[coderabbitai]

Walkthrough

This pull request introduces comprehensive changes to the Talawa Admin project, focusing on configuration, testing, localization, and workflow improvements. The changes span multiple aspects of the project, including setting up new configuration files, migrating test suites from Jest to Vitest, adding localization support for multiple languages, and enhancing GitHub Actions workflows. The modifications aim to improve the project's development experience, code quality, and internationalization capabilities.

Changes

File/Directory	Change Summary
.coderabbit.yaml	New configuration file for CodeRabbit AI with language and review settings
.env.example	Added environment variables for development configuration
.eslintignore, .eslintrc.json	Updated linting configurations and ignore rules
.github/workflows/	Added and modified multiple workflow files for CI/CD processes
public/locales/	Added localization files for English, French, Hindi, Spanish, and Chinese
config/	Added Babel and Vite configuration files
scripts/	Added mock files, test environments, and utility scripts
package.json	Updated dependencies, scripts, and project configuration

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant Repo as Repository
    participant CI as GitHub Actions
    participant Test as Vitest
    participant Lint as ESLint
    participant Deploy as Deployment

    Dev->>Repo: Commits code changes
    Repo->>CI: Triggers workflows
    CI->>Lint: Run linting checks
    Lint-->>CI: Linting results
    CI->>Test: Run Vitest tests
    Test-->>CI: Test coverage report
    CI->>Deploy: Deploy if all checks pass

Loading

Assessment against linked issues

Objective	Addressed	Explanation
Refactor TableLoader.test.tsx from Jest to Vitest [#2822]	✅

Possibly related issues

• Refactor : src/components/CheckIn/TableRow.test.tsx from Jest to Vitest #2496: Refactor src/components/CheckIn/TableRow.test.tsx from Jest to Vitest
• Refactor : src/components/CheckIn/CheckInModal.test.tsx from Jest to Vitest #2494: Refactor src/components/CheckIn/CheckInModal.test.tsx from Jest to Vitest
• Refactor: src/components/AddOn/support/components/MainContent/MainContent.test.tsx from Jest to Vitest #2475: Refactor src/components/AddOn/support/components/MainContent/MainContent.test.tsx from Jest to Vitest

Possibly related PRs

• Refactored src/components/AddOn/core/AddOnEntry/AddOnEntry.test.tsx from Jest to Vitest #2501: Refactors tests from Jest to Vitest
• Migrated src/screens/CommunityProfile/* from Jest to Vitest #3115: Migrates tests from Jest to Vitest
• Improve Code Coverage in src/components/UserPortal/UserNavbar/UserNavbar.tsx #3117: Improves code coverage for UserNavbar component

Suggested labels

refactor

Suggested reviewers

• palisadoes
• varshith257
• pranshugupta54

Poem

🐰 A Rabbit's Refactoring Tale 🔧

In lines of code, a journey starts,
From Jest to Vitest, testing arts,
Configs dance, workflows align,
Locales bloom in every line!

Hop, hop, hooray! The code's now bright! 🌟

---

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: 22

🧹 Nitpick comments (57)

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

1-1: File should be moved to correct ISO language code directory

The file is located in public/locales/sp/errors.json, but according to ISO 639-1, the correct language code for Spanish is 'es'. The file should be moved to public/locales/es/errors.json.

Would you like me to help create a GitHub issue to track this file relocation task?

---

1-11: Standardize message formatting

The error messages have inconsistent formatting:

• Inconsistent use of exclamation marks
• Varying capitalization patterns
• Different punctuation styles

Consider standardizing the formatting across all messages for a more professional and consistent user experience.

Would you like me to propose a standardized version of all messages?

.github/workflows/issue.yml (3)

34-56: Simplify the label logic for better maintainability

The current label logic uses nested conditions and repeated API calls. Consider refactoring to:

1. Extract label sets into variables
2. Combine the conditions using a single API call

- if(labels.data.reduce((a, c)=>a||["dependencies"].includes(c.name), false))
-   await github.rest.issues.addLabels({
-     owner: context.repo.owner,
-     repo: context.repo.repo,
-     issue_number: context.issue.number,
-     labels: ["good first issue", "security"]
-   });
- else if(labels.data.reduce((a, c)=>a||["security", "ui/ux"].includes(c.name), false))
-   await github.rest.issues.addLabels({
-     owner: context.repo.owner,
-     repo: context.repo.repo,
-     issue_number: context.issue.number,
-     labels: ["good first issue"]
-   });
+ const existingLabels = labels.data.map(l => l.name);
+ const labelsToAdd = new Set();
+ 
+ if (existingLabels.includes('dependencies')) {
+   labelsToAdd.add('good first issue');
+   labelsToAdd.add('security');
+ } else if (existingLabels.some(l => ['security', 'ui/ux'].includes(l))) {
+   labelsToAdd.add('good first issue');
+ }
+ 
+ if (labelsToAdd.size > 0) {
+   await github.rest.issues.addLabels({
+     ...apiParams,
+     labels: Array.from(labelsToAdd)
+   });
+ }

---

58-65: Consider adding error handling to the greeting job

While the greeting configuration looks good, consider adding continue-on-error: true to prevent workflow failures if the greeting action encounters issues. This is especially important since this is a non-critical step.

  Issue-Greeting:
    name: Greeting Message to User
    runs-on: ubuntu-latest
    steps:
      - uses: actions/first-interaction@v1
+       continue-on-error: true
        with:
          repo-token: ${{ secrets.GITHUB_TOKEN }}

---

1-66: Fix workflow formatting issues

There are several minor formatting issues to address:

1. Fix indentation at line 15 (should be 4 spaces)
2. Remove extra blank lines at the end of the file

🧰 Tools

🪛 actionlint (1.7.4)

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)

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

config/vite.config.ts (1)

27-28: Update the comment to match the configured port.

Currently, the comment states the default port is 3000, but the code sets it to 4321. To avoid confusion, either update the comment to indicate that 4321 is used as the default or revert the port to 3000 as needed.

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

.github/workflows/eslint_disable_check.py (2)

39-39: Consider checking multi-line disable statements.
You are currently only checking for // eslint-disable. If you want to also catch multi-line comments such as /* eslint-disable */, you might enhance your regex accordingly.

---

61-61: Rename unused variable dirs to _dirs.
To silence the unused variable warning and align with Python best practices, rename dirs to _dirs.

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

setup.ts (1)

106-117: Consider using a consistent I/O pattern.
The file alternates between sync methods (readFileSync, writeFileSync) and async callbacks (readFile, callback). This can introduce implicit race conditions. Stick to either synchronous or asynchronous I/O throughout for consistency.

.husky/post-merge (1)

4-4: Consider also checking lock files.
If your repository uses package-lock.json or yarn.lock, you may want to detect changes to those files as well and run npm install or yarn install accordingly.

.husky/pre-commit (1)

5-5: Decide on lint fixes in the pre-commit hook.
You have a commented-out npm run lint:fix. Consider removing it if unnecessary or enabling it for automatic lint fixes before each commit.

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

11-12: Remove extra blank line to satisfy formatting rules.
The static analysis suggests removing the blank line to keep your code aligned with the Prettier configuration.

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

🧰 Tools

🪛 eslint

[error] 11-12: Delete ··⏎

(prettier/prettier)

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

5-7: Remove or define the @pdfme TSDoc tag.
The configuration may not recognize custom tags such as @pdfme. Consider removing it or defining the tag in your TSDoc configuration to avoid lint or build errors.

🧰 Tools

🪛 eslint

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

(tsdoc/syntax)

---

9-9: Add an explicit return type to the async setup method.
Static analysis suggests specifying a return type. For better code clarity and TypeScript consistency, explicitly declare the return type (e.g., Promise<void>).

- async setup() {
+ async setup(): Promise<void> {

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

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

10-13: Check for empty arrays with more specific messaging or structured error handling.
Currently, one generic error covers both empty template schemas and inputs. For improved debugging, consider separate error messages if ‘template.schemas.length’ is 0 or if ‘inputs.length’ is 0.

---

21-21: Use direct return instead of Promise.resolve(...).
In an async function, you can simply return new Uint8Array([...pdfHeader, ...mockContent]) without wrapping in Promise.resolve(...).

- return Promise.resolve(new Uint8Array([...pdfHeader, ...mockContent]));
+ return new Uint8Array([...pdfHeader, ...mockContent]);

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

5-11: Clarify the promise test.
This test checks if generate(...) returns a Promise. Consider removing the async from the test body or adding an await if other asynchronous checks follow in the same test.

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

14-35: Improve performance by parallel file reading if needed.
In large repositories, reading directories sequentially may be slow. Consider using concurrency or a library for parallel file traversal if performance becomes an issue.

---

38-46: Enhance TSDoc detection logic.
The current regex checks for /** ... */. To detect multiple doc blocks or inline commentary, consider more complex patterns or a TSDoc parser.

---

49-66: Provide feedback summary on CI.
When TSDoc issues are flagged, consider summarizing the total count or including direct links to documentation. This can help devs quickly remediate issues.

jest.config.js (2)

33-34: Address Prettier feedback regarding spacing or commas.

Static analysis indicates minor formatting issues on lines 33-34. These typically involve removing extra spaces or adding a trailing comma where expected. Consider adjusting to align with your project's Prettier configuration.

🧰 Tools

🪛 eslint

[error] 33-33: Delete ·

(prettier/prettier)

---

[error] 34-34: Insert ,

(prettier/prettier)

---

52-52: Double-check the "resetMocks" configuration.

Leaving resetMocks: false might lead to unexpected test behaviors if one test's mocks inadvertently affect subsequent tests. Ensure you have clear reasons for this setting, or consider enabling it for a cleaner test isolation approach.

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

87-92: Consider adding trailing commas to satisfy Prettier’s multi-argument style rules.

Prettier often expects trailing commas in multi-line arguments. If your project enforces this style, add them so that your code remains consistent with the configured rules.

🧰 Tools

🪛 eslint

[error] 89-89: Insert ,

(prettier/prettier)

---

[error] 92-92: Insert ,

(prettier/prettier)

.github/workflows/compare_translations.py (1)

135-135: Include the original exception context for better debugging.

Raising a new exception from the original one provides clearer error traces in Python 3. Consider incorporating the from e notation when re-raising.

 except json.JSONDecodeError as e:
-    raise ValueError(f"Error decoding JSON from file {filepath}: {e}")
+    raise ValueError(f"Error decoding JSON from file {filepath}: {e}") from e

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

36-44: Consider clarifying _valid_filename docstring vs. actual logic.

The docstring mentions “Determine whether filepath has the correct filename,” but this helper filters out files matching “.test.” or “.spec.” by returning False. Consider clarifying that it rejects test/spec files rather than affirming valid filenames.

---

69-79: Add support for additional binary or non-source extensions.

You currently exclude only .css, .jpg, .png, and .jpeg. If the repository has other file types (e.g., .gif, .svg), consider adding them here to avoid analyzing non-source files.

---

122-142: Use pathlib for safer path manipulations.

While os.walk and os.path.join work, consider using pathlib for more robust and readable path operations.

---

198-199: Correct docstring reference to "Analyze dart files."

The docstring says “Analyze dart files,” but the logic scans directories for line counts in various file types. Adjust this wording to accurately describe the script’s actual scope.

-"""Analyze dart files.
+"""Analyze source files for line count limit compliance.

---

267-267: Typo in comment.

Typo “voilated” should be “violated.”

-    # If the line rule is voilated then ...
+    # If the line rule is violated then ...

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

31-36: Fix no-bare-urls by embedding link and consider turning emphasis into a heading.

Markdownlint warns about the bare URL and suggests using [link text](...). Also, the line “Potential internship candidates” can be a heading to comply with the MD036 rule:

-**Potential internship candidates**
-
-Please read this if you are planning to apply for a Palisadoes Foundation internship 
-https://github.com/PalisadoesFoundation/talawa/issues/359
+### Potential internship candidates
+
+Please read this section if you are planning to apply for a Palisadoes Foundation internship. 
+[GitHub Issue #359](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: Fix markdown formatting issues in the internship section.

1. Use proper heading syntax instead of bold text
2. Convert bare URL to markdown link format

Apply these changes:

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

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

🧰 Tools

🪛 Markdownlint (0.37.0)

28-28: null
Bare URL used

(MD034, no-bare-urls)

---

25-25: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

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

17-17: Fix trailing spaces in branch patterns.

Remove trailing spaces after branch patterns for better YAML formatting.

Apply these changes:

-      - '**'  
+      - '**'
-      - '**'   
+      - '**'

Also applies to: 20-20

🧰 Tools

🪛 yamllint (1.35.1)

[error] 17-17: trailing spaces

(trailing-spaces)

.github/pull_request_template.md (2)

9-11: Enhance visibility of the branch warning.

The critical warning about PR target branch could be more visible.

Consider this format:

-NOTE!!!
-
-ONLY SUBMIT PRS AGAINST OUR `DEVELOP` BRANCH. THE DEFAULT IS `MAIN`, SO YOU WILL HAVE TO MODIFY THIS BEFORE SUBMITTING YOUR PR FOR REVIEW. PRS MADE AGAINST `MAIN` WILL BE CLOSED.
+⚠️ IMPORTANT
+
+> **Warning**
+> ONLY SUBMIT PRS AGAINST OUR `DEVELOP` BRANCH
+> - The default branch is `main` - you must change this before submitting
+> - PRs targeting `main` will be automatically closed

---

51-53: Consider adding a checkbox for contributing guide.

Make it easier for contributors to confirm they've read the guide.

Apply this change:

-**Have you read the [contributing guide](https://github.com/PalisadoesFoundation/talawa-admin/blob/master/CONTRIBUTING.md)?**
-
-<!--Yes or No-->
+- [ ] I have read and understood the [contributing guide](https://github.com/PalisadoesFoundation/talawa-admin/blob/master/CONTRIBUTING.md)

DOCUMENTATION.md (3)

22-23: Fix grammatical error in the introduction

There's a minor typo in the introduction.

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

---

25-25: Fix grammar in the local server description

The sentence has incorrect verb form.

-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

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

🪛 Markdownlint (0.37.0)

25-25: null
Bare URL used

(MD034, no-bare-urls)

---

26-29: Maintain consistent capitalization and improve formatting

1. "Markdown" should be capitalized as it's a proper noun
2. Consider using proper markdown formatting for the browser reference
3. Fix typo in "brower"

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

🧰 Tools

🪛 LanguageTool

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

(MARKDOWN_NNP)

.github/workflows/stale.yml (2)

28-43: Consider documenting the stale workflow configuration values

The stale workflow configuration is comprehensive, but adding comments to explain the chosen values would improve maintainability:

• Why 10 days before marking as stale?
• Why 180 days before closing?
• Why limit to 30 operations per run?

Add comments to explain the rationale:

 - uses: actions/stale@v8
   with:
     repo-token: ${{ secrets.GITHUB_TOKEN }}
+    # Mark issues as stale after 10 days of inactivity
     days-before-stale: 10
+    # Close stale issues after 180 days without activity
     days-before-close: 180
+    # Limit API operations to avoid rate limiting
     operations-per-run: 30

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

---

31-34: Consider shortening the stale messages

The current messages are quite lengthy. Consider making them more concise while maintaining the key information.

-        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-issue-message: 'Marking as stale due to 10 days of inactivity. Will close in 180 days if no updates. Please verify if the develop branch has resolved this 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.'
+        stale-pr-message: 'Marking as stale due to 10 days of inactivity. Will close in 180 days if no updates. Please check for conflicts with develop branch and request help if needed.'

.github/workflows/push.yml (2)

45-49: Optimize cache key strategy

The current cache key strategy could be improved to be more specific.

-          key: ${{ runner.os }}-code-coverage-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}
+          key: ${{ runner.os }}-node-${{ matrix.node-version }}-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}
           restore-keys: |
-            ${{ runner.os }}-code-coverage-${{ env.cache-name }}-
-            ${{ runner.os }}-code-coverage-
-            ${{ runner.os }}-
+            ${{ runner.os }}-node-${{ matrix.node-version }}-${{ env.cache-name }}-
+            ${{ runner.os }}-node-${{ matrix.node-version }}-

---

54-54: Consider adding test failure threshold

The test command could benefit from a coverage threshold to ensure minimum coverage requirements are met.

-      - run: npm run test -- --watchAll=false --coverage
+      - run: npm run test -- --watchAll=false --coverage --coverageThreshold='{"global":{"branches":"80","functions":"80","lines":"80","statements":"80"}}'

.github/workflows/README.md (3)

24-24: Fix typo in sentence

There's a duplicate word "to" in the sentence.

-      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

The abbreviation "eg." should be written as "e.g." with two periods.

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

---

41-47: Consider adding specific version requirements for linting tools

The script requirements section should specify minimum versions for the linting tools to ensure consistent checks across different environments.

 1. All scripts in this directory must be written in python3 for consistency.
 1. The python3 scripts must follow the following coding standards. Run these commands against your scripts before submitting PRs that modify or create python3 scripts in this directory.
-    1. Pycodestyle
-    1. Pydocstyle
-    1. Pylint
-    1. Flake8
+    1. Pycodestyle (>=2.10.0)
+    1. Pydocstyle (>=6.3.0)
+    1. Pylint (>=2.17.0)
+    1. Flake8 (>=6.0.0)

ISSUE_GUIDELINES.md (3)

5-5: Fix grammar in introduction

The sentence has article agreement issues and could be more concise.

-In order to give everyone a chance to submit a issues reports and contribute to the Talawa project, we have put restrictions in place.
+To give everyone a chance to submit issue reports and contribute to the Talawa project, we have put restrictions in place.

🧰 Tools

🪛 LanguageTool

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

(EN_A_VS_AN)

---

29-29: Fix sentence structure and remove duplicate content

The sentence contains duplicate content and formatting issues.

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

---

44-44: Capitalize "Slack" references

The word "Slack" is a proper noun and should be capitalized.

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

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

-1. Discuss issues in our various slack channels when necessary
+1. 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)

README.md (1)

53-53: Fix markdown heading formatting

Remove extra space after the hash symbol in the heading.

-#  Videos
+# Videos

🧰 Tools

🪛 Markdownlint (0.37.0)

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

(MD019, no-multiple-space-atx)

.eslintrc.json (1)

78-122: Consider adding overrides for test files.

The naming convention rules are quite strict and might be too restrictive for test files. Consider adding overrides for test files to allow more flexible naming patterns.

Add test file overrides:

{
  // ... existing config ...
+ "overrides": [
+   {
+     "files": ["**/*.test.tsx", "**/*.spec.tsx"],
+     "rules": {
+       "@typescript-eslint/naming-convention": [
+         "error",
+         {
+           "selector": "variable",
+           "format": ["camelCase", "UPPER_CASE", "PascalCase"],
+           "leadingUnderscore": "allow"
+         }
+       ]
+     }
+   }
+ ]
}

PR_GUIDELINES.md (3)

31-34: Add language specification to code blocks.

Code blocks should specify the language for proper syntax highlighting.

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

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

---

`39-42`: **Add language specification to code blocks.**

Code blocks should specify the language for proper syntax highlighting.

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

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

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

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

(MD040, fenced-code-language)

</details>

</details>

---

`56-57`: **Improve sentence structure and punctuation.**

The sentence about code quality could be improved for clarity and proper punctuation.

```diff
-Removing assigned reviewers from your Pull Request will cause it to be closed. The quality of our code is very important to us. Therefore we make experienced maintainers of our code base review your code.
+Removing assigned reviewers from your Pull Request will cause it to be closed. The quality of our code is crucial to us. Therefore, we ensure experienced maintainers review your code.

🧰 Tools

🪛 LanguageTool

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

(EN_WEAK_ADJECTIVE)

---

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

(SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)

CODE_STYLE.md (2)

120-121: Enhance testing requirements section

Consider adding more specific guidelines about testing, such as:

• Test file naming conventions
• Test coverage requirements
• Mocking strategies

Would you like me to propose a detailed testing guidelines section?

---

127-138: Improve directory structure documentation

The directory structure documentation could be enhanced by:

1. Adding examples for each directory
2. Explaining the purpose of each directory more thoroughly
3. Including guidelines for test file placement

Would you like me to propose an enhanced directory structure section with examples?

Also applies to: 139-149

🧰 Tools

🪛 LanguageTool

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

🪛 Markdownlint (0.37.0)

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)

CONTRIBUTING.md (1)

104-107: Add language identifier to code blocks

Specify the language for code blocks to enable syntax highlighting.

-```
+```bash
 npm install
 npm run test --watchAll=false --coverage

🧰 Tools

🪛 Markdownlint (0.37.0)

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

(MD040, fenced-code-language)

schema.graphql (2)

275-302: Add date validation for event start and end dates.

The Event type should enforce that endDate is after startDate when both are provided.

Consider adding a custom directive for date validation:

type Event {
  # ... other fields ...
-  endDate: Date
+  endDate: Date @constraint(greaterThan: "startDate")
  startDate: Date!
  # ... other fields ...
}

---

514-524: Add content moderation capabilities to ChatMessage.

Consider adding moderation status and reason fields for better content management.

Add moderation fields to ChatMessage:

type ChatMessage {
  # ... other fields ...
+  moderationStatus: ModerationStatus
+  moderationReason: String
+  moderatedBy: User
}

+enum ModerationStatus {
+  APPROVED
+  PENDING
+  REJECTED
+}

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 96a343e and bc43295.

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

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

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

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

🧰 Additional context used

📓 Learnings (1)

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

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

🪛 eslint

scripts/githooks/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)

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)

scripts/githooks/update-toc.js

[error] 11-12: Delete ··⏎

(prettier/prettier)

jest.config.js

[error] 33-33: Delete ·

(prettier/prettier)

---

[error] 34-34: Insert ,

(prettier/prettier)

🪛 Markdownlint (0.37.0)

README.md

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

(MD019, no-multiple-space-atx)

CODE_STYLE.md

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

57-57: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

73-73: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

75-75: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

92-92: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

190-190: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

230-230: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

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

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)

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)

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)

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

DOCUMENTATION.md

25-25: null
Bare URL used

(MD034, no-bare-urls)

🪛 LanguageTool

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)

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)

CODE_OF_CONDUCT.md

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

(ENGLISH_WORD_REPEAT_RULE)

ISSUE_GUIDELINES.md

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

(UNLIKELY_OPENING_PUNCTUATION)

---

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

(IN_ORDER_TO_PREMIUM)

---

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

(EN_A_VS_AN)

---

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

(PLEASE_COMMA)

---

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

(FIX_RESOLVE)

---

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

(MAKE_STYLE_BETTER)

---

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

(ON_SKYPE)

---

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

(ON_SKYPE)

---

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

(ON_SKYPE)

---

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

(PLEASE_COMMA)

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)

---

[uncategorized] ~163-~163: Possible missing comma found.
Context: ...odecov/results.jpg)]() 1. After making changes you can add them to git locally using `...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[uncategorized] ~164-~164: Possible missing comma found.
Context: ...o add all changes). 1. After adding the changes you need to commit them using `git comm...

(AI_HYDRA_LEO_MISSING_COMMA)

---

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

(AI_HYDRA_LEO_MISSING_COMMA)

---

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

(AI_HYDRA_LEO_MISSING_THE)

---

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

(AI_HYDRA_LEO_MISSING_THE)

---

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

(ON_SKYPE)

INSTALLATION.md

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

(ENGLISH_WORD_REPEAT_RULE)

---

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

(DURING_THAT_TIME_COMMA)

---

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

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

---

[uncategorized] ~278-~278: Possible missing comma found.
Context: ... navigate to the running talawa-admin's website you'll land at talawa-admin registratio...

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

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)

.github/workflows/README.md

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

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)

🪛 yamllint (1.35.1)

.github/workflows/push.yml

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 17-17: trailing spaces

(trailing-spaces)

---

[error] 18-18: trailing spaces

(trailing-spaces)

---

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

(indentation)

---

[error] 21-21: trailing spaces

(trailing-spaces)

---

[error] 50-50: trailing spaces

(trailing-spaces)

---

[warning] 62-62: too many blank lines

(1 > 0) (empty-lines)

.github/workflows/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/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/pull-request-target.yml

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 13-13: trailing spaces

(trailing-spaces)

---

[error] 15-15: trailing spaces

(trailing-spaces)

---

[error] 27-27: trailing spaces

(trailing-spaces)

---

[error] 28-28: trailing spaces

(trailing-spaces)

---

[error] 29-29: trailing spaces

(trailing-spaces)

---

[error] 31-31: trailing spaces

(trailing-spaces)

---

[error] 33-33: trailing spaces

(trailing-spaces)

---

[error] 34-34: trailing spaces

(trailing-spaces)

---

[error] 36-36: trailing spaces

(trailing-spaces)

---

[error] 41-41: trailing spaces

(trailing-spaces)

---

[error] 46-46: trailing spaces

(trailing-spaces)

---

[error] 71-71: trailing spaces

(trailing-spaces)

.github/workflows/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/stale.yml

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 20-20: trailing spaces

(trailing-spaces)

---

[error] 21-21: trailing spaces

(trailing-spaces)

🪛 actionlint (1.7.4)

.github/workflows/issue.yml

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

(action)

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

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

.github/workflows/issue.yml (2)

21-25: Verify the sparse checkout configuration

The sparse checkout is correctly configured to only download the required auto-label.json5 file, which is a good optimization. However, let's verify this file exists.

✅ Verification successful

Sparse checkout configuration is correctly set up

The sparse checkout configuration is correctly set up as the file .github/workflows/auto-label.json5 exists in the repository, matching the path specified in the sparse checkout configuration.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if the auto-label configuration file exists
fd -t f "auto-label.json5" .github/workflows/

Length of output: 80

---

1-11: Verify the existence of the referenced README.md file

The header comments reference a README.md file that should define what belongs in this workflow file.

Also, remove trailing spaces from line 6 to fix the formatting issue.

✅ Verification successful

README exists and provides clear guidelines for workflow files

The referenced README.md file exists and contains comprehensive guidelines for GitHub workflow files. The file issue.yml follows the correct naming convention as per the guidelines which state that "all actions related to issues" should be placed in the issues.yml file. The only minor issue is the trailing space in the header comment which should be removed.

• Remove trailing space from line 6: # Please read the README.md file in this directory that defines what should

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if the README exists in the workflows directory
fd -t f "README.md" .github/workflows/

Length of output: 66

---

Script:

#!/bin/bash
# Let's check the content of the README to verify if it contains guidelines for workflow files
cat .github/workflows/README.md

Length of output: 2105

🧰 Tools

🪛 yamllint (1.35.1)

[error] 6-6: trailing spaces

(trailing-spaces)

config/vite.config.ts (4)

1-5: Imports look good.

All required packages for a typical React + TypeScript Vite setup (React plugin, tsconfig paths, environment, and SVGR) are properly imported.

---

7-11: Build output directory is clear.

Specifying outDir as "build" is standard for production builds, aligning well with common deployment structures.

---

12-12: Consider specifying a base URL only if needed.

The current base is set to an empty string. This is typically used for subpath deployments or GitHub Pages. Confirm this is correct for your hosting environment; otherwise, consider removing it to rely on Vite defaults.

---

14-23: Plugins configuration is well-structured.

1. The React plugin is vital for JSX and related transformations.
2. viteTsconfigPaths() helps keep imports consistent with tsconfig.
3. The EnvironmentPlugin('all') usage is concise to expose environment variables.
4. svgrPlugin with icon: true is convenient for inline SVG usage.

setup.ts (1)

14-18: Great approach for environment defaults.
Copying .env.example to .env ensures consistent and predictable environment variables for new contributors. Keep verifying that .env.example remains comprehensive.

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

1-2: Consider alignment with Vitest environment.
Since this pull request focuses on migrating tests from Jest to Vitest, it’s worth noting that this custom environment relies on jest-environment-jsdom. If the project fully moves to Vitest, consider providing a similar polyfill for Vitest or verifying that this environment remains necessary.

---

9-15: Ensure globally patched polyfills remain valid in Vitest.
Once the environment is switched to Vitest, confirm that this.global.TextEncoder and this.global.TextDecoder remain valid. If not, replicate this patch differently (e.g., using a setup file).

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

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

25-27: Nice use of rejects.toThrow() for error handling.
The tests provide clear checks for invalid input scenarios, ensuring robust error handling.

Also applies to: 35-37, 44-45

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

5-11: Validate skip behavior.
Ensure these skipped files truly warrant exclusion from TSDoc checks (e.g., they may not contain meaningful TypeScript components). If TSDoc coverage becomes more strict, reevaluate skipping them.

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

10-10: Ignore missing return type hints in .js files.

The static analysis hints about missing return types are meant for TypeScript files. Since this is a .js file, you can safely disregard these warnings. The codebase’s guidelines explicitly advise against adding TypeScript-style type annotations in JavaScript files.

Also applies to: 20-20, 43-43

🧰 Tools

🪛 eslint

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

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

.github/workflows/talawa_admin_md_mdx_format_adjuster.py (1)

1-96: Well-structured script with clear documentation.

No issues found. The script is clean, logically organized, and meets the stated documentation standards.

.coderabbit.yaml (1)

1-18: No issues found.

The configuration is straightforward, and all settings appear consistent with typical usage.

public/manifest.json (1)

13-13: Verify icon changes for Progressive Web App compatibility.

Reducing the first icon size from 192x192 to 16x16 may affect the look of installed web apps on mobile devices. Also confirm that “images/logo512.png” is correctly referenced and bundled.

Also applies to: 16-16

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

2-2: Naming and labeling look good.

The updated identifiers (“Bug Report,” label “bug”) and empty assignees field conform to the improved naming conventions.

Also applies to: 4-6

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

2-6: LGTM! Metadata updates improve consistency.

The capitalization and formatting changes in the metadata section enhance template consistency.

.github/pull_request_template.md (1)

22-24: LGTM! Clear issue linking format.

The issue linking section is well-structured and provides clear instructions.

README.md (2)

45-51: LGTM! Well-organized documentation structure

The documentation section is well-structured with clear links to installation, contribution guidelines, and other important resources.

---

3-3: ⚠️ Potential issue

Fix broken Slack community link

The Slack community link points to the GitHub organization instead of the Slack workspace.

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

76-77: Verify token permissions scope.

The workflow uses GITHUB_TOKEN with first-interaction action. Ensure the token has minimal required permissions.

✅ Verification successful

Let me gather more information about the workflow permissions and token usage.

---

Let me check the other workflow files for any permission configurations and examine the first-interaction action usage.

---

The GITHUB_TOKEN usage with first-interaction action is safe and follows security best practices

The first-interaction action only requires minimal read access to identify first-time contributors and write access to create comments, which are automatically granted by the default GITHUB_TOKEN. The action is used in a pull_request_target workflow which is a secure context for handling first-time contributions. The token's scope is appropriately limited to the required functionality.

Key observations:

• The workflow only performs read operations (checking first-time contributors) and creates welcome comments
• No sensitive operations or elevated permissions are being used
• The action is an official GitHub action (actions/first-interaction@v1)
• The workflow follows the principle of least privilege

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check workflow permissions in the repository
gh api repos/:owner/:repo/actions/permissions --jq '.default_workflow_permissions'

Length of output: 322

---

Script:

#!/bin/bash
# Check the workflow file for permissions configuration
cat .github/workflows/pull-request-target.yml

# Search for other workflow files that might define permissions
fd -e yml -e yaml . .github/workflows/

Length of output: 3880

---

Script:

#!/bin/bash
# Check contents of other workflow files for permissions
cat .github/workflows/codeql-codescan.yml
cat .github/workflows/pull-request.yml
cat .github/workflows/push.yml

# Check first-interaction action documentation in the repository
fd -g "*first-interaction*" . .github/

Length of output: 12476

package.json (1)

2-3: Verify if version bump is necessary

The version has been bumped to 3.0.0, which indicates breaking changes. While migrating test frameworks is significant, verify if this warrants a major version bump according to semver.

CODE_OF_CONDUCT.md (1)

3-19: LGTM! Enhanced document navigation

The addition of a table of contents improves document navigation and readability.

🧰 Tools

🪛 LanguageTool

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

(ENGLISH_WORD_REPEAT_RULE)

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

222-226: LGTM! Good test coverage threshold.

Setting a high coverage threshold (95%) helps maintain code quality and ensures thorough testing.

schema.graphql (1)

861-876: Well-implemented pagination following Relay specification.

The PageInfo type correctly implements all required fields for Relay-style pagination.

[coderabbitai]

⚠️ Potential issue

Messages need to be translated to Spanish

The file is intended for Spanish localization but most messages are in English. All messages should be in Spanish for consistency.

Here's the corrected version with all messages in Spanish:

 {
-  "talawaApiUnavailable": "Talawa-API service is unavailable!. Is it running? Check your network connectivity too.",
+  "talawaApiUnavailable": "¡El servicio Talawa-API no está disponible! ¿Está funcionando? Verifique también su conectividad a la red.",
-  "notFound": "Not found",
+  "notFound": "No encontrado",
-  "unknownError": "An unknown error occurred. Please try again later. {{msg}}",
+  "unknownError": "Ocurrió un error desconocido. Por favor, inténtelo de nuevo más tarde. {{msg}}",
-  "notAuthorised": "Sorry! you are not Authorised!",
+  "notAuthorised": "¡Lo siento! No está autorizado.",
-  "errorSendingMail": "Error sending mail",
+  "errorSendingMail": "Error al enviar el correo",
-  "emailNotRegistered": "Email not registered",
+  "emailNotRegistered": "Correo electrónico no registrado",
-  "notFoundMsg": "Oops! The Page you requested was not found!",
+  "notFoundMsg": "¡Ups! La página que solicitó no fue encontrada.",
   "errorOccurredCouldntCreate": "Ocurrió un error. No se pudo crear {{entity}}",
   "errorLoading": "Ocurrió un error al cargar los datos de {{entity}}"
 }

📝 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

	{
	"talawaApiUnavailable": "Talawa-API service is unavailable!. Is it running? Check your network connectivity too.",
	"notFound": "Not found",
	"unknownError": "An unknown error occurred. Please try again later. {{msg}}",
	"notAuthorised": "Sorry! you are not Authorised!",
	"errorSendingMail": "Error sending mail",
	"emailNotRegistered": "Email not registered",
	"notFoundMsg": "Oops! The Page you requested was not found!",
	"errorOccurredCouldntCreate": "Ocurrió un error. No se pudo crear {{entity}}",
	"errorLoading": "Ocurrió un error al cargar los datos de {{entity}}"
	}
	{
	"talawaApiUnavailable": "¡El servicio Talawa-API no está disponible! ¿Está funcionando? Verifique también su conectividad a la red.",
	"notFound": "No encontrado",
	"unknownError": "Ocurrió un error desconocido. Por favor, inténtelo de nuevo más tarde. {{msg}}",
	"notAuthorised": "¡Lo siento! No está autorizado.",
	"errorSendingMail": "Error al enviar el correo",
	"emailNotRegistered": "Correo electrónico no registrado",
	"notFoundMsg": "¡Ups! La página que solicitó no fue encontrada.",
	"errorOccurredCouldntCreate": "Ocurrió un error. No se pudo crear {{entity}}",
	"errorLoading": "Ocurrió un error al cargar los datos de {{entity}}"
	}

[coderabbitai]

💡 Codebase verification

Update actions/github-script from v6 to v7

The latest version of actions/github-script is v7.0.1, while the workflow is using v6. Updating to v7 is recommended to get the latest features and security improvements.

• Update .github/workflows/issue.yml:29 to use actions/github-script@v7

🔗 Analysis chain

Update github-script action version

The current version of actions/github-script@v6 might be outdated according to the static analysis. Consider updating to the latest version.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check the latest version tag for github-script action
gh api repos/actions/github-script/releases/latest --jq .tag_name

Length of output: 74

🧰 Tools

🪛 actionlint (1.7.4)

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)

[coderabbitai]

🛠️ Refactor suggestion

Handle file read error before using file data.
Within the callback, add a check for err to avoid potential runtime errors if .env is unreadable or missing.

 fs.readFile('.env', 'utf8', (err, data) => {
+  if (err) {
+    console.error(`Error reading .env: ${err}`);
+    process.exit(1);
+  }
   const result = data.replace(`PORT=${port}`, `PORT=${customPort}`);
   fs.writeFileSync('.env', result, 'utf8');
 });

📝 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

	fs.readFile('.env', 'utf8', (err, data) => {
	const result = data.replace(`PORT=${port}`, `PORT=${customPort}`);
	fs.writeFileSync('.env', result, 'utf8');
	});
	}
	fs.readFile('.env', 'utf8', (err, data) => {
	if (err) {
	console.error(`Error reading .env: ${err}`);
	process.exit(1);
	}
	const result = data.replace(`PORT=${port}`, `PORT=${customPort}`);
	fs.writeFileSync('.env', result, 'utf8');
	});
	}

[coderabbitai]

💡 Codebase verification

The test should await the Promise returned by generate

Looking at the mock implementation in scripts/__mocks__/@pdfme/generator.ts, the generate function is indeed declared as async and returns a Promise<Uint8Array>. The current test doesn't await the Promise, which could lead to unreliable results. The test should be modified to await the Promise resolution as suggested in the review comment.

• scripts/__mocks__/@pdfme/generator.test.ts: Add await before calling generate and store the resolved value for assertion.

🔗 Analysis chain

Await the returned promise to confirm it resolves to Uint8Array.
Currently, the test uses expect(result).toBeInstanceOf(Uint8Array); without waiting for resolution. For an accurate check, use:

const resolved = await result;
expect(resolved).toBeInstanceOf(Uint8Array);

---

Let me verify if the generate function returns a Promise by checking its implementation or mock.

🏁 Scripts executed

The following scripts were executed for the analysis:

Error: No shell scripts found

---

Script:

#!/bin/bash
# Search for the mock implementation of generate function
ast-grep --pattern 'const generate = $_'

# Also search for any other relevant implementation
rg "generate.*=" -A 3

Length of output: 4646

[coderabbitai]

🛠️ Refactor suggestion

Remove or replace the hardcoded absolute path for portability.

Specifying an absolute path ('/Users/prathamesh/Desktop/Open-Source/palisadoes/talawa-admin/src') can cause issues for other team members or in different environments. Consider removing or replacing it with a more flexible, relative path.

 modulePaths: [
-    '/Users/prathamesh/Desktop/Open-Source/palisadoes/talawa-admin/src',
     '<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]

⚠️ Potential issue

Update test debugging section for Vitest

The test debugging section needs to be updated to reflect Vitest's debugging capabilities instead of Jest's.

Would you like me to help update the debugging documentation to reflect Vitest's features?

🧰 Tools

🪛 Markdownlint (0.37.0)

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)

[coderabbitai]

⚠️ Potential issue

Remove duplicate OrganizationCustomField type definition.

The OrganizationCustomField type is defined twice with identical fields.

Remove the duplicate definition to prevent schema conflicts:

-type OrganizationCustomField {
-  _id: ID!
-  name: String!
-  organizationId: String!
-  type: String!
-}

📝 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

	type OrganizationCustomField {
	_id: ID!
	name: String!
	organizationId: String!
	type: String!
	}
	type OrganizationCustomField {
	_id: ID!
	name: String!
	organizationId: String!
	type: String!
	}
	type OrganizationCustomField {
	_id: ID!
	name: String!
	organizationId: String!
	type: String!
	}

[coderabbitai]

🛠️ Refactor suggestion

Enhance authentication directive with role specifications.

The @auth directive should specify allowed roles to prevent unauthorized access.

Consider updating the directive to include role specifications:

-directive @auth on FIELD_DEFINITION
+directive @auth(requires: [UserType!]) on FIELD_DEFINITION

📝 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

	directive @auth on FIELD_DEFINITION
	directive @auth(requires: [UserType!]) on FIELD_DEFINITION

[coderabbitai]

🛠️ Refactor suggestion

Add password validation constraints in UserInput.

The schema should enforce password requirements to ensure security.

Consider adding a custom scalar or directive for password validation:

input UserInput {
  appLanguageCode: String
  email: EmailAddress!
  firstName: String!
  lastName: String!
-  password: String!
+  password: Password!
  selectedOrganization: ID!
}

+scalar Password @constraint(
+  minLength: 8
+  pattern: "^(?=.*[A-Za-z])(?=.*\\d)(?=.*[@$!%*#?&])[A-Za-z\\d@$!%*#?&]"
+)

Committable suggestion skipped: line range outside the PR's diff.

[coderabbitai]

🛠️ Refactor suggestion

Enhance mutation error handling with union types.

Many mutations lack proper error types, making it difficult for clients to handle errors gracefully.

Consider adding union types for mutation responses:

type Mutation {
-  acceptMembershipRequest(membershipRequestId: ID!): MembershipRequest!
+  acceptMembershipRequest(membershipRequestId: ID!): AcceptMembershipRequestResult!
  # ... other mutations ...
}

+union AcceptMembershipRequestResult = MembershipRequest | UnauthorizedError | NotFoundError
+
+type NotFoundError implements Error {
+  message: String!
+  entity: String!
+}

Committable suggestion skipped: line range outside the PR's diff.

[Cioppolo14]

This PR has too many submitted files that are out of scope of the original issue.

Please ensure the following:

1. Fetch the latest upstream/develop-postgres files
2. Create a new local branch based on the latest upstream/develop-postgres branch.
   1. Your new local branch must not have the same name
3. Make your PR modifications based on this new local branch
4. Submit your PRs against our develop-postgres branch.

Please ask the slack channels for assistance.

Closing