Upcomingevents jest to vitest

[abbi4code]

What kind of change does this PR introduce?
This PR migrates the test cases in src/screens/UserPortal/Volunteer/UpcomingEvents from Jest to Vitest, ensuring compatibility with Vitest .

✅ Replace Jest-specific functions and mocks with Vitest equivalents
✅ Ensure all tests in src/screens/UserPortal/Volunteer/UpcomingEvents pass after migration using npm run test:vitest
✅ Maintain the test coverage for the file as 100% after migration
✅ Upload a video or photo for this specific file coverage is 100% in the PR description

Feature/Refactoring UpcomingEvents Component

Issue Number:

Fixes #2582

Did you add tests for your changes?
Yes

Snapshots/Videos:

Summary by CodeRabbit

Release Notes

• New Features

  • Introduced a new configuration file for YAML language server settings.
  • Added a template for environment variable configuration.
  • Implemented a new README for GitHub workflows, outlining guidelines for contributors.
  • Added localization support for multiple languages including English, French, Hindi, Spanish, and Chinese.

• Documentation

  • Enhanced CONTRIBUTING.md and added CODE_STYLE.md for clearer guidelines.
  • Created DOCUMENTATION.md to guide users on accessing project documentation.

• Bug Fixes

  • Updated error handling in various scripts and configurations to improve stability.

• Improvements

  • Enhanced linting and testing configurations for better code quality.
  • Streamlined GitHub Actions workflows for pull requests and issues.

• Refactor

  • Restructured various files for improved organization and clarity.

[coderabbitai]

Walkthrough

The pull request introduces several configuration files and updates across the project, including a new .coderabbit.yaml for YAML language server settings, a .env.example for environment variables, and various workflow files for GitHub Actions. It also includes updates to linting configurations, documentation files, and localization support in multiple languages. Additionally, several Jest tests are refactored to Vitest, enhancing the testing framework's integration.

Changes

File Path	Change Summary
.coderabbit.yaml	New configuration file specifying settings for a YAML language server, including schema reference and various parameters.
.env.example	New template file for environment variables, including PORT, REACT_APP_TALAWA_URL, and others for configuration.
.eslintignore	Added entries to exclude specific files from linting.
.eslintrc.json	Updated environment settings and rules for linting, including new TypeScript-specific rules.
.github/ISSUE_TEMPLATE/bug-report.md	Updated metadata and added new sections for additional details and internship candidates.
.github/ISSUE_TEMPLATE/feature-request.md	Similar updates as the bug report template for consistency and clarity.
.github/dependabot.yaml	New configuration file for Dependabot to automate dependency updates.
.github/pull_request_template.md	Modified to include new sections for branching strategy and confirming tests.
.github/workflows/README.md	New README file outlining guidelines for managing workflow files.
.github/workflows/auto-label.json5	New configuration file defining label synonyms and default labels for workflows.
.github/workflows/check-tsdoc.js	New script to validate TSDoc comments in .tsx files.
.github/workflows/ci.yml	Deleted CI workflow file that defined automated testing processes.
.github/workflows/codeql-analysis.yml	Deleted CodeQL analysis workflow file.
.github/workflows/codeql-codescan.yml	New workflow for automating code analysis using CodeQL.
.github/workflows/compare_translations.py	New utility script for comparing translation files.
.github/workflows/countline.py	New script to analyze files for line count.
.github/workflows/eslint_disable_check.py	New script to check for eslint-disable statements in TypeScript files.
.github/workflows/issue.yml	Modified workflow for issue labeling and greeting users.
.github/workflows/linter.yml	Deleted linter workflow file.
.github/workflows/npm-publish.yml	Deleted npm publish workflow file.
.github/workflows/pull-request-target.yml	New workflow for managing pull request interactions.
.github/workflows/pull-request.yml	New workflow for managing pull request checks and tests.
.github/workflows/push.yml	New workflow for testing and code coverage on push events.
.github/workflows/stale.yml	New workflow for managing stale issues and pull requests.
.github/workflows/talawa_admin_md_mdx_format_adjuster.py	New script for adjusting Markdown files to MDX format.
.gitignore	Updated to ignore additional files and directories.
.husky/post-merge	New script to install dependencies if package.json changes.
.husky/pre-commit	New script to run formatting and linting checks before commits.
.lintstagedrc.json	New configuration for lint-staged to run commands on staged files.
.node-version	Updated Node.js version specification.
.prettierignore	Updated to ignore the .github directory and other files.
.prettierrc	Added property for handling line endings.
CODEOWNERS	New file designating code ownership for the repository.
CODE_OF_CONDUCT.md	Added a Table of Contents for better navigation.
CODE_STYLE.md	New comprehensive code style guide for the project.
CONTRIBUTING.md	Updated for clarity and organization, including a Table of Contents.
DOCUMENTATION.md	New documentation file for accessing project documentation.
INSTALLATION.md	New installation guide for the project.
ISSUE_GUIDELINES.md	New document standardizing issue reporting processes.
PR-guidelines.md	Removed file containing PR submission guidelines.
PR_GUIDELINES.md	New comprehensive PR submission guidelines.
README.md	Enhanced structure and content, including a new community section and links to documentation.
config/babel.config.cjs	New Babel configuration file for modern JavaScript and TypeScript support.
config/vite.config.ts	New Vite configuration file for build and development setup.
index.html	New main entry point HTML file for the web application.
schema.graphql	New GraphQL schema defining various types and directives for the application.
public/locales/...	New localization files for multiple languages (English, French, Hindi, Spanish, Chinese) containing key-value pairs for UI elements and error messages.
scripts/__mocks__/*.ts	New mock files for testing, including Jest mock functions for various libraries.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant GitHub
    participant CI/CD
    participant Application

    User->>GitHub: Create Pull Request
    GitHub->>CI/CD: Trigger Workflows
    CI/CD->>Application: Run Tests
    Application-->>CI/CD: Return Test Results
    CI/CD-->>GitHub: Update PR Status

Loading

Assessment against linked issues

Objective	Addressed	Explanation
Replace Jest-specific functions and mocks with Vitest equivalents (2582)	✅
Ensure all tests in src/screens/UserPortal/Volunteer/UpcomingEvents pass after migration (2582)	✅
Maintain the test coverage for the file as 100% after migration (2582)	❓	Coverage status is not explicitly provided in the PR description.
Upload a video or photo for this specific file coverage is 100% in the PR description (2582)	❌	No video or photo of coverage uploaded in the PR description.

Possibly related issues

• Refactor: src/screens/EventVolunteers/Requests from Jest to Vitest #2547: Refactor of src/screens/EventVolunteers/Requests to Vitest aligns with the overall migration strategy.
• Refactor:src/screens/UserPortal/Events from Jest to Vitest #2574: Refactor of src/screens/UserPortal/Events to Vitest is part of the same migration effort.
• Refactor: src/screens/EventVolunteers/Volunteers from Jest to Vitest #2550: Refactor of src/screens/EventVolunteers/Volunteers to Vitest is relevant to the testing framework changes.
• Refactor: src/screens/EventManagement from Jest to Vitest #2546: Refactor of src/screens/EventManagement to Vitest supports the migration theme.
• Refactor: src/screens/UserPortal/Volunteer/VolunteerManagement.test.tsx from Jest to Vitest #2581: Refactor of src/screens/UserPortal/Volunteer/VolunteerManagement.test.tsx to Vitest is related to the overall testing migration.
• Refactor: src/screens/UserPortal/Volunteer/Invitations from Jest to Vitest #2583: Refactor of src/screens/UserPortal/Volunteer/Invitations to Vitest is part of the migration effort.

Possibly related PRs

• coderabbit yaml file #1991: Introduces a new .coderabbit.yaml configuration file relevant to the current PR.
• develop branch - coderabbit yaml file #1997: Adds a .coderabbit.yaml file, reinforcing the relevance to the main PR.
• Fixes: Translations Are Not Correctly Tested in Our PR Workflow  #2263: Enhances handling of translation files, potentially related to the new localization files.
• feat: Workflow changes which will label issues automatically as per #2256 #2390: Introduces a job for automatic labeling, which may relate to the new configurations.
• Refactored src/components/AddOn/support/components/Action/Action.test.tsx from Jest to Vitest #2482: Refactors tests from Jest to Vitest, aligning with the current PR's objectives.

Suggested labels

refactor

Suggested reviewers

• pranshugupta54
• varshith257
• GlenDsza

Poem

🐰 In the code where bunnies hop,
New configs make the workflow pop!
With tests refactored, all in line,
Talawa's growth is simply divine!
So let us code and let us cheer,
For every change brings us near!

---

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

🧹 Outside diff range and nitpick comments (49)

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

11-11: Remove commented debug code.

Remove the commented console.log statement as it's not needed in the final implementation.

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

---

14-21: Consider enhancing the mock PDF generation.

The current implementation creates a basic PDF-like structure. Consider adding more realistic PDF elements like:

• PDF version (e.g., %PDF-1.7)
• EOF marker (%%EOF)
• Basic object structure

This would make the mock more useful for testing PDF parsing scenarios.

---

10-13: Consider separating validation checks.

The current implementation combines two validation checks into one condition. Consider separating them for better error messages and maintainability.

-  if (template.schemas.length === 0 || inputs.length === 0) {
-    throw new Error('Template or inputs cannot be empty.');
-  }
+  if (template.schemas.length === 0) {
+    throw new Error('Template schemas cannot be empty.');
+  }
+  if (inputs.length === 0) {
+    throw new Error('Inputs cannot be empty.');
+  }

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

4-47: Improve test organization and coverage.

Consider enhancing the test suite with:

1. A describe block for successful cases and another for error cases
2. Test for minimum content size calculation
3. Test for PDF header presence in the output

describe('generate', () => {
  describe('successful cases', () => {
    it('should generate valid PDF structure', async () => {
      const result = await generate({
        template: { schemas: ['field1'] } as Template,
        inputs: [{ field1: 'value1' }],
      });
      
      // Check PDF header
      expect(result.slice(0, 4)).toEqual(new Uint8Array([0x25, 0x50, 0x44, 0x46]));
    });
  });

  describe('error cases', () => {
    // ... existing error tests ...
  });
});

.github/workflows/countline.py (3)

255-255: Use 'utf-8' encoding when opening files

When reading files, it's preferable to use 'utf-8' encoding to support a wide range of characters and ensure consistency.

Apply this diff to change the file encoding:

-    with open(filepath, encoding="latin-1") as code:
+    with open(filepath, encoding="utf-8") as code:

---

280-280: Simplify boolean expression for readability

You can simplify the condition by directly checking the boolean variable without using bool() or comparing it to True.

Apply this diff to simplify the condition:

-    if bool(errors_found) is True:
+    if errors_found:

---

286-286: Correct typo in the output message

There's a typo in "pre-requisite"; it should be "prerequisite".

Apply this diff to fix the typo:

-    Please fix this. It is a pre-requisite for pull request approval.
+    Please fix this. It is a prerequisite for pull request approval.

.husky/post-merge (2)

4-4: Ensure reliable detection of changes in 'package.json'

The command git diff HEAD^ HEAD may not detect changes in package.json in all merge scenarios, such as fast-forward merges. Consider using git diff-tree to reliably detect changes during merges.

Apply this diff to improve the change detection:

-git diff HEAD^ HEAD --exit-code -- ./package.json || npm install
+if git diff-tree -r --name-only --no-commit-id ORIG_HEAD HEAD | grep -q 'package.json'; then
+  npm install
+fi

This ensures that npm install is run only when package.json has changed during a merge.

---

4-4: Add a newline at the end of the file

For compatibility and to adhere to POSIX standards, it's recommended to have a newline character at the end of the file.

Please add a newline at the end of the file.

.lintstagedrc.json (1)

2-3: Include '.yaml' extension in file patterns for consistency

The file patterns include *.yml but exclude *.yaml. If your project uses the .yaml extension, consider adding it to ensure all YAML files are linted and formatted.

Apply this diff to include the .yaml extension:

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

.husky/pre-commit (1)

5-5: Remove or uncomment the lint:fix command

The commented out npm run lint:fix command should either be removed if not needed or uncommented if it serves a purpose. Having commented code can lead to confusion.

-# npm run lint:fix

scripts/vitest-setup.ts (1)

4-7: Enhance polyfill setup with error handling

The polyfill setup could be more robust by adding error handling and ensuring both TextEncoder and TextDecoder are properly initialized.

-if (typeof global.TextEncoder === 'undefined') {
-  global.TextEncoder = TextEncoder;
-  global.TextDecoder = TextDecoder;
+try {
+  if (typeof global.TextEncoder === 'undefined') {
+    global.TextEncoder = TextEncoder;
+  }
+  if (typeof global.TextDecoder === 'undefined') {
+    global.TextDecoder = TextDecoder;
+  }
+} catch (error) {
+  console.error('Failed to setup TextEncoder/TextDecoder polyfills:', error);
+  throw error;
}

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

5-5: Consider making the directory path configurable

The script assumes the current directory ('./') which might not always be the desired location. Consider making this configurable.

+const DIR_PATH = process.env.MARKDOWN_DIR || './';
+
 const markdownFiles = fs
-  .readdirSync('./')
+  .readdirSync(DIR_PATH)
   .filter((file) => file.endsWith('.md'));

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

4-7: Fix JSDoc tag

The @pdfme tag is undefined. Consider using a standard JSDoc link tag instead.

- * A custom environment to set the TextEncoder and TextDecoder variables, that is required by @pdfme during testing.
+ * A custom environment to set the TextEncoder and TextDecoder variables, that is required by
+ * {@link https://github.com/pdfme/pdfme|pdfme} during testing.

🧰 Tools

🪛 eslint

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

(tsdoc/syntax)

---

9-15: Add TypeScript return type annotations

Add return type annotations to improve type safety and documentation.

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

🧰 Tools

🪛 eslint

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

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

---

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

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

config/vite.config.ts (1)

27-28: Fix incorrect comment about default port

The comment states "this sets a default port to 3000" but the actual port is set to 4321.

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

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

27-28: Fix markdown formatting issues

There are two markdown linting issues to address:

1. Bare URL used on line 28
2. Emphasis used instead of heading for "Potential internship candidates"

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

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

🧰 Tools

🪛 Markdownlint (0.35.0)

28-28: null
Bare URL used

(MD034, no-bare-urls)

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

6-6: Remove trailing spaces

Remove trailing spaces from lines 6, 17, and 20 to fix YAML linting errors.

Also applies to: 17-17, 20-20

🧰 Tools

🪛 yamllint (1.35.1)

[error] 6-6: trailing spaces

(trailing-spaces)

.github/workflows/stale.yml (1)

6-6: Remove trailing spaces.

There are trailing spaces in these lines that should be removed.

-# be placed in this file 
+# be placed in this file
-  pull-requests: write  
-  
+  pull-requests: write
+

Also applies to: 20-21

🧰 Tools

🪛 yamllint (1.35.1)

[error] 6-6: trailing spaces

(trailing-spaces)

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

41-41: Enhance TSDoc detection regex.

The current regex might match non-TSDoc comments. Consider using a more precise pattern that validates TSDoc structure.

-    return /\/\*\*[\s\S]*?\*\//.test(content);
+    return /\/\*\*\s*\n\s*\*[\s\S]*?\*\//.test(content);

---

50-50: Improve directory path handling.

Consider normalizing and validating the input directory path.

-  const dir = process.argv[2] || './src';
+  const dir = path.resolve(process.argv[2] || './src');
+  try {
+    await fs.access(dir);
+  } catch (err) {
+    console.error(`Invalid directory path: ${dir}`);
+    process.exit(1);
+  }

---

32-33: Enhance error handling.

Consider adding more context to error messages and potentially implementing a retry mechanism for transient file system errors.

-    console.error(`Error reading directory ${dir}: ${err.message}`);
+    console.error(`Failed to read directory ${dir}:`, {
+      error: err.message,
+      stack: err.stack,
+      path: dir
+    });
-    console.error(`Error reading file ${filePath}: ${err.message}`);
+    console.error(`Failed to read file ${filePath}:`, {
+      error: err.message,
+      stack: err.stack,
+      path: filePath
+    });

Also applies to: 43-44

.github/workflows/push.yml (1)

17-18: Fix YAML formatting issues

There are several formatting issues in the workflow file:

• Trailing spaces on lines 17, 18, 21, 50
• Incorrect indentation in the env section
• Extra blank lines at the end

Also applies to: 20-21, 50-50, 62-62

🧰 Tools

🪛 yamllint (1.35.1)

[error] 17-17: trailing spaces

(trailing-spaces)

---

[error] 18-18: trailing spaces

(trailing-spaces)

jest.config.js (1)

48-51: Uncomment or remove watch plugins

The watch plugins configuration is commented out. Either remove these lines or uncomment them if they're needed.

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

10-18: Improve error handling in containsSkipComment

The function swallows errors and returns false, which might lead to false positives. Consider propagating the error or adding better error handling.

  } catch (error) {
-   console.error(`Error reading file ${file}:`, error.message);
-   return false;
+   throw new Error(`Failed to read file ${file}: ${error.message}`);
  }

🧰 Tools

🪛 eslint

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

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

.github/workflows/issue.yml (1)

21-25: Consider using a more specific sparse-checkout pattern

The sparse-checkout is configured to only include the auto-label.json5 file, but the path includes the entire .github/workflows/ directory. For better efficiency, use the full path:

- sparse-checkout: |
-   .github/workflows/auto-label.json5
+ sparse-checkout: auto-label.json5

.github/workflows/talawa_admin_md_mdx_format_adjuster.py (1)

66-94: Add progress reporting and parallel processing

For large directories with many files, consider adding progress reporting and parallel processing.

+ from concurrent.futures import ThreadPoolExecutor
+ from tqdm import tqdm

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."
    )
+   parser.add_argument(
+       "--workers",
+       type=int,
+       default=4,
+       help="Number of worker threads (default: 4)"
+   )

    args = parser.parse_args()

    # Collect all markdown files first
+   md_files = []
    for root, _, files in os.walk(args.directory):
        for file in files:
            if file.lower().endswith(".md"):
-               process_file(os.path.join(root, file))
+               md_files.append(os.path.join(root, file))

+   # Process files in parallel with progress bar
+   with ThreadPoolExecutor(max_workers=args.workers) as executor:
+       list(tqdm(
+           executor.map(process_file, md_files),
+           total=len(md_files),
+           desc="Processing files"
+       ))

ISSUE_GUIDELINES.md (1)

44-44: Capitalize "Slack" references

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

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

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

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

Also applies to: 53-53, 57-57

🧰 Tools

🪛 LanguageTool

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

(ON_SKYPE)

README.md (2)

51-51: Fix typo in documentation

"documenation" should be "documentation"

---

53-53: Fix heading formatting

Remove extra space after the hash in the heading "# Videos"

-#  Videos
+# Videos

🧰 Tools

🪛 Markdownlint (0.35.0)

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

(MD019, no-multiple-space-atx)

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

6-71: Remove trailing spaces in YAML

Multiple lines contain trailing spaces which should be removed for better YAML formatting.

🧰 Tools

🪛 yamllint (1.35.1)

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 13-13: trailing spaces

(trailing-spaces)

---

[error] 15-15: trailing spaces

(trailing-spaces)

---

[error] 27-27: trailing spaces

(trailing-spaces)

---

[error] 28-28: trailing spaces

(trailing-spaces)

---

[error] 29-29: trailing spaces

(trailing-spaces)

---

[error] 31-31: trailing spaces

(trailing-spaces)

---

[error] 33-33: trailing spaces

(trailing-spaces)

---

[error] 34-34: trailing spaces

(trailing-spaces)

---

[error] 36-36: trailing spaces

(trailing-spaces)

---

[error] 41-41: trailing spaces

(trailing-spaces)

---

[error] 46-46: trailing spaces

(trailing-spaces)

---

[error] 71-71: trailing spaces

(trailing-spaces)

.github/workflows/eslint_disable_check.py (2)

61-61: Rename unused loop variable

The loop variable dirs is not used within the loop body. Rename it to _dirs to indicate it's intentionally 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.0)

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

Rename unused dirs to _dirs

(B007)

---

39-41: Remove extra blank line

Remove the extra blank line after the pattern definition for better code organization.

    eslint_disable_pattern = re.compile(r'//\s*eslint-disable(?:-next-line|-line)?', re.IGNORECASE)
-    
    try:

.eslintrc.json (1)

82-86: Consider relaxing interface naming restrictions.

The current configuration requires interfaces to be prefixed with either "Interface" or "TestInterface". This might be overly restrictive and goes against common TypeScript conventions where interfaces typically don't require specific prefixes.

Consider modifying the rule to allow more flexible interface naming:

-        "prefix": ["Interface", "TestInterface"]
+        "format": ["PascalCase"]

PR_GUIDELINES.md (2)

31-34: Add language specifiers to code blocks.

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

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

Also applies to: 39-42

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

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

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

(MD040, fenced-code-language)

</details>

</details>

---

`58-61`: **Improve clarity of test requirements.**

The section about test requirements could be more specific about Vitest, given the project's migration from Jest to Vitest.

Consider adding explicit mention of Vitest:
```diff
-Upon successful push to the fork, check if all tests are passing
+Upon successful push to the fork, ensure all Vitest tests pass by running `npm run test:vitest`

🧰 Tools

🪛 LanguageTool

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

CODE_STYLE.md (3)

53-54: Fix grammatical error in fragment closure statement.

The statement "All the Return fragment should be closed in empty tag" has grammatical issues.

-All the Return fragment should be closed in empty tag
+All React fragments should be closed with empty tags

🧰 Tools

🪛 LanguageTool

[uncategorized] ~53-~53: The grammatical number of this noun doesn’t look right. Consider replacing it.
Context: ...ase naming convention - All the Return fragment should be closed in empty tag - Use of...

(AI_EN_LECTOR_REPLACEMENT_NOUN_NUMBER)

---

58-62: Add language identifiers to code blocks.

Code blocks should specify their language for proper syntax highlighting.

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

Also applies to: 78-89

🧰 Tools

🪛 Markdownlint (0.35.0)

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

(MD040, fenced-code-language)

---

71-78: Improve conflict resolution guidelines.

The conflict resolution section needs better formatting and clarity.

-Usually these conflicts are resolved in a **First Come First Serve** basis however there are certain exceptions to it.
+Usually, these conflicts are resolved on a **First Come, First Served** basis; however, there are certain exceptions:

🧰 Tools

🪛 LanguageTool

[uncategorized] ~71-~71: You might be missing the article “the” here.
Context: ...mponents should be either imported from React-Bootstrap library or Material UI librar...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

🪛 Markdownlint (0.35.0)

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)

---

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

(MD040, fenced-code-language)

CONTRIBUTING.md (2)

104-107: Add language identifiers to npm command blocks.

Code blocks should specify their language for proper syntax highlighting.

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

Also applies to: 114-117

🧰 Tools

🪛 Markdownlint (0.35.0)

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

(MD040, fenced-code-language)

---

77-78: Improve clarity in conflict resolution section.

The communication guidelines need better formatting and clarity.

-Last but not the least, communication is important make sure to talk to other contributors, in these cases, in slack channel or in a issue/PR thread.
+Communication is essential - make sure to discuss with other contributors in the Slack channel or in the relevant issue/PR thread.

🧰 Tools

🪛 LanguageTool

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

INSTALLATION.md (2)

321-335: Fix markdown formatting issues

Several formatting inconsistencies need to be addressed:

1. Heading levels should only increment by one level at a time (h3 to h4 jump)
2. Code blocks should specify a language
3. Use fenced code blocks consistently instead of indented blocks

Apply these changes:

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

-#### post-merge hook
+### post-merge hook

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

-        git pull --no-verify
+```bash
+git pull --no-verify
+```

🧰 Tools

🪛 Markdownlint (0.35.0)

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

(MD001, heading-increment)

---

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)

---

228-233: Enhance reCAPTCHA setup guidance

The current wording about reCAPTCHA setup in development environments could be clearer. Consider providing more context about why it's not recommended in development.

-You may not want to setup reCAPTCHA since the project will still work. Moreover, it is recommended to not set it up in development environment.
+reCAPTCHA setup is optional and not recommended for development environments to simplify local testing and debugging. The application will function without it.

🧰 Tools

🪛 LanguageTool

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

DOCUMENTATION.md (1)

22-29: Fix grammar and consistency issues

Several minor issues need to be addressed for better clarity and professionalism.

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

-A local version of `docs.talawa.io` should automatically launched
+A local version of `docs.talawa.io` should automatically launch

-Add/modify the markdown documents
+Add/modify the Markdown documents

-monitor the local website in your brower
+monitor the local website in your browser

🧰 Tools

🪛 Markdownlint (0.35.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)

.github/workflows/README.md (5)

7-7: Improve clarity of the warning message

The warning about file changes could be clearer about the implications and process.

-Any changes to files in this directory are flagged when pull requests are run. Make changes only on the advice of a contributor.
+Changes to workflow files are automatically flagged during pull request checks. Please consult with a project contributor before making any modifications to these files.

---

13-15: Fix grammatical issues in the requirements list

Add a comma after "possible" and fix list formatting.

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

🧰 Tools

🪛 LanguageTool

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

(AI_HYDRA_LEO_MISSING_COMMA)

---

24-24: Fix typo in workflow description

Remove the duplicate "to" in the sentence.

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

🧰 Tools

🪛 LanguageTool

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

(ENGLISH_WORD_REPEAT_RULE)

---

35-35: Fix abbreviation format

The abbreviation "e.g." should include both periods.

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

🧰 Tools

🪛 LanguageTool

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

(E_G)

---

43-46: Consider adding links to linting tool documentation

The linting requirements would be more helpful with links to each tool's documentation or configuration guidelines.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between afa614a and c340f38.

⛔ Files ignored due to path filters (75)

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

📒 Files selected for processing (82)

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

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

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

💤 Files with no reviewable changes (13)

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

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

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

🧰 Additional context used

📓 Learnings (1)

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

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

🪛 eslint

scripts/custom-test-env.js

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

(tsdoc/syntax)

---

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

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

---

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

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

scripts/githooks/update-toc.js

[error] 11-12: Delete ··⏎

(prettier/prettier)

jest.config.js

[error] 33-33: Delete ·

(prettier/prettier)

---

[error] 34-34: Insert ,

(prettier/prettier)

scripts/githooks/check-localstorage-usage.js

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

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

---

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

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

---

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

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

---

[error] 89-89: Insert ,

(prettier/prettier)

---

[error] 92-92: Insert ,

(prettier/prettier)

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

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 17-17: trailing spaces

(trailing-spaces)

---

[error] 20-20: trailing spaces

(trailing-spaces)

---

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

(indentation)

---

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

(indentation)

.github/workflows/issue.yml

[error] 6-6: trailing spaces

(trailing-spaces)

---

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

(indentation)

---

[warning] 66-66: too many blank lines

(1 > 0) (empty-lines)

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

🪛 Markdownlint (0.35.0)

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

INSTALLATION.md

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

(MD001, heading-increment)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD014, commands-show-output)

---

105-105: null
Bare URL used

(MD034, no-bare-urls)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD046, code-block-style)

---

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

(MD046, code-block-style)

---

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

(MD051, link-fragments)

---

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

(MD051, link-fragments)

CODE_STYLE.md

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

57-57: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

73-73: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

75-75: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

92-92: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

190-190: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

230-230: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

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)

README.md

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

(MD019, no-multiple-space-atx)

PR_GUIDELINES.md

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

.github/ISSUE_TEMPLATE/bug-report.md

36-36: null
Bare URL used

(MD034, no-bare-urls)

---

33-33: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

DOCUMENTATION.md

25-25: null
Bare URL used

(MD034, no-bare-urls)

🪛 actionlint (1.7.4)

.github/workflows/codeql-codescan.yml

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

(action)

---

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

(action)

---

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

(action)

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

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

(expression)

---

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

(shellcheck)

---

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

(expression)

🪛 LanguageTool

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)

CODE_STYLE.md

[uncategorized] ~53-~53: The grammatical number of this noun doesn’t look right. Consider replacing it.
Context: ...ase naming convention - All the Return fragment should be closed in empty tag - Use of...

(AI_EN_LECTOR_REPLACEMENT_NOUN_NUMBER)

---

[uncategorized] ~55-~55: This verb does not appear to agree with the subject. Consider using a different form.
Context: ...y tag - Use of custom classes directly are refrained, use of modular css is encour...

(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)

---

[uncategorized] ~71-~71: You might be missing the article “the” here.
Context: ...mponents should be either imported from React-Bootstrap library or Material UI librar...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

---

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

---

[uncategorized] ~230-~230: You might be missing the article “a” here.
Context: ...iles imported into it How to compile Sass file src/assets/scss/app.scss is t...

(AI_EN_LECTOR_MISSING_DETERMINER_A)

---

[uncategorized] ~233-~233: A comma might be missing here.
Context: ...partial Sass files. According to naming convention the file name of the partial Sass files...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)

CONTRIBUTING.md

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

(INSERT_PLEASE)

---

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

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

(THE_SUPERLATIVE)

---

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

(UNLIKELY_OPENING_PUNCTUATION)

---

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

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

(IF_THERE_COMMA)

---

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

(RB_LY_COMMA)

---

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

(FIRST_SERVED)

---

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

(ON_SKYPE)

---

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

(EN_WORDINESS_PREMIUM_LAST_BUT_NOT_THE_LEAST)

---

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

(MISSING_TO_BETWEEN_BE_AND_VB)

---

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

(ON_SKYPE)

---

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

(EN_A_VS_AN)

---

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

(DURING_THAT_TIME_COMMA)

---

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

(MAC_OS)

---

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

(BE_VBP_IN)

---

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

(ON_SKYPE)

README.md

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

PR_GUIDELINES.md

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

(UNLIKELY_OPENING_PUNCTUATION)

---

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

(IN_ORDER_TO_PREMIUM)

---

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

(SPLIT_INFINITIVE)

---

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

(EN_WEAK_ADJECTIVE)

---

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

(SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)

---

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

(FIX_RESOLVE)

---

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

(SOONER_OR_LATER)

---

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

(COMMA_COMPOUND_SENTENCE)

---

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

(MAKE_CHANGES)

ISSUE_GUIDELINES.md

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

(UNLIKELY_OPENING_PUNCTUATION)

---

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

(IN_ORDER_TO_PREMIUM)

---

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

(EN_A_VS_AN)

---

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

(PLEASE_COMMA)

---

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

(AI_HYDRA_LEO_MISSING_COMMA)

---

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

(FIX_RESOLVE)

---

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

(MAKE_STYLE_BETTER)

---

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

(ON_SKYPE)

---

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

(ON_SKYPE)

---

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

(ON_SKYPE)

---

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

(PLEASE_COMMA)

.github/workflows/README.md

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

(AI_HYDRA_LEO_MISSING_COMMA)

---

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

(ENGLISH_WORD_REPEAT_RULE)

---

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

(E_G)

CODE_OF_CONDUCT.md

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

(ENGLISH_WORD_REPEAT_RULE)

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)

🪛 Ruff (0.8.0)

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

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

1-5: Verify the mock implementation usage

Let's ensure this mock is properly referenced and used consistently across the test files.

✅ Verification successful

Mock implementation is correctly used and referenced

The verification shows that the mock implementation is properly used:

• The mock is correctly set up in scripts/__mocks__/@dicebear/core.ts
• It's properly configured in Jest config (jest.config.js)
• The mocked value mocked-data-uri is consistently used and referenced in tests
• The only test file explicitly using this mock value is src/screens/MemberDetail/MemberDetail.test.tsx, which maintains consistency with the mock implementation

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for references to this mock and verify consistent usage

# Find test files using @dicebear/core
echo "Checking for test files using @dicebear/core:"
rg -l "@dicebear/core" "**/*.test.{ts,tsx,js,jsx}"

# Check for any hardcoded references to 'mocked-data-uri'
echo -e "\nChecking for hardcoded mock URI references:"
rg "mocked-data-uri" "**/*.test.{ts,tsx,js,jsx}"

# Verify no remaining jest.fn() calls related to avatar mocking
echo -e "\nChecking for remaining jest.fn() calls related to avatar mocking:"
rg "jest\.fn.*avatar" "**/*.test.{ts,tsx,js,jsx}"

Length of output: 700

---

Script:

#!/bin/bash
# Let's try a different approach to find test files and mock usage

# First, let's find all test files in the repository
echo "Finding all test files:"
fd -e test.ts -e test.tsx -e test.js -e test.jsx

# Look for @dicebear/core imports or usage
echo -e "\nChecking for @dicebear/core usage:"
rg "@dicebear/core"

# Check for mocked-data-uri string
echo -e "\nChecking for mocked-data-uri references:"
rg "mocked-data-uri"

# Look for avatar-related jest mocks
echo -e "\nChecking for avatar-related jest mocks:"
rg "jest\.fn.*avatar|createAvatar.*jest\.fn"

Length of output: 13831

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

54-67: Same naming convention issues as Chinese translations

See the review comment for the Chinese translations file regarding standardizing the i18n key naming convention.

---

1-98: Inconsistency between PR objectives and provided files

The PR objectives mention migrating test cases for the UpcomingEvents component from Jest to Vitest. However, the files provided for review are localization JSON files. Please verify if:

1. The correct files were provided for review
2. The PR objectives need to be updated
3. The localization changes are part of the same PR

scripts/vitest-setup.ts (1)

2-2: 🛠️ Refactor suggestion

Consider replacing jest-dom with testing-library/vitest

Since we're migrating to Vitest, consider using @testing-library/vitest instead of @testing-library/jest-dom for better compatibility.

-import '@testing-library/jest-dom';
+import '@testing-library/vitest';

Likely invalid or redundant comment.

public/manifest.json (1)

16-16: Verify the updated image path

Please confirm that the logo512.png file exists in the images/ directory.

✅ Verification successful

Image path verification successful

The image file logo512.png exists at the correct path public/images/logo512.png as specified in the manifest.json.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

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

Length of output: 135

.gitignore (1)

Line range hint 3-37: LGTM! Comprehensive updates to .gitignore

The changes follow best practices by:

• Ignoring lock files to prevent conflicts between package managers
• Properly formatting the coverage directory path
• Including environment files for security
• Adding common editor-specific directories

.github/pull_request_template.md (2)

4-11: LGTM! Clear branching strategy documentation.

The added branching strategy section effectively prevents PRs against the wrong branch, which is crucial for maintaining code stability.

---

22-33: Excellent additions for test-related PRs.

The new sections for issue number, test confirmation, and snapshots/videos are particularly valuable for test migration PRs like this one, ensuring proper documentation of test coverage and changes.

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

1-68: Verify PR scope alignment.

The changes reviewed (PR template, stale workflow, TSDoc checker) appear to be infrastructure improvements unrelated to the stated PR objective of migrating tests from Jest to Vitest. Consider:

1. Splitting these changes into separate PRs to maintain focused scope
2. Including the actual test migration changes

.github/workflows/push.yml (1)

54-54: 🛠️ Refactor suggestion

Add test command validation

The test command should fail if coverage thresholds are not met. Consider adding the --coverage-threshold flag.

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

Likely invalid or redundant comment.

.github/workflows/talawa_admin_md_mdx_format_adjuster.py (1)

19-44: Consider adding test cases for edge cases

The escape_mdx_characters function handles basic escaping well, but should consider edge cases:

1. Already escaped sequences
2. Code blocks where escaping might not be needed
3. URLs containing special characters

|[.](.[<>{}].*)' --type md

</details>
<details>
<summary>.github/workflows/eslint_disable_check.py (1)</summary>

`1-122`: **LGTM with minor improvements**

The script is well-structured, properly documented, and follows Python coding standards. The implementation effectively checks for eslint-disable statements in TypeScript files.

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

<details>
<summary>🪛 Ruff (0.8.0)</summary>

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

Rename unused `dirs` to `_dirs`

(B007)

</details>

</details>

</details>
<details>
<summary>.eslintrc.json (1)</summary>

`4-6`: **LGTM: Environment configuration is appropriate.**

The addition of `node`, `es6`, and `jest` environments aligns well with a modern JavaScript/TypeScript project setup.

</details>
<details>
<summary>CODE_OF_CONDUCT.md (2)</summary>

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

The table of contents is well-organized and properly implemented using markdown links. The HTML comment markers for the TOC are a good practice for automated TOC generation tools.

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

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

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

(ENGLISH_WORD_REPEAT_RULE)

</details>

</details>

---

`1-1`: **Verify completeness of the PR review**

The PR objectives mention migrating test cases from Jest to Vitest, but the files provided for review are documentation files. Please ensure that the test migration files are included in the review.

<details>
<summary>✅ Verification successful</summary>

**Migration from Jest to Vitest is properly implemented**

The test file has been successfully migrated to Vitest:
- Uses Vitest's `vi` for mocking instead of Jest's `jest` object
- Has proper Vitest configuration in `vitest.config.ts`
- Test file structure follows Vitest conventions
- No remaining Jest-specific syntax or configurations found



</details>

<details>
<summary>🏁 Scripts executed</summary>

The following scripts were executed for the analysis:

Script:

```shell
#!/bin/bash
# Description: Check for Jest to Vitest migration files

# Look for test files in the specified directory
echo "Checking for test files in the UpcomingEvents component directory..."
fd -e test.js -e test.tsx -e spec.js -e spec.tsx . "src/screens/UserPortal/Volunteer/UpcomingEvents"

# Look for Vitest configuration
echo "Checking for Vitest configuration..."
fd vitest.config

Length of output: 438

---

Script:

#!/bin/bash
# Check the content of the test file and vitest config to verify migration status
echo "Content of UpcomingEvents.test.tsx:"
cat src/screens/UserPortal/Volunteer/UpcomingEvents/UpcomingEvents.test.tsx

echo -e "\nContent of vitest.config.ts:"
cat vitest.config.ts

# Search for any remaining Jest-specific syntax or configurations
echo -e "\nChecking for Jest-specific patterns:"
rg -i "jest\." src/screens/UserPortal/Volunteer/UpcomingEvents/UpcomingEvents.test.tsx || true
rg -i "describe|test|it|expect" src/screens/UserPortal/Volunteer/UpcomingEvents/UpcomingEvents.test.tsx || true

Length of output: 12042

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

2-6: LGTM! Improved frontmatter formatting

The standardization of naming conventions and format is good. Using lowercase for labels follows GitHub's conventions.

[coderabbitai]

⚠️ Potential issue

Replace Jest mocks with Vitest equivalents

The current implementation uses Jest-specific jest.fn() which needs to be replaced with Vitest's vi.fn() for compatibility.

Apply this diff to migrate to Vitest:

-export const createAvatar = jest.fn(() => {
+export const createAvatar = vi.fn(() => {
   return {
-    toDataUri: jest.fn(() => 'mocked-data-uri'),
+    toDataUri: vi.fn(() => 'mocked-data-uri'),
   };
 });

Don't forget to add the following import at the top of the file:

import { vi } from 'vitest';

[coderabbitai]

⚠️ Potential issue

Fix incorrect Promise return tests.

The first two tests have issues:

1. They use empty arrays which should throw errors according to the implementation
2. The second test is missing await and incorrectly checks the Promise instead of its resolved value

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

📝 Committable suggestion

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

Suggested change

	test('should return a Promise', async () => {
	const result = generate({
	template: { schemas: [] } as Template,
	inputs: [],
	});
	expect(result).toBeInstanceOf(Promise);
	});
	test('should resolve to a Uint8Array', async () => {
	const result = generate({
	template: { schemas: [] } as Template,
	inputs: [],
	});
	expect(result).toBeInstanceOf(Uint8Array);
	});
	test('should return a Promise that resolves to Uint8Array', async () => {
	const result = generate({
	template: { schemas: ['field1'] } as Template,
	inputs: [{ field1: 'value1' }],
	});
	expect(result).toBeInstanceOf(Promise);
	const resolved = await result;
	expect(resolved).toBeInstanceOf(Uint8Array);
	});

[coderabbitai]

🛠️ Refactor suggestion

Fix formatting and complete the error messages

Several messages need attention:

1. Remove unnecessary trailing space and period in "talawaApiUnavailable"
2. Complete the authorization message in "notAuthorised"
3. Complete the not found message in "notFoundMsg"

-  "talawaApiUnavailable": "Le service Talawa-API n'est pas disponible !. ",
+  "talawaApiUnavailable": "Le service Talawa-API n'est pas disponible !",
-  "notAuthorised": "Désolé! ",
+  "notAuthorised": "Désolé ! Vous n'êtes pas autorisé !",
-  "notFoundMsg": "Oops! ",
+  "notFoundMsg": "Oops ! La page que vous avez demandée est introuvable !"

Also applies to: 5-5, 8-8

[coderabbitai]

🛠️ Refactor suggestion

Standardize i18n key naming convention

Some keys use PascalCase with spaces while others use camelCase. For consistency and better maintainability:

1. Use camelCase for all keys
2. Avoid spaces in keys

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

📝 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

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

[coderabbitai]

🛠️ Refactor suggestion

Include the original exception when re-raising to preserve traceback

When re-raising an exception, it's important to include the original exception as context. Modify the raise statement to use from e to maintain the traceback.

Apply this diff to include the original exception:

     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

📝 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

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

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)

[coderabbitai]

⚠️ Potential issue

Fix potential command injection vulnerability.

The unquoted use of ${CHANGED_FILES} could lead to command injection.

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

📝 Committable suggestion

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

Suggested change

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

🧰 Tools

🪛 actionlint (1.7.4)

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

(shellcheck)

[coderabbitai]

⚠️ Potential issue

Fix broken image links.

The image links are using empty markdown references which won't work.

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

📝 Committable suggestion

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

Suggested change

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

🧰 Tools

🪛 Markdownlint (0.35.0)

158-158: null
No empty links

(MD042, no-empty-links)

---

159-159: null
No empty links

(MD042, no-empty-links)

---

161-161: null
No empty links

(MD042, no-empty-links)

[coderabbitai]

🛠️ Refactor suggestion

Add test coverage requirements

Given the project's requirement for maintaining 100% test coverage, consider adding information about checking and maintaining coverage levels.

Add this section after the existing content:

+### Checking test coverage
+
+To ensure the required 100% test coverage is maintained, run:
+```bash
+npm run test:coverage
+```
+
+Review the coverage report to verify all new code is fully tested.

🧰 Tools

🪛 Markdownlint (0.35.0)

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

(MD040, fenced-code-language)

[coderabbitai]

⚠️ Potential issue

Fix incorrect context reference

The text mentions "feature request" in a bug report template, which is incorrect.

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

[coderabbitai]

🛠️ Refactor suggestion

Improve formatting of the internship section

The section needs proper markdown formatting:

1. Use proper heading syntax instead of bold text
2. Format the URL as a proper markdown link

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

📝 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

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

🧰 Tools

🪛 Markdownlint (0.35.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)

[palisadoes]

This PR needs to be closed. To many files were submitted

[abbi4code]

So i need to do the following and ensure of them @palisadoes

1. Fetch the latest upstream/develop-postgres files
2. Make your PR modifications based on the local copy of this develop-postgres branch
3. Submit your PRs against our develop-postgres branch.
4. Your source branch in your local repository must not be the same as the target branch