Feature/refactor use session to vitest

[vivekbisen04]

Pull Request Title

Refactor: src/utils/useSession.test.tsx from Jest to Vitest #2754

---

What kind of change does this PR introduce?

Refactoring from Jest to Vitest for the specified test file.

---

Issue Number

Fixes #2754

---

Did you add tests for your changes?

Yes, all test cases were updated and verified to work with Vitest.

---

Snapshots/Videos

---

If relevant, did you update the documentation?

Not applicable, as this is a refactor of existing tests.

---

Summary

• Replaced Jest-specific functions and mocks with their Vitest equivalents.
• Renamed the test file from .test.tsx to .spec.tsx.
• Ensured all tests pass after migration using npm run test:vitest.

---

Does this PR introduce a breaking change?

No, it is a refactor of existing test cases with no changes to the codebase logic.

---

Other Information

• Followed Vitest documentation and the base Vitest configuration from PR #2457.

---

Have you read the contributing guide?

Yes.

---

Acceptance Criteria Recap

1. Replace Jest functions/mocks: Ensure all test cases are refactored using Vitest's features.
2. Rename the test file: Change the suffix to .spec.*.
3. Pass all tests: Run npm run test:vitest to ensure success.
4. Maintain 100% test coverage: Validate and attach proof in the PR description.

---

Additional Notes

If there are any discrepancies between test coverage or other configurations, feel free to com

Summary by CodeRabbit

• New Features

  • Introduced a new configuration file for a YAML language server with various review-related settings.
  • Added a new .env.example file with key environment variables for application configuration.
  • Implemented a new GitHub Actions workflow for managing stale issues and pull requests.
  • Added comprehensive localization support with new JSON files for multiple languages (English, French, Hindi, Spanish, Chinese).

• Bug Fixes

  • Enhanced error handling in scripts to ensure better user feedback and debugging.

• Documentation

  • Updated and added various documentation files, including installation guides and contribution guidelines.
  • Improved the structure and clarity of the code style and issue reporting documents.

• Chores

  • Cleaned up and reorganized several configuration and setup files to improve maintainability.

[coderabbitai]

Walkthrough

This pull request introduces a comprehensive set of configuration files, development tools, and workflow enhancements for the Talawa Admin project. The changes span multiple aspects of the project, including environment setup, testing infrastructure, localization, and GitHub Actions workflows. The modifications aim to improve development processes, code quality, and project maintainability.

Changes

File/Directory	Change Summary
.coderabbit.yaml	New configuration file for AI-assisted code reviews
.env.example	New environment variable template with configuration options
.eslintignore, .eslintrc.json	Updated linting configurations and ignore rules
.github/workflows/	Multiple new and updated GitHub Actions workflows for CI/CD
config/	New Babel and Vite configuration files
public/locales/	Added localization files for multiple languages (en, fr, hi, sp, zh)
scripts/	New utility scripts for testing, githooks, and development setup
package.json	Updated dependencies, scripts, and project configuration

Assessment against linked issues

Objective	Addressed	Explanation
Refactor src/utils/useSession.test.tsx from Jest to Vitest [#2754]	✅

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/CheckInWrapper.test.tsx from Jest to Vitest #2495: Refactor src/components/CheckIn/CheckInWrapper.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

• Refactor Tests: Migrate src/screens/UserPortal/UserScreen/UserScreen.tsx from Jest to Vitest #2632: Refactors tests to migrate from Jest to Vitest
• Refactor : src/screens/OrgContribution component from Jest to Vitest #2729: Refactors tests for the UserScreen component
• fixed:#2475 Refactor: src/components/AddOn/support/components/MainContent/MainContent.test.tsx from Jest to Vitest #2843: Refactors tests for the MainContent component

Suggested reviewers

• @palisadoes

Poem

🐰 Hop, hop, hooray! Code's on its way!
Configuration dancing, workflows in play
From locales to tests, we've paved the way
Talawa Admin's magic, bright as day! 🌈

Tip

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

---

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

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

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

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

CodeRabbit Commands (Invoked using PR comments)

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

Other keywords and placeholders

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

Documentation and Community

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

[github-actions]

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

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

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

Our policies make our code better.

Reviewers

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

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

Reviewing Your Code

Your reviewer(s) will have the following roles:

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

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

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

Other

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

[github-actions]

Congratulations on making your first PR! 🎊 If you haven't already, check out our Contributing Guidelines and PR Reporting Guidelines to ensure that you are following our guidelines for contributing and creating PR.

[coderabbitai]

Actionable comments posted: 22

🧹 Nitpick comments (55)

DOCUMENTATION.md (2)

21-30: Fix grammar and consider consistent capitalization.

The instructions are clear, but there are a few minor improvements to consider:

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

Consider capitalizing "Markdown" when referring to the formatting language for consistency with technical documentation standards.

🧰 Tools

🪛 Markdownlint (0.37.0)

25-25: null
Bare URL used

(MD034, no-bare-urls)

🪛 LanguageTool

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

(MD_BASEFORM)

---

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

---

31-32: Improve preposition usage.

-***PLEASE*** do not add markdown files in this repository. Add them to `talawa-docs`!
+***PLEASE*** do not add markdown files to this repository. Add them to `talawa-docs`!

🧰 Tools

🪛 LanguageTool

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

(AI_EN_LECTOR_REPLACEMENT_PREPOSITION)

schema.graphql (8)

1-3: Add documentation for the auth directive.

The @auth directive lacks documentation explaining its purpose and usage. Consider adding documentation to improve schema clarity.

Add documentation like this:

+"""
+Directive for field-level authorization.
+Use this directive to protect fields that require authentication.
+"""
directive @auth on FIELD_DEFINITION

---

3-4: Add documentation for the role directive.

The @role directive lacks documentation explaining its purpose and requirements.

Add documentation like this:

+"""
+Directive for role-based access control.
+Use this directive to protect fields that require specific user types.
+"""
directive @role(requires: UserType) on FIELD_DEFINITION

---

618-625: Refactor createAdvertisement to use an input type.

The createAdvertisement mutation has multiple parameters that could be grouped into an input type. There's already a CreateAdvertisementInput type defined that could be used.

Refactor the mutation to use the input type:

-createAdvertisement(
-  endDate: Date!
-  link: String!
-  name: String!
-  orgId: ID!
-  startDate: Date!
-  type: String!
-): Advertisement!
+createAdvertisement(input: CreateAdvertisementInput!): Advertisement!

---

675-681: Standardize mutation naming conventions.

There's inconsistency in mutation naming. Some use "remove" (removePost) while others use "delete" (deleteAdvertisement) for similar operations.

Consider standardizing to either "remove" or "delete" prefix:

-removeAdvertisement(id: ID!): Advertisement
+deleteAdvertisement(id: ID!): Advertisement

# OR standardize all to "remove":
-deleteAdvertisement(id: ID!): DeletePayload!
+removeAdvertisement(id: ID!): DeletePayload!

---

1013-1013: Consider making agendaCategory query return type non-null.

The agendaCategory query takes a non-null ID but returns a nullable type. If the ID is invalid, it might be better to throw an error than return null.

Update the return type to be non-null:

-agendaCategory(id: ID!): AgendaCategory!
+agendaCategory(id: ID!): AgendaCategory!!

---

1021-1022: Add pagination support to eventsByOrganization query.

The eventsByOrganization query returns an array of events without pagination. For organizations with many events, this could lead to performance issues.

Consider adding pagination support similar to eventsByOrganizationConnection:

-eventsByOrganization(id: ID, orderBy: EventOrderByInput): [Event]
+eventsByOrganization(
+  id: ID,
+  orderBy: EventOrderByInput
+  first: Int
+  skip: Int
+  where: EventWhereInput
+): EventConnection!

---

1138-1138: Add documentation for custom scalars.

The URL scalar lacks documentation explaining its validation rules and expected format.

Add documentation:

+"""
+A URL scalar that validates URLs according to RFC 3986.
+Accepts both HTTP and HTTPS protocols.
+"""
scalar URL

---

1500-1508: Standardize enum value casing.

The WeekDays enum uses uppercase two-letter codes while other enums use UPPER_SNAKE_CASE.

Consider standardizing to UPPER_SNAKE_CASE:

enum WeekDays {
-  FR
-  MO
-  SA
-  SU
-  TH
-  TU
-  WE
+  FRIDAY
+  MONDAY
+  SATURDAY
+  SUNDAY
+  THURSDAY
+  TUESDAY
+  WEDNESDAY
}

setup.ts (2)

13-19: Graceful error handling for .env creation.
Currently, the code does not handle the possibility of the .env.example file being missing or unreadable. Consider adding try/catch or conditional checks around file operations to avoid unhandled errors.

---

72-76: Avoid permanent loop if connection cannot be established.
If the user repeatedly provides an invalid or unreachable endpoint, the script may loop indefinitely. Consider implementing a maximum retry limit or an option to exit gracefully.

.husky/post-merge (1)

1-4: Consider using npm ci or verifying lockfile changes.
Running npm install after each merge might introduce inconsistencies if the lockfile is not updated. Using npm ci (or verifying changes in package-lock.json) can help ensure consistent dependency installs.

scripts/__mocks__/@dicebear/core.ts (1)

1-5: Switch to vi.fn() in Vitest environment.
If the overall testing framework is Vitest, replace jest.fn() with vi.fn() for consistency.

.husky/pre-commit (3)

5-5: Consider removing or repurposing the commented lint command.
Leaving commented-out commands can create confusion and clutter.

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

---

7-7: Consider limiting type checks to CI to optimize pre-commit flow.
Running npm run typecheck on every commit can slow development if the codebase is large.

---

10-10: Avoid adding all changes automatically.
git add . in a pre-commit hook can unintentionally commit unrelated changes. Instead, consider only adding the changes that were explicitly staged.

-git add .
+git add --update

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

11-12: Remove the extra whitespace to comply with prettier.
The static analysis tool suggests removing the extra blank line for consistency.

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

🧰 Tools

🪛 eslint

[error] 11-12: Delete ··⏎

(prettier/prettier)

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

5-5: Define or remove the @pdfme tag.
Your TSDoc configuration may not recognize the custom @pdfme tag.

 /**
- * A custom environment to set the TextEncoder and TextDecoder variables, that is required by @pdfme ...
+ * A custom environment to set the TextEncoder and TextDecoder variables, that is required by the @pdfme library ...

🧰 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 for the setup method.
Your ESLint configuration requires return types for functions, including async methods.

  async setup(): Promise<void> {
    await super.setup();
    ...

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

18-20: Consider deterministic content for tests.
Random content generation might make tests nondeterministic. Use a seeded random or a fixed pattern if you want reproducible results.

-  const mockContent = Array.from({ length: contentSize }, () =>
-    Math.floor(Math.random() * 256),
-  );
+  // Optionally use a fixed seed or a static pattern for deterministic tests
+  const mockContent = new Array(contentSize).fill(42);

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

1-3: Consider consistent naming if migrating all tests to Vitest.
This file name ends with .test.ts and uses a Jest-like structure (e.g., describe, test, it). Since the PR objective is to refactor tests to Vitest, ensure that the test naming convention (.spec.ts) and test runner APIs are consistently updated.

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

13-35: Potential for improved concurrency.
Currently, directory reading and file checks happen sequentially. If performance or large directories become a concern, consider using Promise.all patterns.

jest.config.js (1)

1-3: Coverage threshold is set at 20%.
While 20% might be acceptable for now, consider gradually increasing this threshold to continuously improve code quality.

.github/workflows/talawa_admin_md_mdx_format_adjuster.py (2)

19-44: Ensure consistent handling of file content changes.
The code compares new_content to content (line 62) before writing back. This is good to prevent unnecessary file writes. However, if multiple threads/processes used this script concurrently (for example, in parallel builds), there could be a race condition overwriting changes in the same file. While not strictly an issue in typical usage here, you may consider adding a lock or concurrency-safe approach if multiple calls could happen simultaneously.

---

66-96: Consider fail-fast behavior or skip on missing directory.
Line 80 sets a required argument for --directory, and then code processes the files within that directory. If the directory does not exist, the script simply stops with an error (line 109). This is acceptable, but an alternative is to exit earlier or provide an auto-fix suggestion for the user if the directory might be misnamed.

Would you like me to propose a more user-friendly approach (e.g., a prompt or fallback to a default directory) if the user provides an invalid path?

.github/workflows/eslint_disable_check.py (3)

1-28: Improve clarity in docstring line 3.
The docstring suggests analyzing “TypeScript files in the 'src' directory” and also 'setup.ts'. For better discoverability, mention that .tsx files are also included while .test.tsx are excluded.

-"""ESLint Checker Script.
+"""ESLint Disable Checker Script for TypeScript (.ts/.tsx) and setup files.

---

61-61: Rename unused variable to underscore as recommended by static analysis.
The variable dirs is not used. Renaming it to _dirs aligns with the conventional practice of indicating an unused variable.

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

🧰 Tools

🪛 Ruff (0.8.2)

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

Rename unused dirs to _dirs

(B007)

---

91-122: Add a summary upon successful completion.
After printing “ESLint-disable check completed successfully” (line 119), you could summarize how many files were checked or whether any files were skipped for clarity in CI logs.

.github/workflows/compare_translations.py (2)

126-136: Improve raised exception context.
When a JSON decode error occurs (line 135), Python best practices suggest using “raise from e” to retain the original traceback context for debugging.

    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)

---

160-183: Potential optimization by skipping directories with missing default files.
Where the code compiles default_translation (line 164) from default_translations[file], it might be beneficial to skip the loop if the corresponding file does not exist in the other language directory. This could optimize performance and reduce error logs in large projects.

.github/workflows/countline.py (3)

68-79: Raise awareness on other file types.
Currently, invalid_extensions only includes CSS and image formats (line 69). Depending on the project, you might want to exclude other common non-source file extensions (like .svg, .ico, etc.), or rely on a whitelist approach.

---

135-142: Optimize frequent directory scans if performance matters.
_filepaths_in_directories (line 122) does a full recursive walk for each directory. If the codebase is large, this might become expensive. Consider memoizing or controlling repeated calls if relevant.

---

210-294: Clarify line count threshold coverage.
In lines 257–264, the code excludes empty lines and lines starting with # or /. It's worth noting that some comment styles, especially inline or multiline, may not be accounted for. Consider scanning for // or block comment patterns if your codebase includes these.

.coderabbit.yaml (1)

1-1: Overall Review Summary

While the changes in these configuration files are valid and well-structured, they appear to be unrelated to the PR's stated objective of migrating tests from Jest to Vitest. To maintain clear change scope and make reviews more focused:

1. Consider moving these configuration changes to separate PRs:

   • PR 1: Prettier and lint-staged configurations
   • PR 2: CodeRabbit AI integration

2. Update this PR to include only the Jest to Vitest migration changes.

This separation will make the changes easier to review, test, and potentially revert if needed.

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

2-2: Remove trailing spaces from error messages

The following messages have unnecessary trailing spaces:

• talawaApiUnavailable: "तलवा-एपीआई सेवा उपलब्ध नहीं है! "
• notAuthorised: "क्षमा मांगना! "

-  "talawaApiUnavailable": "तलवा-एपीआई सेवा उपलब्ध नहीं है! ",
+  "talawaApiUnavailable": "तलवा-एपीआई सेवा उपलब्ध नहीं है!",
-  "notAuthorised": "क्षमा मांगना! ",
+  "notAuthorised": "क्षमा मांगना!",

Also applies to: 5-5

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

2-2: Fix punctuation in French error message

The talawaApiUnavailable message has both a period and an exclamation mark followed by a space.

-  "talawaApiUnavailable": "Le service Talawa-API n'est pas disponible !. ",
+  "talawaApiUnavailable": "Le service Talawa-API n'est pas disponible !",

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

24-28: Improve markdown formatting

A few markdown formatting issues need to be addressed:

1. The "Potential internship candidates" section should use proper heading syntax
2. The bare URL should be properly formatted as a markdown link

Apply these changes:

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

-https://github.com/PalisadoesFoundation/talawa/issues/359
+[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)

1-44: Fix YAML formatting issues

There are several YAML formatting inconsistencies:

1. Trailing spaces on lines 6, 17, and 20
2. Incorrect indentation in the steps section

Apply these formatting fixes:

-      - '**'  
+      - '**'
-       - name: Checkout repository
+      - name: Checkout repository
-          languages: ${{ matrix.language }}
+           languages: ${{ matrix.language }}

🧰 Tools

🪛 actionlint (1.7.4)

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)

🪛 yamllint (1.35.1)

[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/pull_request_template.md (1)

4-11: Improve visibility of branching strategy warning

The branching strategy is crucial information but could be more visible. Consider using markdown formatting to highlight the warning.

-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: BRANCH SELECTION**
+
+> **WARNING:** ONLY SUBMIT PRS AGAINST OUR `DEVELOP` BRANCH
+> - The default branch is `MAIN` - you must change this before submitting
+> - PRs made against `MAIN` will be closed

.github/workflows/push.yml (2)

54-54: Consider parameterizing test command

The test command could be moved to a script in package.json for better maintainability.

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

Then add to package.json:

{
  "scripts": {
    "test:coverage": "npm run test -- --watchAll=false --coverage"
  }
}

---

59-60: Consider enabling CI failure on coverage errors

The current configuration ignores Codecov upload errors. Consider enabling fail_ci_if_error for better visibility of coverage issues.

-          verbose: true
-          fail_ci_if_error: false
+          verbose: true
+          fail_ci_if_error: true

.github/workflows/README.md (1)

35-35: Fix abbreviation format

Change eg. to e.g. to follow standard abbreviation format.

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

🧰 Tools

🪛 LanguageTool

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

(E_G)

.github/workflows/issue.yml (2)

42-48: Improve code readability in label check

The reduce operation could be simplified using some() for better readability.

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

---

49-55: Consider consolidating duplicate code

The label addition logic is repeated. Consider extracting it into a reusable function.

+const addLabels = async (github, context, labels) => {
+  await github.rest.issues.addLabels({
+    owner: context.repo.owner,
+    repo: context.repo.repo,
+    issue_number: context.issue.number,
+    labels
+  });
+};

-if(labels.data.reduce((a, c)=>a||["dependencies"].includes(c.name), false))
+if(labels.data.some(label => ["dependencies"].includes(label.name)))
-  await github.rest.issues.addLabels({
-    owner: context.repo.owner,
-    repo: context.repo.repo,
-    issue_number: context.issue.number,
-    labels: ["good first issue", "security"]
-  });
+  await addLabels(github, context, ["good first issue", "security"]);

ISSUE_GUIDELINES.md (3)

5-5: Fix grammar in introduction

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

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

🧰 Tools

🪛 LanguageTool

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

(EN_A_VS_AN)

---

29-29: Fix duplicate text in search instruction

The sentence has duplicate text and grammatical errors.

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

---

44-44: Capitalize "Slack" in channel references

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

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

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

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

Also applies to: 53-53, 57-57

🧰 Tools

🪛 LanguageTool

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

(ON_SKYPE)

README.md (1)

53-53: Fix markdown formatting

Remove extra spaces 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)

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

12-77: Clean up YAML formatting

Remove trailing spaces from multiple lines as flagged by yamllint.

Use an editor with whitespace trimming or run yamlfmt to clean up the formatting.

🧰 Tools

🪛 yamllint (1.35.1)

[error] 13-13: trailing spaces

(trailing-spaces)

---

[error] 15-15: trailing spaces

(trailing-spaces)

---

[error] 27-27: trailing spaces

(trailing-spaces)

---

[error] 28-28: trailing spaces

(trailing-spaces)

---

[error] 29-29: trailing spaces

(trailing-spaces)

---

[error] 31-31: trailing spaces

(trailing-spaces)

---

[error] 33-33: trailing spaces

(trailing-spaces)

---

[error] 34-34: trailing spaces

(trailing-spaces)

---

[error] 36-36: trailing spaces

(trailing-spaces)

---

[error] 41-41: trailing spaces

(trailing-spaces)

---

[error] 46-46: trailing spaces

(trailing-spaces)

---

[error] 71-71: trailing spaces

(trailing-spaces)

.eslintrc.json (1)

41-76: Consider gradual adoption of strict TypeScript rules

While strict TypeScript rules are beneficial, enabling all of them at once might be overwhelming. Consider a phased approach to rule adoption.

Consider:

1. Start with essential rules first
2. Add more strict rules in subsequent PRs
3. Document the reasoning for each rule in comments

PR_GUIDELINES.md (1)

49-69: Consider adding commit message guidelines.

While the PR processing guidelines are comprehensive, consider adding a section about commit message conventions to ensure consistency across contributions.

Example addition:

+### Commit Message Guidelines
+
+Commit messages should follow the conventional commits format:
+- feat: A new feature
+- fix: A bug fix
+- docs: Documentation only changes
+- style: Changes that do not affect the meaning of the code
+- refactor: A code change that neither fixes a bug nor adds a feature
+- test: Adding missing tests or correcting existing tests
+- chore: Changes to the build process or auxiliary tools

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

---

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

package.json (1)

154-168: Document Node.js version requirement.

The Node.js version requirement (>=20.x) should be documented in the project's README.md file to ensure contributors are aware of this requirement before setup.

CODE_STYLE.md (2)

1-39: Consider adding version information for tech stack.

While the tech stack list is comprehensive, it would be helpful to specify the versions of each technology being used, especially for major dependencies like React.js and TypeScript.

---

123-150: Consider adding example files for each directory.

While the directory structure is well-explained, it would be helpful to include example files for each directory to better illustrate their purpose.

🧰 Tools

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

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

---

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

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 471f113 and 3d1f1f0.

⛔ Files ignored due to path filters (75)

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

📒 Files selected for processing (82)

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

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

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

💤 Files with no reviewable changes (13)

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

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

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

👮 Files not reviewed due to content moderation or server errors (3)

• public/locales/en/translation.json
• public/locales/sp/translation.json
• .github/ISSUE_TEMPLATE/bug-report.md

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

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)

🪛 LanguageTool

ISSUE_GUIDELINES.md

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

(UNLIKELY_OPENING_PUNCTUATION)

---

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

(IN_ORDER_TO_PREMIUM)

---

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

(EN_A_VS_AN)

---

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

(PLEASE_COMMA)

---

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

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

---

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

(BE_VBP_IN)

---

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

(ON_SKYPE)

PR_GUIDELINES.md

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

(UNLIKELY_OPENING_PUNCTUATION)

---

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

(IN_ORDER_TO_PREMIUM)

---

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

(SPLIT_INFINITIVE)

---

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

(EN_WEAK_ADJECTIVE)

---

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

(SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)

---

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

(FIX_RESOLVE)

---

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

(SOONER_OR_LATER)

---

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

(COMMA_COMPOUND_SENTENCE)

---

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

(MAKE_CHANGES)

README.md

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

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

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)

INSTALLATION.md

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

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)

---

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

(ENGLISH_WORD_REPEAT_RULE)

---

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

(DURING_THAT_TIME_COMMA)

---

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[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: You might be missing the article “the” here.
Context: ...to do this is to right-click and choose appropriate option based on your OS. 3. **For Our O...

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

---

[uncategorized] ~99-~99: A determiner appears to be missing. Consider inserting it.
Context: ...dmin.git ``` ## Install node.js Best way to install and manage node.js is ...

(AI_EN_LECTOR_MISSING_DETERMINER)

---

[uncategorized] ~100-~100: Possible missing preposition found.
Context: ... way to install and manage node.js is making use of node version managers. We recomm...

(AI_EN_LECTOR_MISSING_PREPOSITION)

---

[uncategorized] ~102-~102: The preposition “on” seems more likely in this position than the preposition “in”.
Context: ...steps to install the node.js packages in Windows, Linux and MacOS. 1. For Windo...

(AI_EN_LECTOR_REPLACEMENT_PREPOSITION_IN_ON)

---

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

(MAC_OS)

---

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

(ENGLISH_WORD_REPEAT_RULE)

---

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

(MAC_OS)

---

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

(NOUN_VERB_CONFUSION)

---

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

(COMMA_COMPOUND_SENTENCE)

---

[uncategorized] ~162-~162: You might be missing the article “the” here.
Context: ...the contents of the .env.example into .env file. Use this command: ``` cp .e...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

---

[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] ~238-~238: You might be missing the article “the” here.
Context: ...named REACT_APP_RECAPTCHA_SITE_KEY in .env file. ``` REACT_APP_RECAPTCHA_SIT...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

---

[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: A comma might be missing here.
Context: ... navigate to the running talawa-admin's website you'll land at talawa-admin registratio...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)

---

[uncategorized] ~278-~278: You might be missing the article “the” here.
Context: ...g talawa-admin's website you'll land at talawa-admin registration page. Sign up using ...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

---

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

CODE_OF_CONDUCT.md

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

(ENGLISH_WORD_REPEAT_RULE)

DOCUMENTATION.md

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

(MD_BASEFORM)

---

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

(MARKDOWN_NNP)

---

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

(AI_EN_LECTOR_REPLACEMENT_PREPOSITION)

🪛 Markdownlint (0.37.0)

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)

PR_GUIDELINES.md

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

README.md

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

(MD019, no-multiple-space-atx)

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

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)

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)

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

🪛 yamllint (1.35.1)

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

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 20-20: trailing spaces

(trailing-spaces)

---

[error] 21-21: trailing spaces

(trailing-spaces)

.github/workflows/codeql-codescan.yml

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 17-17: trailing spaces

(trailing-spaces)

---

[error] 20-20: trailing spaces

(trailing-spaces)

---

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

(indentation)

---

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

(indentation)

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

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 17-17: trailing spaces

(trailing-spaces)

---

[error] 18-18: trailing spaces

(trailing-spaces)

---

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

(indentation)

---

[error] 21-21: trailing spaces

(trailing-spaces)

---

[error] 50-50: trailing spaces

(trailing-spaces)

---

[warning] 62-62: too many blank lines

(1 > 0) (empty-lines)

.github/workflows/pull-request.yml

[error] 49-49: trailing spaces

(trailing-spaces)

---

[error] 60-60: trailing spaces

(trailing-spaces)

---

[error] 63-63: trailing spaces

(trailing-spaces)

---

[error] 92-92: trailing spaces

(trailing-spaces)

---

[error] 126-126: trailing spaces

(trailing-spaces)

---

[error] 129-129: trailing spaces

(trailing-spaces)

---

[error] 150-150: trailing spaces

(trailing-spaces)

---

[error] 157-157: trailing spaces

(trailing-spaces)

---

[error] 197-197: trailing spaces

(trailing-spaces)

---

[error] 201-201: trailing spaces

(trailing-spaces)

---

[error] 204-204: trailing spaces

(trailing-spaces)

---

[error] 205-205: trailing spaces

(trailing-spaces)

---

[error] 213-213: trailing spaces

(trailing-spaces)

---

[error] 243-243: trailing spaces

(trailing-spaces)

---

[error] 249-249: trailing spaces

(trailing-spaces)

---

[error] 251-251: trailing spaces

(trailing-spaces)

🪛 actionlint (1.7.4)

.github/workflows/stale.yml

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

(action)

.github/workflows/codeql-codescan.yml

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

(action)

---

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

(action)

---

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

(action)

.github/workflows/issue.yml

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

(action)

.github/workflows/pull-request.yml

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

(expression)

---

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

(shellcheck)

---

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

(expression)

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

DOCUMENTATION.md (3)

1-13: LGTM! Well-structured table of contents.

The header and table of contents are properly formatted and provide clear navigation.

---

14-20: LGTM! Clear documentation locations.

The section effectively communicates the two documentation sources and their purposes.

---

1-32: Verify if this documentation change belongs in this PR.

This documentation file appears unrelated to the stated PR objective of refactoring tests from Jest to Vitest. Please verify if this file should be included in this PR or if it belongs in a separate PR focused on documentation updates.

🧰 Tools

🪛 Markdownlint (0.37.0)

25-25: null
Bare URL used

(MD034, no-bare-urls)

🪛 LanguageTool

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

(MD_BASEFORM)

---

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

(MARKDOWN_NNP)

---

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

(AI_EN_LECTOR_REPLACEMENT_PREPOSITION)

setup.ts (1)

25-39: Ensure dynamic port changes are well-managed.
The script prints the existing custom port and asks the user to confirm, but if they type “No” after seeing an existing port, the earlier logic remains. Consider providing a fallback or clarifying instructions on how to override the current port.

scripts/__mocks__/@dicebear/collection.ts (1)

1-1: Confirm usage of jest.fn() in Vitest migration.
If this project is fully migrating to Vitest, you may want to replace jest.fn() with vi.fn(). Mixing frameworks can cause inconsistent testing behavior.

Would you like help in converting these mocks to Vitest?

jest-preview.config.ts (1)

1-5: Assess continuing need for Jest-specific config.
If the project is transitioning to Vitest, verify whether this Jest configuration remains necessary. Keeping it could cause confusion or misconfiguration for developers.

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

5-11: Great approach testing promise resolution.
You're verifying that generate returns a Promise. Thorough coverage of return type behavior is helpful.

---

13-19: Good coverage of promise result type.
Testing output type as Uint8Array is clear and ensures the correct data structure is returned.

---

21-28: Clear error testing for an empty template.
This is a good pattern for validating contract assumptions. Properly checks that the function throws an error when input is incorrect.

---

30-37: Valid error handling for empty inputs.
The test ensures robust checks for invalid usage.

---

39-46: Comprehensive error coverage.
By testing both empty template and empty inputs, you've ensured completeness in error handling scenarios.

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

1-2: Adherence to TSDoc enforcement is commendable.
Importing fs/promises and path sets a solid foundation for automated checks.

---

38-46: Straightforward TSDoc detection.
Your regex approach is appropriate for a broad check. If in the future you need more precise detection, consider AST-based solutions like a TypeScript parser.

---

48-66: Robust handling of missing TSDoc coverage.
Properly exits with a non-zero code, ensuring CI detects and prevents missing documentation from merging.

jest.config.js (4)

27-35: Good use of moduleNameMapper for mocking dependencies.
This approach simplifies testing by redirecting imports to local mocks.

🧰 Tools

🪛 eslint

[error] 33-33: Delete ·

(prettier/prettier)

---

[error] 34-34: Insert ,

(prettier/prettier)

---

36-47: Extensive file extensions coverage.
Listing a wide range of possible file extensions allows for flexible test file naming.

---

60-65: Coverage thresholds configured.
Ensures minimum coverage enforcement in CI, preventing coverage regressions.

---

66-70: Appropriate ignore patterns for test paths.
Excluding build files, node_modules, and public is standard practice.

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

10-18: Skipping localStorage check with comment is well-structured.
Allows flexibility for test or special cases. Make sure it’s used sparingly and not abused.

🧰 Tools

🪛 eslint

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

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

---

20-37: Efficient retrieval of modified files.
Implementation covers both entire repository and staged changes. Properly handles possible errors.

🧰 Tools

🪛 eslint

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

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

---

43-59: Skipping logic is aligned with prior learnings.
The project does not add TypeScript annotations to .js files, so ignoring type-hinting suggestions is correct.

🧰 Tools

🪛 eslint

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

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

---

61-75: Comprehensive localStorage usage detection.
Identifies multiple localStorage operations and logs the files that need refactoring to custom hooks.

---

82-96: Clear error messaging for localStorage usage.
Exiting with a non-zero status prevents code with undesired storage usage from merging.

🧰 Tools

🪛 eslint

[error] 89-89: Insert ,

(prettier/prettier)

---

[error] 92-92: Insert ,

(prettier/prettier)

.github/workflows/compare_translations.py (1)

147-156: Guard against missing default language directory.
The script assumes en/ exists (line 147). If the directory is missing, the script might crash at line 155. Consider adding a check or a clearer error message.

.github/workflows/countline.py (1)

35-56: Verify the intent of _valid_filename.
The function returns False if .test. or .spec. is found in the filename (lines 46–51). The docstring states “Determine whether filepath has the correct filename,” but it’s not immediately clear if we want to exclude tests or proceed only if no test references exist. Clarifying or inverting the logic might help.

.prettierignore (1)

1-4: These changes appear unrelated to the PR objective

While the changes to .prettierignore are valid, they seem unrelated to the PR's stated objective of migrating tests from Jest to Vitest. Consider moving these changes to a separate PR to maintain clear change scope.

.lintstagedrc.json (1)

1-5: Verify custom script and PR scope

1. The lint-staged configuration looks good, but let's verify the custom script exists:

2. These changes appear unrelated to the PR's objective of migrating tests from Jest to Vitest. Consider moving them to a separate PR focused on git hooks and linting improvements.

.coderabbit.yaml (1)

1-18: Review configuration and scope concerns

The CodeRabbit configuration looks good, but there are two concerns:

1. These changes appear unrelated to the PR's objective of migrating tests from Jest to Vitest. Consider moving them to a separate PR focused on CodeRabbit integration.

2. Security consideration: Enabling auto-review on the main branch (line 16) might need additional review. Consider if this aligns with your security policies for the main branch.

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

1-11: Verify consistency across language files

Let's verify that all error keys are consistent across different language files.

✅ Verification successful

Error message keys are consistent across all language files

The verification shows that all error message keys are perfectly consistent across all language files (en, fr, hi, sp, zh). Each file contains exactly the same set of keys in the same order:

• emailNotRegistered
• errorLoading
• errorOccurredCouldntCreate
• errorSendingMail
• notAuthorised
• notFound
• notFoundMsg
• talawaApiUnavailable
• unknownError

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for consistency of error message keys across language files

# Get all locale files
echo "Checking error message keys across language files..."
for file in public/locales/*/errors.json; do
  echo "Keys in $file:"
  jq 'keys' "$file"
done

Length of output: 1929

public/manifest.json (1)

16-16: Verify the new image path exists

The logo path has been updated to include the 'images/' directory. Let's verify this path exists.

✅ Verification successful

Image path verification successful

The image file exists at the specified path public/images/logo512.png, confirming that the manifest.json correctly references the image location.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check if the image exists in the new path

# Check if the image exists in the new path
if [ -f "public/images/logo512.png" ]; then
    echo "✅ Image exists at public/images/logo512.png"
else
    echo "❌ Image not found at public/images/logo512.png"
    echo "Searching for logo512.png in other directories..."
    fd "logo512.png" public/
fi

Length of output: 135

.github/workflows/README.md (1)

23-25: LGTM! Clear guidelines for PR workflow organization

The separation of workflows based on contributor type (first-time vs. all) is a good practice for maintaining security and providing appropriate checks.

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

.github/workflows/issue.yml (1)

62-65: LGTM! Good first-time contributor experience

The greeting message with links to guidelines is a great way to help new contributors get started.

ISSUE_GUIDELINES.md (1)

1-59: LGTM! Comprehensive issue guidelines

The guidelines provide clear instructions for both new and existing contributors, with good organization and helpful links to resources.

🧰 Tools

🪛 LanguageTool

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

(UNLIKELY_OPENING_PUNCTUATION)

---

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

(IN_ORDER_TO_PREMIUM)

---

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

(EN_A_VS_AN)

---

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

(PLEASE_COMMA)

---

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

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

README.md (1)

24-32: LGTM! Well-structured documentation

The addition of a table of contents and restructured documentation sections improves navigation and readability.

Also applies to: 45-51

.eslintrc.json (1)

1-1: Verify completeness of the PR

The PR objectives mention refactoring test files from Jest to Vitest, but the provided files don't contain any test file changes. Let's verify the test file changes:

PR_GUIDELINES.md (2)

1-18: LGTM! Well-structured introduction and TOC.

The introduction is welcoming and the table of contents is comprehensive and well-organized.

🧰 Tools

🪛 LanguageTool

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

---

19-48: LGTM! Clear guidelines for PR submissions and linting.

The section provides clear instructions for PR submissions and includes proper linting commands that match the project's configuration.

🧰 Tools

🪛 Markdownlint (0.37.0)

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)

🪛 LanguageTool

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

package.json (2)

73-89: LGTM! Well-organized scripts section.

The scripts section provides a comprehensive set of development tools with clear naming conventions.

---

8-70: Review dependency versions for security and compatibility.

1. Version conflicts detected:

• @apollo/client: ^3.11.8 in dependencies but ^3.4.0-beta.19 in resolutions
• @types/react and @types/react-dom: Latest in dependencies but fixed to 17.0.2 in resolutions

2. Security considerations:

• Some dependencies use caret ranges which could introduce breaking changes

CODE_STYLE.md (2)

40-122: LGTM! Clear coding guidelines with helpful examples.

The section provides clear guidelines for component structure and code style, with practical examples demonstrating correct and incorrect usage.

🧰 Tools

🪛 Markdownlint (0.37.0)

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)

---

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)

---

151-253: LGTM! Thorough documentation of imports and Bootstrap customization.

The sections provide clear guidelines for imports and detailed instructions for Bootstrap customization, including file structure and compilation commands.

🧰 Tools

🪛 Markdownlint (0.37.0)

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)

---

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)

---

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)

🪛 LanguageTool

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

3-20: Well-structured table of contents addition

The table of contents is properly implemented with:

• Clear section organization
• Correct markdown linking syntax
• Appropriate indentation for subsections
• Proper TOC markers for maintenance

🧰 Tools

🪛 LanguageTool

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

(ENGLISH_WORD_REPEAT_RULE)

[coderabbitai]

⚠️ Potential issue

Remove duplicate AdvertisementType enum definition.

The AdvertisementType enum is defined twice with identical values.

Remove one of the duplicate enum definitions:

enum AdvertisementType {
  BANNER
  MENU
  POPUP
}

-enum AdvertisementType {
-  BANNER
-  MENU
-  POPUP
-}

Also applies to: 554-558

[coderabbitai]

⚠️ Potential issue

Remove duplicate UserPhone type definition.

The UserPhone type is defined twice with identical fields.

Remove one of the duplicate type definitions:

type UserPhone {
  home: PhoneNumber
  mobile: PhoneNumber
  work: PhoneNumber
}

-type UserPhone {
-  home: PhoneNumber
-  mobile: PhoneNumber
-  work: PhoneNumber
-}

Also applies to: 1407-1411

[coderabbitai]

⚠️ Potential issue

Remove duplicate OrganizationCustomField type definition.

The OrganizationCustomField type is defined twice with identical fields. This can cause schema validation errors.

Remove one of the duplicate definitions:

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

-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

Handle err in fs.readFile callbacks.
The callback receives err but does not handle it. This could lead to silent failures if the file system encounters an issue. Consider checking and throwing/logging the error to aid debugging.

[coderabbitai]

🛠️ Refactor suggestion

Avoid storing absolute paths in modulePaths.
Specifying an absolute path (/Users/prathamesh/Desktop/Open-Source/palisadoes/talawa-admin/src) may cause issues for other contributors. Use relative or <rootDir> references instead to keep the config portable.

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

📝 Committable suggestion

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

Suggested change

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

[coderabbitai]

⚠️ Potential issue

Fix potential command injection vulnerability

The current implementation directly uses GitHub context variables in shell commands, which could lead to command injection. Use array expansion to safely handle file paths.

- CHANGED_FILES: ${{ steps.changed_files.outputs.all_changed_files }}
- npx eslint ${CHANGED_FILES} && python .github/workflows/eslint_disable_check.py
+ CHANGED_FILES: ${{ toJSON(steps.changed_files.outputs.all_changed_files) }}
+ npx eslint $(echo "$CHANGED_FILES" | jq -r '.[]') && python .github/workflows/eslint_disable_check.py

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

🧰 Tools

🪛 actionlint (1.7.4)

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

(expression)

---

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

(shellcheck)

🪛 yamllint (1.35.1)

[error] 60-60: trailing spaces

(trailing-spaces)

[coderabbitai]

⚠️ Potential issue

Update test debugging instructions for Vitest

The jest-preview instructions need to be updated for Vitest's debugging capabilities.

- You can see the output of failing tests in broswer by running `jest-preview` package before running your tests
- npm install
- npm run jest-preview
- npm run test --watchAll=false --coverage
+ You can debug tests in the browser using Vitest's built-in UI:
+ npm run test:vitest --ui

📝 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

	You can see the output of failing tests in broswer by running `jest-preview` package before running your tests
	```
	npm install
	npm run jest-preview
	npm run test --watchAll=false --coverage
	```
	You can debug tests in the browser using Vitest's built-in UI:

🧰 Tools

🪛 Markdownlint (0.37.0)

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

(MD040, fenced-code-language)

[coderabbitai]

⚠️ Potential issue

Update test commands for Vitest

The test commands need to be updated to use Vitest instead of Jest.

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

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

🧰 Tools

🪛 Markdownlint (0.37.0)

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

(MD040, fenced-code-language)

[coderabbitai]

⚠️ Potential issue

Update test command for Vitest

The test command needs to be updated to use Vitest.

- npm run test
+ npm run test:vitest

📝 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

	You can run the tests for `talawa-admin` using this command:
	```
	npm run test
	```
	You can run the tests for `talawa-admin` using this command:

🧰 Tools

🪛 Markdownlint (0.37.0)

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

(MD040, fenced-code-language)

[coderabbitai]

⚠️ Potential issue

Update test debugging instructions for Vitest

The debugging instructions need to be updated to use Vitest's UI.

- You can see the output of failing tests in broswer by running `jest-preview` package before running your tests
- npm run jest-preview
- npm run test
+ You can debug tests using Vitest's built-in UI by running:
+ npm run test:vitest --ui

📝 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

	You can see the output of failing tests in broswer by running `jest-preview` package before running your tests
	```
	npm run jest-preview
	npm run test
	```
	You can debug tests using Vitest's built-in UI by running:

🧰 Tools

🪛 Markdownlint (0.37.0)

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

(MD040, fenced-code-language)

[palisadoes]

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