Test/migrate jest to vitest error handler

[Dhiren-Mhatre]

Refactoring - Migration of test framework from Jest to Vitest

Fixes #2758

All existing tests have been successfully migrated from Jest to Vitest with 100% coverage maintained.

Snapshots/Videos:

Screencast.from.2024-12-24.23-06-10.mp4

If relevant, did I update the documentation?
N/A - This is a test framework migration without changes to functionality.

Summary
This PR migrates the errorHandler test file from Jest to Vitest as part of the ongoing testing framework migration. Changes include:

• Renamed file from errorHandler.test.tsx to errorHandler.spec.tsx
• Updated imports to use Vitest instead of Jest
• Converted Jest mocks to Vitest equivalents
• Maintained 100% test coverage
• Fixed TypeScript and ESLint issues

Does this PR introduce a breaking change?
No

Other information
All tests pass with npm run test:vitest and maintain 100% coverage.

Have i read the contributing guide?
Yes

Summary by CodeRabbit

• New Features

  • Introduced a new configuration file for the YAML language server with various settings.
  • Added a Dependabot configuration to automate dependency updates.
  • Enhanced the bug report and feature request templates with new sections for additional details and internship candidates.
  • Implemented a new script to check for local storage usage across the codebase.

• Bug Fixes

  • Updated error messages and localization files for improved clarity in multiple languages.

• Documentation

  • Expanded the installation guide and contributing guidelines to improve clarity and navigation.
  • Added a new section in the README for community engagement.

• Style

  • Updated various configuration files to improve compatibility and enforce coding standards.

• Tests

  • Enhanced test coverage for the App component, including scenarios for logged-in and logged-out users.

• Chores

  • Removed outdated workflow files and templates to streamline the project structure.

[coderabbitai]

Walkthrough

This pull request introduces comprehensive configuration and workflow updates for the Talawa Admin project. The changes span multiple areas including development tooling, testing infrastructure, localization, and GitHub Actions workflows. Key modifications include adding new configuration files for Vite, Jest, Babel, and CodeRabbit, updating ESLint and Prettier configurations, introducing localization files for multiple languages, and restructuring GitHub workflow definitions to enhance code quality, testing, and contribution processes.

Changes

File/Directory	Change Summary
.coderabbit.yaml	New configuration file for YAML language server settings
.eslintignore, .eslintrc.json	Updated linting configuration and ignore rules
.github/workflows/	Comprehensive updates to GitHub Actions workflows for CI/CD, code quality checks, and automated processes
public/locales/	Added localization files for English, French, Hindi, Spanish, and Chinese
config/	New configuration files for Vite, Babel, and Jest
setup.ts, scripts/	New setup and utility scripts for development and testing

Assessment against linked issues

Objective	Addressed	Explanation
Refactor src/utils/errorHandler.test.tsx from Jest to Vitest [#2758]	❓	Partial migration of test infrastructure, but specific file not directly addressed

Possibly related issues

• Refactor : src/components/CheckIn/TableRow.test.tsx from Jest to Vitest #2496: Refactoring TableRow.test.tsx to Vitest
• Refactor : src/components/ChangeLanguageDropdown/ChangeLanguageDropdown.test.tsx from Jest to Vitest #2493: Refactoring ChangeLanguageDropdown.test.tsx to Vitest
• Refactor : src/components/CheckIn/CheckInWrapper.test.tsx from Jest to Vitest #2495: Refactoring CheckInWrapper.test.tsx to Vitest

Possibly related PRs

• refactored: src/screens/OrgSettings from Jest to Vitest(fixes: #2567) #2625: Refactoring tests to use Vitest
• added vitest to chat.jsx #2649: Adding Vitest to Chat component
• Refactor : src/components/CheckIn/CheckInWrapper.test.tsx from Jest to Vitest #2709: Refactoring CheckInWrapper component tests

Suggested reviewers

• @palisadoes

Poem

🐰 Hop, hop, config deploy!
Workflows dance, tests rejoice
Locales bloom in rainbow's light
CodeRabbit's magic takes its flight
A rabbit's code, precise and bright! 🌈

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

🧹 Nitpick comments (49)

.husky/post-merge (1)

1-4: Ensure robust package installation behavior
This script accurately guards against unnecessary installations by comparing changes in package.json. However, consider gracefully handling scenarios where git diff HEAD^ HEAD might fail (e.g., when there is no previous commit or on shallow clones). Adding a brief comment or fallback logic could make the script more resilient in diverse Git environments.

.husky/pre-commit (1)

4-10: Consider re-enabling lint fixes or removing commented-out step
Here, you format code and run lint-staged, type checks, and table-of-contents updates before committing. The commented-out npm run lint:fix step raises the question: if it’s no longer needed, you could remove it for clarity. If it’s still relevant, consider re-enabling it to fix lint issues automatically during each commit.

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

11-12: Remove extra newline for consistency and style compliance
Static analysis suggests removing unnecessary blank lines. Align with your code style by eliminating trailing whitespace or empty lines that trigger lint errors.

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

- 
});

🧰 Tools

🪛 eslint

[error] 11-12: Delete ··⏎

(prettier/prettier)

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

5-7: Refine TSDoc tags to avoid warnings
The @pdfme reference might not be recognized by your current TSDoc config, causing lint errors. Adjust your documentation configuration or remove the undefined tag to avoid spurious warnings.

🧰 Tools

🪛 eslint

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

(tsdoc/syntax)

---

9-9: Add explicit return type for clarity
Your setup method returns a promise. Consider explicitly specifying its return type (e.g., Promise<void>) to improve type safety and clarity, especially in TypeScript codebases.

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

config/vite.config.ts (1)

9-11: Consider customizing the Vite build output further if needed.
Defining the outDir as 'build' is a standard choice. If additional build-time optimizations are required (e.g., splitting vendor chunks, configuring rollup plugins), you can extend this configuration further.

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

14-21: Consider making content generation deterministic in tests.
Currently, the content bytes are generated randomly. If you need fully reproducible tests, consider seeding or using a stable pseudo-random generator.

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

48-67: Consider expanding TSDoc checks.
In the future, you may enhance the script to validate specific TSDoc tags (e.g., @param, @returns) for critical public functions, ensuring comprehensive documentation.

jest.config.js (2)

13-13: Prettier styling fix needed.

Prettier indicates you may need to insert a newline or adjust the indentation at line 13 to comply with the style guidelines.

  collectCoverageFrom: [
    'src/**/*.{ts,tsx}',
    // ...
    '!vitest.config.ts',],
+ // Adjust indentation or add line break here per Prettier's suggestions

🧰 Tools

🪛 eslint

[error] 13-13: Insert ⏎··

(prettier/prettier)

---

42-43: Trim trailing spaces to satisfy Prettier rules.

Remove any extra spaces at the end of these lines to align with your project's Prettier configuration.

   '^@dicebear/collection$':
-      '<rootDir>/scripts/__mocks__/@dicebear/collection.ts',
-      '\\.svg$': '<rootDir>/scripts/__mocks__/fileMock.js',
+    '<rootDir>/scripts/__mocks__/@dicebear/collection.ts',
+    '\\.svg$': '<rootDir>/scripts/__mocks__/fileMock.js',

🧰 Tools

🪛 eslint

[error] 42-42: Delete ··

(prettier/prettier)

---

[error] 43-43: Delete ··

(prettier/prettier)

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

89-92: Consider Prettier suggestions for trailing commas.

Prettier flags potential missing commas in the console.info arguments. Verify whether your style guide requires trailing commas in multi-line statements.

  console.info(
    '\x1b[34m%s\x1b[0m',
    '\nInfo: Consider using custom hook functions.'
- );
+ ,);
    
  console.info(
    'Please use the getItem, setItem, and removeItem functions provided by the custom hook useLocalStorage.\n'
- );
+ ,);

🧰 Tools

🪛 eslint

[error] 89-89: Insert ,

(prettier/prettier)

---

[error] 92-92: Insert ,

(prettier/prettier)

.github/workflows/talawa_admin_md_mdx_format_adjuster.py (1)

66-96: Consider validating user input for the CLI argument.

If the specified directory does not exist or is invalid, the script will silently traverse zero files. You might want to add validation logic to inform the user of an invalid directory.

 def main():
     parser = argparse.ArgumentParser(description="Make Markdown files MDX compatible.")
     parser.add_argument(
         "--directory",
         type=str,
         required=True,
         help="Directory containing Markdown files to process."
     )
     args = parser.parse_args()

+    if not os.path.isdir(args.directory):
+        print(f"Error: The directory {args.directory} does not exist or is inaccessible.")
+        exit(1)

     # Process each Markdown file...

src/App.test.tsx (1)

86-88: Ensure consistent testing of route transitions.

You are manually assigning window.location to navigate (line 86). Consider using React Router’s mechanics or a library like history for more consistent integration testing, especially when testing route transitions.

.github/workflows/eslint_disable_check.py (1)

61-61: Rename the unused loop variable
The dirs variable is not used in the loop body, which may trigger warnings in certain linters. Consider renaming it to _dirs to clearly indicate that it's unused.

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

setup.ts (1)

25-39: Consider clarifying console logs
When a custom port is already set, the script always prints a confirmation message and defaults shouldSetCustomPort to true. This might be slightly confusing; clarifying in logs or variable names can help.

.github/workflows/compare_translations.py (1)

135-135: Raise exceptions with a cause
When re-raising exceptions in a Python except block, consider using raise ValueError(...) from e to retain the original stack trace.

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)

public/manifest.json (1)

Line range hint 1-1: Review scope observation

These configuration changes appear to be outside the stated PR objective of migrating Jest to Vitest for error handler tests. Consider:

1. Moving these configuration changes to a separate PR
2. Or updating the PR description to include these additional changes

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

2-2: Fix inconsistent punctuation in French messages

Some messages have inconsistent punctuation:

• Line 2: Extra space before period and unnecessary period after exclamation
• Line 4: Double space before {{msg}}
• Line 5: Incomplete message ending with just "Désolé! "

-  "talawaApiUnavailable": "Le service Talawa-API n'est pas disponible !. ",
+  "talawaApiUnavailable": "Le service Talawa-API n'est pas disponible !",
-  "unknownError": "Une erreur inconnue est survenue.  {{msg}}",
+  "unknownError": "Une erreur inconnue est survenue. {{msg}}",
-  "notAuthorised": "Désolé! ",
+  "notAuthorised": "Désolé ! Vous n'êtes pas autorisé.",

Also applies to: 4-4, 5-5

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

14-20: Consider limiting workflow triggers for efficiency

The workflow currently runs on all branches for both pull requests and pushes. Consider limiting this to specific branches (e.g., develop, master) to optimize CI resources.

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

🧰 Tools

🪛 yamllint (1.35.1)

[error] 17-17: trailing spaces

(trailing-spaces)

---

[error] 20-20: trailing spaces

(trailing-spaces)

.github/pull_request_template.md (2)

9-11: Enhance visibility of important branch notice

The critical note about PR targeting could be more visible using GitHub Markdown formatting.

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

---

22-24: Improve issue reference format

The issue reference section could be more clear and automated.

-**Issue Number:**
-
-Fixes #<!--Add related issue number here.-->
+**Related Issue:** #<!--Add issue number-->
+
+**Fixes:** #<!--Add issue number if this PR fixes it-->

DOCUMENTATION.md (3)

24-26: Fix grammar in Docusaurus instructions

There are grammar issues in the Docusaurus launch instructions.

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

🧰 Tools

🪛 Markdownlint (0.37.0)

25-25: null
Bare URL used

(MD034, no-bare-urls)

🪛 LanguageTool

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

(MD_BASEFORM)

---

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

---

26-29: Fix typos and formatting in documentation steps

There are several minor issues in the documentation steps.

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

🧰 Tools

🪛 LanguageTool

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

(MARKDOWN_NNP)

---

31-32: Improve formatting of final warning

The final warning could be more prominent and clear.

-## Other information
-***PLEASE*** do not add markdown files in this repository. Add them to `talawa-docs`!
+## ⚠️ Important Note
+> **DO NOT** add Markdown files to this repository. Add them to the `talawa-docs` repository instead!

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

.github/workflows/stale.yml (1)

31-34: Consider adding more context in stale/close messages

The messages could be more helpful by:

1. Including links to contribution guidelines
2. Mentioning how to reopen if needed
3. Providing contact information for assistance

-        stale-issue-message: 'This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.'
+        stale-issue-message: 'This issue has been inactive for 10 days and will be closed in 180 days without updates. Please check if the develop branch resolves it. See our [contribution guidelines](../CONTRIBUTING.md) for help, or contact maintainers to reopen if needed.'

.github/workflows/push.yml (1)

54-61: Consider fail-fast strategy for code coverage

The current configuration has fail_ci_if_error: false which might hide coverage upload issues. Consider enabling it to catch coverage reporting problems early.

       - name: Present and upload coverage to Codecov as ${{env.CODECOV_UNIQUE_NAME}}
         uses: codecov/codecov-action@v4
         with:
           token: ${{ secrets.CODECOV_TOKEN }}
           verbose: true
-          fail_ci_if_error: false
+          fail_ci_if_error: true
           name: '${{env.CODECOV_UNIQUE_NAME}}'

.github/workflows/README.md (3)

24-24: Fix typo in documentation

There's a word repetition in the sentence.

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

🧰 Tools

🪛 LanguageTool

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

(ENGLISH_WORD_REPEAT_RULE)

---

35-35: Fix abbreviation format

The abbreviation format needs correction.

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

🧰 Tools

🪛 LanguageTool

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

(E_G)

---

41-47: Enhance Python tooling documentation

Consider adding:

1. Minimum version requirements for each tool
2. Links to tool documentation
3. Example commands or configuration files

Would you like me to generate a detailed section about the Python tooling setup and configuration?

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

7-7: Fix trailing space in translation string

The Chinese translation for "noResultsFoundFor" contains a trailing space which might cause inconsistent UI rendering.

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

---

40-40: Remove duplicate description key

The key "desc" is a duplicate of "description", both translating to "描述". Consider using a single key for consistency.

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

Also applies to: 31-32

---

54-67: Inconsistent key naming convention

Some keys use Title Case ("My Organizations", "Dashboard", etc.) while others use camelCase. Maintain consistent key naming across the localization files.

-  "My Organizations": "我的组织",
-  "Dashboard": "仪表板",
+  "myOrganizations": "我的组织",
+  "dashboard": "仪表板",

.github/workflows/issue.yml (1)

42-48: Simplify label condition logic

The current implementation uses reduce for a simple array inclusion check. Consider 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)))
               await github.rest.issues.addLabels({
                 owner: context.repo.owner,
                 repo: context.repo.repo,
                 issue_number: context.issue.number,
                 labels: ["good first issue", "security"]
               });
-            else if(labels.data.reduce((a, c)=>a||["security", "ui/ux"].includes(c.name), false))
+            else if(labels.data.some(label => ["security", "ui/ux"].includes(label.name)))

Also applies to: 49-55

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

40-40: Remove duplicate description key

Similar to the Chinese localization file, the key "desc" is a duplicate of "description". Use a single key for consistency.

  "description": "Description",
-  "desc": "Description",

Also applies to: 31-31

---

54-67: Standardize key naming convention

Some keys use Title Case while others use camelCase. Maintain a consistent naming convention across all localization files.

-  "My Organizations": "My Organizations",
-  "Dashboard": "Dashboard",
+  "myOrganizations": "My Organizations",
+  "dashboard": "Dashboard",

---

79-79: Standardize success message capitalization

Success messages have inconsistent capitalization of "Successfully". Standardize the capitalization across all messages.

-  "addedSuccessfully": "{{item}} added Successfully",
-  "updatedSuccessfully": "{{item}} updated Successfully",
-  "removedSuccessfully": "{{item}} removed Successfully",
+  "addedSuccessfully": "{{item}} Added successfully",
+  "updatedSuccessfully": "{{item}} Updated successfully",
+  "removedSuccessfully": "{{item}} Removed successfully",

Also applies to: 82-84

ISSUE_GUIDELINES.md (2)

29-29: Fix grammatical error in duplicate issue check instruction

There's a grammatical error in this line that makes it hard to understand.

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

---

44-44: Capitalize "Slack" in channel references

The word "slack" should be capitalized as it's a proper noun.

-   2. Ask our contributors to assign it to you in `#talawa` slack channel.
+   2. Ask our contributors to assign it to you in `#talawa` Slack channel.
-1. Join our `#talawa-github` slack channel for automatic issue and pull request updates.
+1. Join our `#talawa-github` Slack channel for automatic issue and pull request updates.
-1. Discuss issues in our various slack channels when necessary
+1. Discuss issues in our various Slack channels when necessary

Also applies to: 53-53, 57-57

🧰 Tools

🪛 LanguageTool

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

(ON_SKYPE)

README.md (1)

53-53: Fix markdown formatting

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

PR_GUIDELINES.md (2)

31-34: Add language identifier to code blocks

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

Update the code blocks:

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

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

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

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

(MD040, fenced-code-language)

</details>

</details>

---

`46-47`: **Enhance test requirements clarity**

The testing section could be more specific about the coverage requirements and testing frameworks.

Consider adding:
- Required test coverage percentage
- Specific mention of Vitest as the testing framework
- Examples of good test cases

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

<details>
<summary>🪛 LanguageTool</summary>

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

</details>

</details>

</blockquote></details>
<details>
<summary>CODE_STYLE.md (2)</summary><blockquote>

`58-69`: **Add language identifiers to code blocks.**

Code blocks should specify their language for proper syntax highlighting. Add identifiers like `jsx`, `tsx`, or `html` as appropriate.



Also applies to: 75-89, 95-115

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

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

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)

</details>

</details>

---

`127-138`: **Maintain consistent path formatting.**

Use consistent formatting for paths. Consider using backticks consistently for all directory and file names.

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

<details>
<summary>🪛 LanguageTool</summary>

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

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

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)

</details>

</details>

</blockquote></details>
<details>
<summary>CONTRIBUTING.md (1)</summary><blockquote>

`158-161`: **Fix empty links in codecov section.**

The following links are empty and should be properly formatted:
- Line 158: `[![Code-cov-token.jpg](/public/images/codecov/Code-cov-token.jpg)]()`
- Line 159: `[![addd-your-key.jpg](/public/images/codecov/addd-your-key.jpg)]()`
- Line 161: `[![results.jpg](/public/images/codecov/results.jpg)]()`

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

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

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)

</details>

</details>

</blockquote></details>
<details>
<summary>.github/ISSUE_TEMPLATE/feature-request.md (2)</summary><blockquote>

`24-25`: **Use proper markdown heading syntax.**

Convert the bold text to a proper markdown heading for better document structure and navigation.

```diff
-**Potential internship candidates**
+## Potential internship candidates

🧰 Tools

🪛 Markdownlint (0.37.0)

25-25: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

27-28: Use proper markdown link syntax.

Convert the bare URL to a proper markdown link with descriptive text.

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

🧰 Tools

🪛 Markdownlint (0.37.0)

28-28: null
Bare URL used

(MD034, no-bare-urls)

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

214-221: Consider adding Vitest coverage thresholds.

While uploading coverage to Codecov is good, consider adding Vitest-specific coverage thresholds in the configuration.

Add a vitest.config.ts file with coverage thresholds:

import { defineConfig } from 'vitest/config'

export default defineConfig({
  test: {
    coverage: {
      thresholds: {
        lines: 95,
        functions: 95,
        branches: 95,
        statements: 95
      }
    }
  }
})

INSTALLATION.md (1)

142-144: Add language specifiers to code blocks.

Several code blocks are missing language specifiers, which affects syntax highlighting.

-```
+```bash
 npm install

- +bash
npm run setup

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

Also applies to: 154-156, 164-166

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

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

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

(MD040, fenced-code-language)

</details>

</details>

</blockquote></details>
<details>
<summary>.github/ISSUE_TEMPLATE/bug-report.md (1)</summary><blockquote>

`33-36`: **Improve markdown formatting**

The section formatting can be improved for better readability and compliance with markdown best practices:
1. Use proper heading syntax
2. Format the URL as a markdown link

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

🧰 Tools

🪛 Markdownlint (0.37.0)

36-36: null
Bare URL used

(MD034, no-bare-urls)

---

33-33: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b465221 and 14a6b8d.

⛔ 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)
• .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)
• src/App.test.tsx (1 hunks)

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

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

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

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

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

🧰 Additional context used

📓 Learnings (1)

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

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

🪛 eslint

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

jest.config.js

[error] 13-13: Insert ⏎··

(prettier/prettier)

---

[error] 42-42: Delete ··

(prettier/prettier)

---

[error] 43-43: Delete ··

(prettier/prettier)

scripts/githooks/update-toc.js

[error] 11-12: Delete ··⏎

(prettier/prettier)

scripts/githooks/check-localstorage-usage.js

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

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

---

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

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

---

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

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

---

[error] 89-89: Insert ,

(prettier/prettier)

---

[error] 92-92: Insert ,

(prettier/prettier)

🪛 LanguageTool

CODE_OF_CONDUCT.md

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

(ENGLISH_WORD_REPEAT_RULE)

ISSUE_GUIDELINES.md

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

(UNLIKELY_OPENING_PUNCTUATION)

---

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

(IN_ORDER_TO_PREMIUM)

---

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

(EN_A_VS_AN)

---

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

(PLEASE_COMMA)

---

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

(FIX_RESOLVE)

---

[uncategorized] ~32-~32: Possible missing preposition found.
Context: ...lawa-admin/issues/new/choose) button 1. Use the templates to create a standardized ...

(AI_HYDRA_LEO_MISSING_TO)

---

[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

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

DOCUMENTATION.md

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

(MD_BASEFORM)

---

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

(MARKDOWN_NNP)

---

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

(AI_EN_LECTOR_REPLACEMENT_PREPOSITION)

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

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)

.github/workflows/README.md

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

(AI_HYDRA_LEO_MISSING_COMMA)

---

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

(ENGLISH_WORD_REPEAT_RULE)

---

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

(E_G)

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)

INSTALLATION.md

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

(ENGLISH_WORD_REPEAT_RULE)

---

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

(DURING_THAT_TIME_COMMA)

---

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

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

(NOUN_VERB_CONFUSION)

---

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

(MAC_OS)

---

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

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

(MAC_OS)

---

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

(ENGLISH_WORD_REPEAT_RULE)

---

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

(MAC_OS)

---

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

(NOUN_VERB_CONFUSION)

---

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

(COMMA_COMPOUND_SENTENCE)

---

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

(NOUN_VERB_CONFUSION)

---

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

(NOUN_VERB_CONFUSION)

---

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

(MD_PRP_QUESTION_MARK)

---

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

(BY_DEFAULT_COMMA)

---

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

(PRP_MD_NN)

🪛 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/issue.yml

[error] 6-6: trailing spaces

(trailing-spaces)

---

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

(indentation)

---

[warning] 66-66: too many blank lines

(1 > 0) (empty-lines)

.github/workflows/codeql-codescan.yml

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 17-17: trailing spaces

(trailing-spaces)

---

[error] 20-20: trailing spaces

(trailing-spaces)

---

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

(indentation)

---

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

(indentation)

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

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

(action)

.github/workflows/codeql-codescan.yml

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

(action)

---

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

(action)

---

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

(action)

.github/workflows/pull-request.yml

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

(expression)

---

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

(shellcheck)

---

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

(expression)

🪛 Markdownlint (0.37.0)

README.md

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

(MD019, no-multiple-space-atx)

DOCUMENTATION.md

25-25: null
Bare URL used

(MD034, no-bare-urls)

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)

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)

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)

.github/ISSUE_TEMPLATE/feature-request.md

28-28: null
Bare URL used

(MD034, no-bare-urls)

---

25-25: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

🪛 Ruff (0.8.2)

.github/workflows/eslint_disable_check.py

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

Rename unused dirs to _dirs

(B007)

.github/workflows/compare_translations.py

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

(B904)

🔇 Additional comments (43)

.prettierignore (2)

2-2: LGTM! Ignoring GitHub-specific directory.

The addition of .github to the ignore list is appropriate as GitHub-specific files often follow their own formatting conventions.

---

3-4: LGTM! Well-documented ignore entry for tagTemplate.ts.

The ignore entry is properly documented with a clear explanation of why the file should be excluded from formatting. The coordination with .eslintignore shows a consistent approach to handling this special case.

config/vite.config.ts (3)

1-5: Good use of Vite plugins for a modern React setup.
These imports demonstrate a forward-thinking approach by leveraging React support, TypeScript path resolution, SVGR for SVGs, and environment variable handling. Great job ensuring all relevant Vite plugins are included upfront.

---

13-23: Validate plugin ordering and environment variable usage.
The plugin sequence is important in Vite. Ensure that the environment variables exposed by EnvironmentPlugin('all') are effectively used and that svgrPlugin is placed at a position that suits your React workflow.

---

24-29: Port and auto-open are well-defined.
Opening the browser at port 4321 is consistent. Make sure your team is aware of the custom port, or you can keep a .env or config file for easy port overrides.

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

3-9: Straightforward parameter structure.
Defining template and inputs inline with async/await usage is clear and consistent. Good job.

---

10-13: Excellent validation for empty template or inputs.
Throwing an error early avoids potential downstream issues.

---

15-21: Potential performance optimization for large inputs.
For extremely large schemas or inputs, generating a huge array could be costly. Consider limiting or chunking content generation if performance becomes critical.

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

5-11: Promising coverage of asynchronous behavior.
Verifying that generate returns a Promise is a crucial first step in asynchronous test coverage.

---

13-19: Testing the resolved data type is beneficial.
Ensuring the resolved value is indeed a Uint8Array confirms that your mock matches the intended PDF generation contract.

---

21-28: Thorough error handling checks.
These tests confirm that errors are thrown appropriately when the template is empty. Ensuring coverage of negative paths is commendable.

---

30-37: Comprehensive tests for empty inputs.
This ensures consistent error handling for missing data.

---

39-46: Validating both empty template & inputs is crucial.
Combining both negative scenarios further strengthens your confidence in the error logic.

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

1-12: Clear specification of skip list.
Defining a dedicated filesToSkip array ensures that critical system files are exempt without scattering conditions throughout the code.

---

13-35: Recursively locating .tsx files is well-structured.
The approach of skipping tests and known excluded files is sensible. Error handling is also in place for directory reading issues.

---

37-46: Regular expression check is straightforward.
Confirming that a file contains at least one /** ... */ TSDoc structure is simple yet effective.

---

60-65: Meaningful exit codes for CI.
Exiting with code 1 upon incomplete TSDoc coverage is a clear signal for CI to mark the build as failed, ensuring team awareness.

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

10-10: Ignore type annotation warnings in .js files.

ESLint suggests adding return types in lines 10, 20, and 43, but as per the retrieved learnings, type annotations are disallowed in .js files within this project. It is safe to dismiss these warnings.

Also applies to: 20-20, 43-43

🧰 Tools

🪛 eslint

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

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

.github/workflows/talawa_admin_md_mdx_format_adjuster.py (1)

19-44: Implementation is clean and meets MDX requirements.

The escape_mdx_characters function properly replaces unescaped MDX special characters without double escaping. This approach appears robust and transparent.

src/App.test.tsx (1)

71-71: Confirm array storage strategy.

You’re storing an array of objects in localStorage (line 71). Ensure useLocalStorage correctly stringifies and parses arrays to avoid potential serialization/deserialization errors.

setup.ts (4)

10-21: Overall Implementation Looks Good
The setup procedure and environment file checks appear to be well-structured. The logic for creating or validating .env is clearly defined, which ensures a smooth setup process.

---

68-97: Graceful handling of repeated prompts
The loop for prompting until a successful connection is established is beneficial. Great job ensuring that the user must enter a valid Talawa API URL.

---

106-160: ReCAPTCHA site key validation
The reCAPTCHA handling logic is well-structured, prompting users to confirm usage and specifying a site key as needed. The step-by-step approach is easy to follow.

---

163-178: Logging errors
You correctly update the .env file to enable error logging. Providing optional logs is good practice for debugging.

.github/workflows/compare_translations.py (1)

160-182: Comprehensive translation checks
The logic effectively flags missing or extra keys. Returning an error exit code remains consistent with typical CI flows—well done.

.github/workflows/countline.py (1)

197-294: Solid approach to line counting
The script thoroughly checks for lines of code while ignoring comments and blank lines, and it provides a clear exit status if a threshold is exceeded. This is a well-designed approach for enforcing short, maintainable files.

.lintstagedrc.json (1)

4-4: Verify the existence of the custom script

Please ensure that the referenced script scripts/githooks/check-localstorage-usage.js exists in the repository.

✅ Verification successful

Custom script exists at the specified path

The script scripts/githooks/check-localstorage-usage.js exists in the repository at the expected location, confirming that the lint-staged configuration is valid.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if the custom script exists
if ! fd -t f "check-localstorage-usage.js" scripts/githooks/; then
  echo "Warning: Custom script not found in expected location"
fi

Length of output: 100

.coderabbit.yaml (1)

11-16: Consider impact on test migration workflow

The auto-review configuration might need adjustment during the Jest to Vitest migration:

1. Ensure that the auto-review process is compatible with Vitest test files
2. Verify that both 'develop' and 'main' branches have the necessary Vitest configurations

✅ Verification successful

Let me gather more information about the test configuration files and their usage in the codebase.

---

Auto-review configuration is appropriate for the test migration

The codebase shows a clear transition from Jest to Vitest with both configurations present:

• jest.config.js exists for legacy tests
• vitest.config.ts is already set up for the migration
• Test files are consistently using .test.ts or .spec.ts extensions which are compatible with both Jest and Vitest
• Required dependencies are properly configured with both jest and vitest in devDependencies

The current auto-review configuration in .coderabbit.yaml is appropriate as:

1. It will work with both Jest and Vitest test files due to their compatible naming patterns
2. The presence of both test configurations ensures the review process can handle the transition period

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for Jest/Vitest configurations in base branches
for branch in develop main; do
  echo "Checking $branch branch for test configurations..."
  git ls-tree -r --name-only $branch | rg -e "vitest.config" -e "jest.config"
done

Length of output: 472

---

Script:

#!/bin/bash
# Check for test configuration files and test files
echo "Searching for test configuration files..."
fd -e js -e ts -e json -E "node_modules" . | rg -i "(jest|vitest).config"

echo -e "\nSearching for test files..."
fd -e test.js -e test.ts -e spec.js -e spec.ts -E "node_modules" .

echo -e "\nChecking package.json for test-related dependencies..."
cat package.json | jq '.dependencies,.devDependencies' 2>/dev/null || echo "No package.json found"

Length of output: 4961

.gitignore (2)

13-14: LGTM: Coverage directory exclusions added

These entries are necessary for the Jest to Vitest migration as both testing frameworks generate coverage reports in the coverage/ directory.

---

3-5: Consider using a single package manager

Having multiple package manager lock files (.lock, .yaml) might lead to dependency resolution conflicts. Consider standardizing on a single package manager for consistency.

Run this script to check for multiple lock files in the repository:

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

1-11: Verify error message usage in migrated tests

Since this PR involves migrating test files, we should verify that these error messages are correctly used in the migrated tests.

✅ Verification successful

Error messages are actively used across the codebase including test files

The verification shows that the error messages are actively used across multiple components and test files:

• Found in test files: src/utils/errorHandler.spec.tsx
• Used in error handling utilities: src/utils/errorHandler.tsx
• Actively used across many components and screens including:
  • User management screens
  • Organization dashboard
  • Event management
  • Campaign and pledge screens
  • Not found pages

The error messages in the French locale file are correctly integrated with the i18n system as evidenced by widespread usage of translation hooks (useTranslation) across the codebase.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for error message keys in test files
echo "Searching for error message usage in test files..."
rg -l "errorOccurredCouldntCreate|errorLoading|notFound|unknownError" --type ts --type tsx

Length of output: 231

---

Script:

#!/bin/bash
# Search for error message keys in test files with correct file extensions
echo "Searching for error message usage in test files..."
rg -l "errorOccurredCouldntCreate|errorLoading|notFound|unknownError" "*.test.ts" "*.test.tsx" "*.spec.ts" "*.spec.tsx"

# Also search in any typescript files to see general usage
echo -e "\nSearching in all typescript files..."
rg -l "errorOccurredCouldntCreate|errorLoading|notFound|unknownError" "*.ts" "*.tsx"

Length of output: 701

---

Script:

#!/bin/bash
# Search for error message keys using fd to find test files first
echo "Searching for error message usage in test files..."
fd -e ts -e tsx | xargs rg -l "errorOccurredCouldntCreate|errorLoading|notFound|unknownError"

# Also search for any i18n/translation usage patterns
echo -e "\nSearching for translation usage patterns..."
rg -l "useTranslation|t\(['\"]errors" 

Length of output: 8361

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

9-10: LGTM: Properly translated messages

These messages are correctly translated to Spanish and maintain proper placeholder usage.

.github/workflows/stale.yml (1)

37-43: Review stale configuration timings

The current configuration:

• 10 days before marking as stale
• 180 days before closing
• 30 operations per run

Consider if these timings align with the project's activity levels and maintenance goals.

✅ Verification successful

Let me analyze the data from the GitHub API to evaluate if the stale configuration timings are appropriate.

Let me also check if there are any existing discussions or documentation about the stale settings:

---

Current stale configuration aligns well with repository activity patterns

Based on the analysis of recent issues and pull requests:

1. The 10-day stale marking is appropriate because:

   • Most active PRs are reviewed and merged within 1-7 days
   • Issues typically receive updates/responses within a week
   • Provides sufficient time for contributors to respond while keeping the repository tidy

2. The 180-day close timing is reasonable because:

   • Long-term issues and PRs that need extensive work or discussion have adequate time
   • The stale warning messages clearly explain the timeline and required actions
   • remove-stale-when-updated: true ensures active discussions aren't closed
   • Contributors can request more time by responding to stale notifications

3. The 30 operations per run is suitable for the current activity level:

   • Repository shows consistent but manageable activity
   • Prevents overwhelming GitHub API limits while maintaining housekeeping

The configuration strikes a good balance between maintaining repository cleanliness and accommodating various contribution patterns.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check average issue/PR resolution time to validate stale timings
gh api graphql -f query='
{
  repository(owner: "PalisadoesFoundation", name: "talawa-admin") {
    issues(last: 100, states: CLOSED) {
      nodes {
        closedAt
        createdAt
      }
    }
  }
}'

Length of output: 7354

---

Script:

#!/bin/bash
# Get pull request resolution times
gh api graphql -f query='
{
  repository(owner: "PalisadoesFoundation", name: "talawa-admin") {
    pullRequests(last: 100, states: CLOSED) {
      nodes {
        closedAt
        createdAt
      }
    }
  }
}'

Length of output: 7366

---

Script:

#!/bin/bash
# Search for any discussions about stale settings
rg -i "stale|inactive|close" .github/

Length of output: 2131

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

1-18: Several entries need Spanish translations

The following entries are still in English and need to be translated to Spanish:

• "firstName": "First Name"
• "lastName": "Last Name"
• "searchByName": "Search By Name"
• "loading": "Loading..."
• "endOfResults": "End of results"
• "edit": "Edit"
• "admins": "Admins"
• "members": "Members"

Would you like me to help translate these entries to Spanish? I can generate the translations or create a GitHub issue to track this task.

---

19-53: Additional entries requiring Spanish translations

More entries that need translation to Spanish:

• "users": "Users"
• "requests": "Requests"
• "description": "Description"
• "email": "Email"
• "name": "Name"
• "desc": "Description"

README.md (1)

10-10: Verify test coverage reporting with Vitest

The Codecov badge has been added, but since we're migrating from Jest to Vitest, ensure that the coverage reporting is properly configured for Vitest.

✅ Verification successful

Test coverage reporting is properly configured for Vitest

The coverage configuration for Vitest is correctly set up:

• Coverage is enabled with Istanbul provider in vitest.config.ts
• Reports are configured to be generated in ./coverage/vitest directory
• Multiple report formats are configured: text, HTML, text-summary, and lcov (which is compatible with Codecov)
• Appropriate test script test:vitest:coverage is defined in package.json
• Required dependency @vitest/coverage-istanbul is installed

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if vitest coverage configuration exists
rg -l "coverage" -g "vite.config.*"

Length of output: 35

---

Script:

#!/bin/bash
# Let's check for coverage configuration in package.json and vitest configuration files
echo "=== Checking package.json for coverage configuration ==="
rg "coverage" package.json

echo -e "\n=== Checking for vitest config files ==="
fd "vitest.config" 

echo -e "\n=== Checking for coverage in any test configuration files ==="
fd -e js -e ts -e json | rg -i "test.*config|vitest"

echo -e "\n=== Checking for coverage reporter dependencies ==="
rg "@vitest/coverage" package.json

Length of output: 887

---

Script:

#!/bin/bash
# Let's check the vitest configuration file for coverage settings
echo "=== Checking vitest.config.ts for coverage configuration ==="
cat vitest.config.ts

echo -e "\n=== Checking for recent coverage reports ==="
fd "coverage"

Length of output: 1118

.eslintrc.json (1)

Line range hint 1-150: Install ESLint Vitest plugin

To support the ESLint configuration changes, we need to install the Vitest ESLint plugin.

CODE_OF_CONDUCT.md (2)

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

The addition of a table of contents improves document navigation.

🧰 Tools

🪛 LanguageTool

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

(ENGLISH_WORD_REPEAT_RULE)

---

Line range hint 147-150: Remove unused Jest dependencies

Since we're migrating to Vitest, these Jest-related dependencies should be removed.

Let's verify if there are any remaining Jest configurations or test files:

Remove these dependencies after verifying that all test files have been migrated to Vitest:

-    "jest": "^27.4.5",
-    "jest-localstorage-mock": "^2.4.19",
-    "jest-location-mock": "^2.0.0",
-    "jest-preview": "^0.3.1",

🧰 Tools

🪛 LanguageTool

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

(ENGLISH_WORD_REPEAT_RULE)

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

2-6: LGTM! Metadata updates improve consistency.

The capitalization and label updates align with the project's standardization efforts across issue templates.

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

1-1483: Chinese translations look good!

The Chinese translations are complete, accurate, and maintain consistency with the English source. All placeholders and variables are properly preserved.

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

1-1483: French translations look good!

The French translations are complete, accurate, and maintain consistency with the English source. All placeholders and variables are properly preserved.

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

2-6: LGTM! Metadata changes improve consistency

The updates to the template metadata follow GitHub conventions and maintain consistent capitalization.

[coderabbitai]

⚠️ Potential issue

Avoid hardcoding absolute paths in modulePaths.

Storing a user-specific absolute path (/Users/prathamesh/Desktop/Open-Source/palisadoes/talawa-admin/src) could lead to portability issues for other team members and CI pipelines. Consider using relative paths or removing this entry if not strictly required.

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

📝 Committable suggestion

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

Suggested change

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

[coderabbitai]

⚠️ Potential issue

Incorrect icon size specification

The size "16x16" seems incorrect for a file named "logo192.png". The file name suggests it should be "192x192".

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

📝 Committable suggestion

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

Suggested change

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

[coderabbitai]

💡 Codebase verification

Image path inconsistency and file mismatch detected

The verification revealed two issues:

• The same image name exists in both public/ and public/images/ directories
• The files are different between the two locations, which could lead to unexpected behavior

Recommendations:

• Decide on a single location for the image (preferably public/images/ as per manifest)
• Ensure the correct version of the image is kept
• Remove the duplicate to avoid confusion
• Update any other references to use the correct path (though no direct references were found in the codebase)

🔗 Analysis chain

Verify image path and existence

The logo path has been updated to include the 'images/' directory. Please ensure this directory exists and contains the required image.

---

Image exists in both locations - potential duplication

The verification shows that logo512.png exists in both locations:

• public/images/logo512.png (new location referenced in manifest)
• public/ (old location)

This could lead to confusion and unnecessary duplication. Let's verify if there are any other references to this image that might still be using the old path.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if the image exists in the new location
if ! fd -t f "logo512.png" public/images/; then
  echo "Warning: logo512.png not found in public/images/"
fi

# Check if the old location still contains the file
if fd -t f "logo512.png" public/ -d 1; then
  echo "Note: logo512.png still exists in public/ directory"
fi

Length of output: 210

---

Script:

#!/bin/bash
# Search for references to logo512.png in the codebase
rg "logo512.png" --type-not json

# Check if these are identical files
cmp public/logo512.png public/images/logo512.png 2>/dev/null || echo "Files are different"

Length of output: 132

[coderabbitai]

⚠️ Potential issue

Critical: Messages need Spanish translation

Most messages are still in English instead of Spanish. Only the last two messages (lines 9-10) are in Spanish. Please translate all messages to Spanish for consistency.

Example translations for reference:

-  "talawaApiUnavailable": "Talawa-API service is unavailable!. Is it running? Check your network connectivity too.",
+  "talawaApiUnavailable": "¡El servicio Talawa-API no está disponible! ¿Está ejecutándose? Verifique también su conectividad de red.",
-  "notFound": "Not found",
+  "notFound": "No encontrado",
-  "unknownError": "An unknown error occurred. Please try again later. {{msg}}",
+  "unknownError": "Ocurrió un error desconocido. Por favor, inténtelo de nuevo más tarde. {{msg}}",

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

[coderabbitai]

⚠️ Potential issue

Update CodeQL action versions

The CodeQL action versions are outdated. Update to the latest versions to ensure security and compatibility.

-         uses: github/codeql-action/init@v2
+         uses: github/codeql-action/init@v3
-         uses: github/codeql-action/autobuild@v2
+         uses: github/codeql-action/autobuild@v3
-         uses: github/codeql-action/analyze@v2
+         uses: github/codeql-action/analyze@v3

Also applies to: 41-41, 44-44

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

🪛 yamllint (1.35.1)

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

(indentation)

[coderabbitai]

⚠️ Potential issue

Remove duplicate AdvertisementType enum definition.

The AdvertisementType enum is defined twice (see lines 67-71).

Remove the duplicate definition (lines 554-558).

[coderabbitai]

⚠️ Potential issue

Remove duplicate enum definitions.

The following enums are defined twice:

• EducationGrade (see lines 244-261)
• EmploymentStatus (see lines 265-269)
• Gender (see lines 438-442)
• MaritalStatus (see lines 491-498)

Remove these duplicate definitions.

Also applies to: 1242-1246, 1248-1252, 1254-1261

[coderabbitai]

⚠️ Potential issue

Fix inconsistent translations in orgList section

Several translations are just repeating the key name instead of providing proper English text:

-    "name": "name",
-    "email": "email",
-    "description": "description",
-    "location": "location",
-    "address": "address",
-    "displayImage": "displayImage",
+    "name": "Name",
+    "email": "Email",
+    "description": "Description", 
+    "location": "Location",
+    "address": "Address",
+    "displayImage": "Display Image",

📝 Committable suggestion

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

Suggested change

	"name": "name",
	"email": "email",
	"searchByName": "searchByName",
	"description": "description",
	"location": "location",
	"address": "address",
	"displayImage": "displayImage",
	"name": "Name",
	"email": "Email",
	"searchByName": "searchByName",
	"description": "Description",
	"location": "Location",
	"address": "Address",
	"displayImage": "Display Image",

[coderabbitai]

🛠️ Refactor suggestion

Fix inconsistent casing in keys

The casing of keys is inconsistent:

-    "Title": "Title",
-    "Text": "Text",
+    "title": "Title",
+    "text": "Text",

📝 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

	"Title": "Title",
	"Text": "Text",
	"title": "Title",
	"text": "Text",

[coderabbitai]

⚠️ Potential issue

Fix incorrect template text

The "Additional details" section incorrectly references a feature request instead of a bug report.

-Add any other context or screenshots about the feature request here.
+Add any other context or screenshots about the bug report here.

📝 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

	Add any other context or screenshots about the feature request here.
	Add any other context or screenshots about the bug report here.

[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