Fixed language switch

[KunalSewal]

What kind of change does this PR introduce?

Handles cases when userId is not available: If userId is not available, you should still allow the language change without updating the backend.
So this PR updates the language even if userId is not available.

Issue Number:

Fixes #3586

Snapshots/Videos:

mp4.mp4

If relevant, did you update the documentation?

No

Summary

This is my first open source contribution. I have tested the changes locally.
The issue of not being able to change the language is being resolved through this PR.

Does this PR introduce a breaking change?

No

Checklist

CodeRabbit AI Review

• I have reviewed and addressed all critical issues flagged by CodeRabbit AI
• I have implemented or provided justification for each non-critical suggestion
• I have documented my reasoning in the PR comments where CodeRabbit AI suggestions were not implemented

Test Coverage

• I have written tests for all new changes/features
• I have verified that test coverage meets or exceeds 95%
• I have run the test suite locally and all tests pass

Have you read the contributing guide?

Yes

Summary by CodeRabbit

• New Features

  • Expanded multi-language support with fresh translations in English, French, Hindi, Spanish, and Chinese.
  • Introduced new GraphQL schema with enhanced types and directives for improved API functionality.
  • New configuration files for various tools and services, including Babel and Vite, for better development experience.

• Documentation

  • Comprehensive updates to installation guides, tutorials, and community resources for improved onboarding.
  • Revamped documentation website with clear, structured content and enhanced navigation.
  • Added new sections for managing documentation versions and translating the site.

• Chores

  • Modernized build, test, and deployment workflows to boost performance and stability.
  • Introduced new scripts for health checks, code coverage validation, and linting to ensure code quality.

[coderabbitai]

Warning

Rate limit exceeded

@KunalSewal has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 4 minutes and 52 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 08688b6 and 059cc59.

📒 Files selected for processing (4)

• .github/ISSUE_TEMPLATE/bug-report.md (2 hunks)
• .github/workflows/check-tsdoc.js (1 hunks)
• public/locales/sp/translation.json (1 hunks)
• schema.graphql (1 hunks)

Walkthrough

This pull request makes extensive configuration and documentation updates across the repository. It introduces new configuration files (including a YAML language server config, Babel, Vite, Dependabot, and various workflow files) and removes legacy CI and Docker files. Multiple GitHub workflow definitions and shell/Python scripts are added or revised to enhance code quality checks, translation comparisons, merge conflict checks, and automated pull request handling. In addition, updates span ESLint/Prettier configurations, Git hooks, localization files for several languages, documentation guides, and a significant overhaul of the main package setup and GraphQL schema.

Changes

File(s)	Change Summary
.coderabbit.yaml, .dockerignore, .env.example, .node-version, .prettierrc	New configuration files added for YAML language server, Docker exclusions, environment variables template, Node version, and Prettier settings.
.eslintignore, .eslintrc.json, .lintstagedrc.json, .prettierignore	ESLint and Prettier configurations updated with new rules, ignore patterns, and formatting tasks.
.github/ISSUE_TEMPLATE/bug-report.md, .github/ISSUE_TEMPLATE/feature-request.md, .github/pull_request_template.md	GitHub issue and pull request templates updated with revised naming, sections, and additional fields (e.g., internship candidates).
.github/dependabot.yaml, multiple files in .github/workflows/ (e.g., auto-label.json5, check-tsdoc.js, codeql-codescan.yml, merge-conflict-check.yml, pull-request-target.yml, pull-request.yml, push-deploy-website.yml, push.yml, stale.yml)	Numerous GitHub Actions workflows added, modified, or removed to automate dependency updates, code analysis, merge conflict checking, PR validations, deployment steps, and stale issue management.
.husky/post-merge, .husky/pre-commit	Husky Git hooks added and updated to run dependency installs, auto-formatting, linting, and table-of-contents updates prior to commit.
Docker-related files in Docker_Container/ and Dockerfile	Legacy Docker configuration files removed and a new Dockerfile introduced for a Node.js application (using Node 20.10.0, specifying build and serve commands and exposing port 4321).
Various shell and Python scripts (e.g., validate-coderabbit.sh, countline.py, eslint_disable_check.py, talawa_admin_md_mdx_format_adjuster.py, compare_translations.py, etc.)	New scripts added for TSDoc validation, code coverage disable checks, translation file comparisons, file line counting, MDX conversion, and PR review validation.
Documentation and localization files (e.g., README.md, CONTRIBUTING.md, DOCUMENTATION.md, docs folder, and files under public/locales/)	Extensive updates to documentation guides, installation instructions, code style guides, and localization files in English, French, Hindi, Spanish, and Chinese.
schema.graphql, jest-preview.config.ts, jest.config.js, package.json, and config/*	GraphQL schema expanded with numerous new types and directives; new Jest and Babel/Vite configuration files added; main package.json updated (including dependency, script, and module type changes).
CODEOWNERS, CODE_OF_CONDUCT.md, CODE_STYLE.md, PR_GUIDELINES.md	Administrative documents updated or added to clarify code ownership, community conduct, style guidelines, and PR submission processes.
A collection of mock files and test files in scripts/__mocks__/ and test configurations	New Jest mock implementations added for external modules to support unit testing.

Sequence Diagram(s)

sequenceDiagram
    participant PR as "Pull Request"
    participant MCO as "Merge Conflict Check Workflow"
    participant API as "GitHub API"
    PR->>MCO: Trigger on PR event (open/reopen/sync)
    MCO->>API: Request mergeable status (with retries)
    API-->>MCO: Return mergeable status (true/false)
    MCO->>PR: Output merge conflict check result

Loading

sequenceDiagram
    participant PR as "Pull Request Target Event"
    participant PTW as "PR Target Workflow"
    participant Bot as "coderabbitai[bot]"
    PR->>PTW: Trigger pull_request_target
    PTW->>Bot: Post review policy comment and greeting
    Bot-->>PTW: Acknowledge and provide instructions
    PTW->>PR: Display guidelines and welcome message

Loading

Possibly related PRs

• coderabbit yaml file #1991: Adds a .coderabbit.yaml configuration for CodeRabbit AI; closely related as both PRs introduce a YAML language server configuration.
• develop branch - coderabbit yaml file #1997: Also adds a similar .coderabbit.yaml file; shares a focus on configuring YAML language servers for review automation.
• Plugin and advertisement screen revamp #2006: Involves configuration adjustments alongside localization updates; related through overall configuration and translation enhancements.

Suggested labels

ignore-sensitive-files-pr

Suggested reviewers

• palisadoes
• varshith257

Poem

I’m a little rabbit with joyful cheer,
Hopping through code, my paws so dear.
Configs and workflows now race in line,
With YAML dreams, everything shines.
Bugs get chased, and issues freeze,
Hop along with CodeRabbit with ease!
🐇✨ Happy coding, one hop at a time!

---

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

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

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

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

CodeRabbit Commands (Invoked using PR comments)

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

Other keywords and placeholders

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

Documentation and Community

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

[github-actions]

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

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

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

Our policies make our code better.

Reviewers

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

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

Reviewing Your Code

Your reviewer(s) will have the following roles:

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

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

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

Other

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

[github-actions]

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

[coderabbitai]

Actionable comments posted: 31

🧹 Nitpick comments (51)

docs/docs/tutorial-basics/markdown-features.mdx (2)

13-26: Use standard Markdown comment syntax.

The code example uses JavaScript-style comments (//) which is not standard in Markdown. Consider using HTML comments instead.

-// highlight-start
+<!-- highlight-start -->
 ---
 id: my-doc-id
 title: My document title
 description: My document description
 slug: /my-custom-url
 ---
-// highlight-end
+<!-- highlight-end -->

---

78-107: Consider using more professional terminology.

The word "awesome" in the tip example could be replaced with a more formal alternative.

 :::tip My tip

-Use this awesome feature option
+Use this powerful feature option

 :::

🧰 Tools

🪛 LanguageTool

[style] ~98-~98: Consider using a more formal and expressive alternative to ‘awesome’.
Context: ...erous ::: ``` :::tip My tip Use this awesome feature option ::: :::danger Take car...

(AWESOME)

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

7-7: Remove trailing space in translation value.

The Chinese translation for "noResultsFoundFor" has a trailing space which might cause UI alignment issues.

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

.husky/pre-commit (2)

3-3: Consider uncommenting the lint:fix command.

The lint:fix command is commented out. If it's needed, consider uncommenting it. If it's not needed, consider removing it entirely to avoid confusion.

---

8-8: Consider being more selective with git add.

Using git add . might stage unintended files that were not modified by the pre-commit hook. Consider being more specific about which files to stage:

-git add .
+git add -u

This will only stage modified tracked files.

config/vite.config.ts (1)

24-30: Consider using environment variables for server configuration.

The server configuration has hardcoded values. Consider making the port configurable through environment variables for better flexibility across different environments.

   server: {
     // this ensures that the browser opens upon server start
     open: false,
     host: '0.0.0.0',
     // this sets a default port to 4321
-    port: 4321,
+    port: process.env.PORT ? parseInt(process.env.PORT, 10) : 4321,
   },

docs/src/pages/index.tsx (1)

24-37: Consider adding prop types for Layout component.

The code looks good, but consider adding explicit type definitions for the Layout component's props to improve type safety.

+ type LayoutProps = {
+   title: string;
+   description: string;
+ };

  export default function Home(): JSX.Element {
    const { siteConfig } = useDocusaurusContext();
    return (
      <Layout
        title={`Hello from ${siteConfig.title}`}
        description="Description will go into a meta tag in <head />"
      >

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

14-36: Enhance error handling in file search.

The function silently continues on errors. Consider propagating errors up or adding retry logic.

   async function findTsxFiles(dir) {
     let results = [];
     try {
       const list = await fs.readdir(dir);
       for (const file of list) {
         const filePath = path.join(dir, file);
-        const stat = await fs.stat(filePath);
+        let stat;
+        try {
+          stat = await fs.stat(filePath);
+        } catch (err) {
+          console.error(`Error getting stats for ${filePath}: ${err.message}`);
+          continue;
+        }
         if (stat.isDirectory()) {
           results = results.concat(await findTsxFiles(filePath));
         } else if (

---

50-67: Add summary statistics to run output.

Consider adding summary statistics about the number of files checked and the percentage with TSDoc comments.

   async function run() {
     const dir = process.argv[2] || './src';
     const files = await findTsxFiles(dir);
     const filesWithoutTsDoc = [];
+    let totalFiles = files.length;
 
     for (const file of files) {
       if (!await containsTsDocComment(file)) {
         filesWithoutTsDoc.push(file);
       }
     }
 
     if (filesWithoutTsDoc.length > 0) {
+      console.log(`TSDoc Coverage: ${((totalFiles - filesWithoutTsDoc.length) / totalFiles * 100).toFixed(2)}%`);
       filesWithoutTsDoc.forEach(file => {
         console.error(`No TSDoc comment found in file: ${file}`);
       });
       process.exit(1);
     }
+    console.log(`TSDoc Coverage: 100% (${totalFiles} files checked)`);
   }

docs/src/components/HomepageFeatures/index.tsx (1)

14-14: Consider optimizing SVG imports.

The current SVG imports using require().default could be optimized using direct imports with the ?react query suffix for better tree-shaking and bundle size.

-    Svg: require('@site/static/img/undraw_docusaurus_mountain.svg').default,
+    Svg: () => import('@site/static/img/undraw_docusaurus_mountain.svg?react'),

Also applies to: 24-24, 34-34

jest.config.js (1)

61-64: Consider enabling watch plugins for better development experience.

The commented out watch plugins could improve the development experience by providing better test filtering capabilities.

-  // watchPlugins: [
-  //   'jest-watch-typeahead/filename',
-  //   'jest-watch-typeahead/testname',
-  // ],
+  watchPlugins: [
+    'jest-watch-typeahead/filename',
+    'jest-watch-typeahead/testname',
+  ],

.github/workflows/scripts/talawa_admin_md_mdx_format_adjuster.py (1)

90-93: Add progress reporting for large directories.

When processing a large number of files, it would be helpful to show progress to the user.

+    total_files = sum(1 for _, _, files in os.walk(args.directory)
+                      for file in files if file.lower().endswith(".md"))
+    processed_files = 0
     for root, _, files in os.walk(args.directory):
         for file in files:
             if file.lower().endswith(".md"):
+                processed_files += 1
+                print(f"Processing file {processed_files}/{total_files}: {file}")
                 process_file(os.path.join(root, file))

.github/workflows/scripts/eslint_disable_check.py (3)

76-79: Simplify nested if statements.

The nested if statements can be combined for better readability.

-            if item.endswith(".ts") or item.endswith(".tsx"):
-                if has_eslint_disable(item):
-                    print(f"File {item} contains eslint-disable statement. Please remove them and ensure the code adheres to the specified ESLint rules.")
-                    eslint_found = True
+            if (item.endswith(".ts") or item.endswith(".tsx")) and has_eslint_disable(item):
+                print(f"File {item} contains eslint-disable statement. Please remove them and ensure the code adheres to the specified ESLint rules.")
+                eslint_found = True

🧰 Tools

🪛 Ruff (0.8.2)

76-77: Use a single if statement instead of nested if statements

(SIM102)

---

90-94: Fix multiline string formatting.

The multiline string in the print statement could be formatted better for readability.

-                            print(
-                                f"""File {file_path} contains eslint-disable
-                                statement."""
-                            )
+                            print(f"File {file_path} contains eslint-disable statement.")

---

29-30: Consider adding file extension constants.

The TypeScript file extensions are used in multiple places and could be defined as constants.

+TS_EXTENSIONS = (".ts", ".tsx")
+
 def has_eslint_disable(file_path):

Then use it in the code:

-            if item.endswith(".ts") or item.endswith(".tsx"):
+            if item.endswith(TS_EXTENSIONS):

.github/workflows/scripts/code_coverage_disable_check.py (1)

95-105: Simplify nested if statements.

The nested if statements can be combined using logical operators for better readability.

-        if os.path.isfile(item):
-            # If it's a file, check it directly
-            if (
-                item.endswith(".tsx")
-                or item.endswith(".ts")
-                and not item.endswith(".test.tsx")
-                and not item.endswith(".test.ts")
-                and not item.endswith(".spec.tsx")
-                and not item.endswith(".spec.ts")
-            ):
+        if os.path.isfile(item) and (
+            (item.endswith(".tsx") or item.endswith(".ts"))
+            and not any(item.endswith(ext) for ext in [".test.tsx", ".test.ts", ".spec.tsx", ".spec.ts"])
+        ):

🧰 Tools

🪛 Ruff (0.8.2)

95-105: Use a single if statement instead of nested if statements

(SIM102)

---

97-105: Use a single if statement instead of nested if statements

(SIM102)

.github/workflows/scripts/compare_translations.py (1)

134-136: Improve error handling in load_translation function.

Use raise ... from err to preserve the exception chain for better debugging.

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

🧰 Tools

🪛 Ruff (0.8.2)

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

(B904)

.github/workflows/scripts/countline.py (1)

255-255: Use UTF-8 encoding instead of latin-1.

Using latin-1 encoding might not handle all Unicode characters correctly. Consider using UTF-8 for better Unicode support.

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

Dockerfile (1)

1-15: Optimize the Dockerfile using multi-stage builds.

While the current Dockerfile follows best practices, it can be optimized further:

1. The stage name "build" is unnecessary since there are no subsequent stages.
2. Using a multi-stage build would reduce the final image size by excluding build dependencies.

Apply this diff to optimize the Dockerfile:

-FROM node:20.10.0 AS build
+FROM node:20.10.0-slim AS build
 
 WORKDIR /usr/src/app
 
 COPY package*.json ./
 
 RUN npm install
 
 COPY . .
 
 RUN npm run build
 
+FROM node:20.10.0-slim
+
+WORKDIR /usr/src/app
+
+COPY --from=build /usr/src/app/dist ./dist
+COPY package*.json ./
+
+RUN npm install --production
+
 EXPOSE 4321
 
 CMD ["npm", "run", "serve"]

docs/docs/tutorial-basics/deploy-your-site.md (1)

1-32: LGTM with a minor suggestion.

The deployment instructions are clear and well-structured.

Consider this minor improvement to avoid the intensifier "very":

-You can now deploy the `build` folder **almost anywhere** easily, **for free** or very small cost (read the **[Deployment Guide](https://docusaurus.io/docs/deployment)**).
+You can now deploy the `build` folder **almost anywhere** easily, **for free** or at minimal cost (read the **[Deployment Guide](https://docusaurus.io/docs/deployment)**).

🧰 Tools

🪛 LanguageTool

[style] ~31-~31: As an alternative to the over-used intensifier ‘very’, consider replacing this phrase.
Context: ...most anywhere** easily, for free or very small cost (read the **[Deployment Guide](htt...

(EN_WEAK_ADJECTIVE)

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

2-2: Remove trailing spaces from translations

There are unnecessary trailing spaces in the following translations:

• Line 2: "तलवा-एपीआई सेवा उपलब्ध नहीं है! "
• Line 5: "क्षमा मांगना! "
• Line 8: "उफ़! "

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

Also applies to: 5-5, 8-8

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

2-2: Remove trailing spaces from translations

There are unnecessary trailing spaces in the following translations:

• Line 2: "Le service Talawa-API n'est pas disponible !. "
• Line 5: "Désolé! "

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

Also applies to: 5-5

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

2-2: Fix grammar and punctuation consistency

There are a few issues to address:

1. Line 2: Remove the period after exclamation mark
2. Line 5: Capitalize "you" and fix "Authorised" to "Authorized" (US English)
3. Line 10: Fix typo "occured" to "occurred"

-  "talawaApiUnavailable": "Talawa-API service is unavailable!. Is it running? Check your network connectivity too.",
+  "talawaApiUnavailable": "Talawa-API service is unavailable! Is it running? Check your network connectivity too.",
-  "notAuthorised": "Sorry! you are not Authorised!",
+  "notAuthorised": "Sorry! You are not Authorized!",
-  "errorLoading": "Error occured while loading {{entity}} data",
+  "errorLoading": "Error occurred while loading {{entity}} data",

Also applies to: 5-5, 10-10

docs/docs/tutorial-basics/congratulations.md (1)

7-7: Enhance readability with style improvements.

Consider these minor style enhancements:

1. Line 7: Strengthen the wording by rephrasing to "You have successfully learned..."
2. Line 13: Consider using a single exclamation mark for a more professional tone

- You have just learned the **basics of Docusaurus** and made some changes to the **initial template**.
+ You have successfully learned the **basics of Docusaurus** and made some changes to the **initial template**.
- Anything **unclear** or **buggy** in this tutorial? [Please report it!](https://github.com/facebook/docusaurus/discussions/4610)
+ Anything **unclear** or **buggy** in this tutorial? [Please report it](https://github.com/facebook/docusaurus/discussions/4610)

Also applies to: 13-13

🧰 Tools

🪛 LanguageTool

[style] ~7-~7: Consider rephrasing this to strengthen your wording.
Context: ...earned the basics of Docusaurus and made some changes to the initial template. Docusauru...

(MAKE_CHANGES)

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

14-20: Fix trailing spaces in YAML.

Remove trailing spaces from lines 6, 17, and 20 to maintain consistent formatting.

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

🧰 Tools

🪛 YAMLlint (1.35.1)

[error] 17-17: trailing spaces

(trailing-spaces)

---

[error] 20-20: trailing spaces

(trailing-spaces)

---

21-30: Consider adding security enhancements to the CodeQL workflow.

1. Add permissions field to limit the workflow's access scope
2. Consider adding more languages to the matrix for comprehensive analysis

 jobs:
   CodeQL:
     if: ${{ github.actor != 'dependabot[bot]' }}
     name: Analyse Code With CodeQL
     runs-on: ubuntu-latest
+    permissions:
+      security-events: write
+      actions: read
+      contents: read
     strategy:
       fail-fast: false
       matrix:
-        language: [ 'javascript' ]
+        language: [ 'javascript', 'typescript', 'python' ]

docs/package.json (1)

39-43: Make browser versions more specific in development.

The current development browser versions could be more specific to ensure consistent behavior across environments.

   "development": [
-      "last 3 chrome version",
-      "last 3 firefox version",
-      "last 5 safari version"
+      "last 3 chrome versions",
+      "last 3 firefox versions",
+      "last 5 safari versions"
   ]

.github/workflows/scripts/validate-coderabbit.sh (1)

1-9: Add shellcheck directives and improve error handling.

Add shellcheck directives and handle potential API rate limiting.

 #!/bin/bash
+set -euo pipefail
+
+# shellcheck disable=SC2086
 
 echo "Step 1: Fetching all PR reviews..."
 
+# Check if required environment variables are set
+[[ -z "${GITHUB_TOKEN:-}" ]] && { echo "Error: GITHUB_TOKEN is not set"; exit 1; }
+[[ -z "${GITHUB_REPOSITORY:-}" ]] && { echo "Error: GITHUB_REPOSITORY is not set"; exit 1; }
+[[ -z "${PR_NUMBER:-}" ]] && { echo "Error: PR_NUMBER is not set"; exit 1; }
+
 response=$(curl -s -f -H "Authorization: token $GITHUB_TOKEN" \
   "https://api.github.com/repos/${GITHUB_REPOSITORY}/pulls/${PR_NUMBER}/reviews?per_page=1000") || {
+  if [[ $(echo "$response" | jq -r '.message // empty') == *"API rate limit exceeded"* ]]; then
+    echo "Error: GitHub API rate limit exceeded"
+  else
     echo "Error: Failed to fetch reviews from GitHub API"
+  fi
   exit 1
 }

DOCUMENTATION.md (1)

26-26: Capitalize "Markdown" as it's a proper noun.

-1. Add/modify the markdown documents to the `docs/` directory of the `talawa-docs` repository
+1. Add/modify the Markdown documents to the `docs/` directory of the `talawa-docs` repository

🧰 Tools

🪛 LanguageTool

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

(MARKDOWN_NNP)

.github/workflows/stale.yml (1)

6-6: Remove trailing spaces.

There are trailing spaces at the end of several lines that should be removed for consistency.

-# Please read the README.md file in this directory that defines what should 
+# Please read the README.md file in this directory that defines what should
-  pull-requests: write  
+  pull-requests: write
-  
+
-    name: Process Stale Issues and PRs 
+    name: Process Stale Issues and PRs

Also applies to: 20-21, 24-24

🧰 Tools

🪛 YAMLlint (1.35.1)

[error] 6-6: trailing spaces

(trailing-spaces)

.github/workflows/push-deploy-website.yml (1)

6-6: Remove trailing spaces.

There are trailing spaces at the end of several lines that should be removed for consistency.

-# Please read the README.md file in this directory that defines what should 
+# Please read the README.md file in this directory that defines what should
-      - 'develop-postgres'   
+      - 'develop-postgres'
-      
+
-  
+
-      # This "name" has to be the repos' branch that contains 
+      # This "name" has to be the repos' branch that contains
-      # menu. The branch "name" must match the branch in the 
+      # menu. The branch "name" must match the branch in the
- 
+

Also applies to: 17-18, 21-21, 29-29, 33-33, 57-57

🧰 Tools

🪛 YAMLlint (1.35.1)

[error] 6-6: trailing spaces

(trailing-spaces)

.github/workflows/merge-conflict-check.yml (1)

46-46: Remove trailing space.

There is a trailing space that should be removed for consistency.

-              
+

🧰 Tools

🪛 YAMLlint (1.35.1)

[error] 46-46: trailing spaces

(trailing-spaces)

.github/workflows/README.md (2)

24-24: Fix typo in the text.

Remove the duplicate word "to".

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

🧰 Tools

🪛 LanguageTool

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

(ENGLISH_WORD_REPEAT_RULE)

---

35-35: Fix abbreviation format.

The abbreviation "eg." should be "e.g." with periods.

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

🧰 Tools

🪛 LanguageTool

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

(E_G)

.github/workflows/issue.yml (1)

42-55: Simplify label addition logic.

The current implementation uses repeated code for label addition. Consider refactoring to reduce duplication.

-            if(labels.data.reduce((a, c)=>a||["dependencies"].includes(c.name), false))
-              await github.rest.issues.addLabels({
-                owner: context.repo.owner,
-                repo: context.repo.repo,
-                issue_number: context.issue.number,
-                labels: ["good first issue", "security"]
-              });
-            else if(labels.data.reduce((a, c)=>a||["security", "ui/ux"].includes(c.name), false))
-              await github.rest.issues.addLabels({
-                owner: context.repo.owner,
-                repo: context.repo.repo,
-                issue_number: context.issue.number,
-                labels: ["good first issue"]
-              });
+            const labelSets = {
+              'dependencies': ["good first issue", "security"],
+              'security,ui/ux': ["good first issue"]
+            };
+            
+            for (const [triggers, newLabels] of Object.entries(labelSets)) {
+              if (labels.data.some(label => triggers.split(',').includes(label.name))) {
+                await github.rest.issues.addLabels({
+                  ...apiParams,
+                  labels: newLabels
+                });
+                break;
+              }
+            }

.github/workflows/scripts/app_health_check.sh (2)

47-52: Add timeout to nc command.

The nc command should include a timeout to prevent hanging in case of network issues.

-  if nc -z localhost "${port}" 2>/dev/null; then
+  if nc -z -w 5 localhost "${port}" 2>/dev/null; then

---

68-70: Add container existence check before fetching logs.

Verify if the container exists before attempting to fetch logs to provide better error messages.

     echo "Fetching Docker container logs..."
-    if ! docker logs talawa-admin-app-container; then
-      echo "Error: Failed to fetch logs from container talawa-admin-app-container"
+    if ! docker ps -q -f name=talawa-admin-app-container >/dev/null; then
+      echo "Error: Container talawa-admin-app-container does not exist"
+    elif ! docker logs talawa-admin-app-container; then
+      echo "Error: Failed to fetch logs from container talawa-admin-app-container"

ISSUE_GUIDELINES.md (3)

5-5: Fix grammatical error in introduction.

Change "a issues reports" to "issue reports".

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

🧰 Tools

🪛 LanguageTool

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

(EN_A_VS_AN)

---

29-29: Fix duplicate word in search instruction.

The line contains a duplicate "for" which affects readability.

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

---

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: 57-57, 70-70

🧰 Tools

🪛 LanguageTool

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

(ON_SKYPE)

README.md (1)

56-56: Add hyphen to compound adjective.

Add a hyphen to "open source" when it's used as a compound adjective before "contributors".

-The "[Getting Started - Developers](https://www.youtube.com/watch?v=YpBUoHxEeyg&list=PLv50qHwThlJUIzscg9a80a9-HmAlmUdCF&index=1)" videos are extremely helpful for new open source contributors.
+The "[Getting Started - Developers](https://www.youtube.com/watch?v=YpBUoHxEeyg&list=PLv50qHwThlJUIzscg9a80a9-HmAlmUdCF&index=1)" videos are extremely helpful for new open-source contributors.

🧰 Tools

🪛 LanguageTool

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

56-56: Improve clarity in reviewer assignment section.

Add a comma after "Therefore" and consider rephrasing to avoid the overused "very important".

-The quality of our code is very important to us. Therefore we make experienced maintainers of our code base review your code.
+The quality of our code is crucial to us. Therefore, we ensure experienced maintainers of our code base review your code.

🧰 Tools

🪛 LanguageTool

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

(EN_WEAK_ADJECTIVE)

---

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

(SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)

---

64-64: Improve clarity in notification section.

Add a comma before "and" in compound sentence and replace informal phrase.

-@mentioning someone just adds to the pile of notifications we get and it won't make us look at your issue faster.
+@mentioning someone just adds to the pile of notifications we get, and it won't expedite the review process.

🧰 Tools

🪛 LanguageTool

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

docs/README.md (1)

40-42: Fix code block language specifications.

Add language identifiers to code blocks for better syntax highlighting. For terminal commands, use bash or shell.

Example:

-```terminal
+```bash
$ yarn -version

Also applies to: 69-70, 82-83, 94-95, 107-108

🧰 Tools

🪛 markdownlint-cli2 (0.17.2)

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

(MD014, commands-show-output)

CODE_STYLE.md (1)

58-62: Add language identifiers to code examples.

Specify the language for code blocks to enable syntax highlighting.

Example:

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

Also applies to: 78-89

🧰 Tools

🪛 markdownlint-cli2 (0.17.2)

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

(MD040, fenced-code-language)

docs/src/css/custom.css (1)

175-186: Consolidate duplicate button styles.

The youtube-button and github-button classes share identical styles. Consider creating a common base class.

+.social-button {
+  background: linear-gradient(90deg, #ff3600 0%, #ff8100 100%);
+  border: none;
+  border-radius: 4px;
+  padding: 7px 21px;
+  color: #fff;
+  font-weight: bold;
+  font-size: 14px;
+  text-decoration: none;
+  display: inline-flex;
+  margin-right: 2.75rem;
+}
+
-.youtube-button {
-  background: linear-gradient(90deg, #ff3600 0%, #ff8100 100%);
-  border: none;
-  border-radius: 4px;
-  padding: 7px 21px;
-  color: #fff;
-  font-weight: bold;
-  font-size: 14px;
-  text-decoration: none;
-  display: inline-flex;
-  margin-right: 2.75rem;
+.youtube-button {
+  @extend .social-button;
}

-.github-button {
-  background: linear-gradient(90deg, #ff3600 0%, #ff8100 100%);
-  border: none;
-  border-radius: 4px;
-  padding: 7px 21px;
-  color: #fff;
-  font-weight: bold;
-  font-size: 14px;
-  text-decoration: none;
-  display: inline-flex;
-  margin-right: 2.75rem;
+.github-button {
+  @extend .social-button;
}

Also applies to: 188-199

CONTRIBUTING.md (1)

62-62: Minor grammar improvement needed.

Change "is best resource" to "is the best resource".

-[Pull Request guidelines](PR_GUIDELINES.md) is best resource to follow to start working on open issues.
+[Pull Request guidelines](PR_GUIDELINES.md) is the best resource to follow to start working on open issues.

🧰 Tools

🪛 LanguageTool

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

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

228-230: Consider improving the placeholder text format.

The placeholder text uses double curly braces {{name}} and {{org}} which is correct for i18n interpolation, but the surrounding text could be improved for better readability in Hindi.

-    "removeUserFrom": "{{org}} से उपयोगकर्ता को हटाएं",
-    "removeConfirmation": "क्या आप वाकई '{{name}}' को संगठन '{{org}}' से हटाना चाहते हैं?",
+    "removeUserFrom": "संगठन {{org}} से उपयोगकर्ता को हटाएं",
+    "removeConfirmation": "क्या आप वाकई {{name}} को संगठन {{org}} से हटाना चाहते हैं?",

---

774-775: Fix inconsistent placeholder example.

The placeholder example uses English text which should be translated to Hindi for consistency.

-    "userOtp": "जैसे ",
+    "userOtp": "उदाहरण: 123456",

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

16-16: Consider revising this translation for better clarity.

The translation "Una aplicación de código abierto de los voluntarios de la Fundación palisados" could be improved to "Una aplicación de código abierto desarrollada por los voluntarios de la Fundación Palisadoes" for better clarity and accuracy.

---

49-52: Consider using consistent capitalization in password requirements.

The password requirement translations have inconsistent capitalization:

• "Al menos una letra mayuscula" should be "Al menos una letra mayúscula"
• "Al menos una letra minúscula" is correct
• "Al menos un valor numérico" is correct
• "Al menos un carácter especial" is correct

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 6d67f00 and c831c4d.

⛔ Files ignored due to path filters (99)

• docs/docs/tutorial-extras/img/docsVersionDropdown.png is excluded by !**/*.png
• docs/docs/tutorial-extras/img/localeDropdown.png is excluded by !**/*.png
• docs/static/img/docusaurus-social-card.jpg is excluded by !**/*.jpg
• docs/static/img/docusaurus.png is excluded by !**/*.png
• docs/static/img/favicon.ico is excluded by !**/*.ico
• docs/static/img/icons/facebook.svg is excluded by !**/*.svg
• docs/static/img/icons/favicon_palisadoes.ico is excluded by !**/*.ico
• docs/static/img/icons/github-dark.svg is excluded by !**/*.svg
• docs/static/img/icons/github.svg is excluded by !**/*.svg
• docs/static/img/icons/instagram.svg is excluded by !**/*.svg
• docs/static/img/icons/opportunities.svg is excluded by !**/*.svg
• docs/static/img/icons/slack.svg is excluded by !**/*.svg
• docs/static/img/icons/source.svg is excluded by !**/*.svg
• docs/static/img/icons/team.svg is excluded by !**/*.svg
• docs/static/img/icons/twitter.svg is excluded by !**/*.svg
• docs/static/img/icons/youtube-white.svg is excluded by !**/*.svg
• docs/static/img/icons/youtube.svg is excluded by !**/*.svg
• docs/static/img/logo.svg is excluded by !**/*.svg
• docs/static/img/markdown/misc/logo.png is excluded by !**/*.png
• docs/static/img/undraw_docusaurus_mountain.svg is excluded by !**/*.svg
• docs/static/img/undraw_docusaurus_react.svg is excluded by !**/*.svg
• docs/static/img/undraw_docusaurus_tree.svg is excluded by !**/*.svg
• 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/options-outline.svg is excluded by !**/*.svg
• public/images/svg/organization.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 (107)

• .coderabbit.yaml (1 hunks)
• .dockerignore (1 hunks)
• .env.example (1 hunks)
• .eslintignore (1 hunks)
• .eslintrc.json (2 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/issue.yml (1 hunks)
• .github/workflows/linter.yml (0 hunks)
• .github/workflows/merge-conflict-check.yml (1 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-deploy-website.yml (1 hunks)
• .github/workflows/push.yml (1 hunks)
• .github/workflows/scripts/app_health_check.sh (1 hunks)
• .github/workflows/scripts/code_coverage_disable_check.py (1 hunks)
• .github/workflows/scripts/compare_translations.py (1 hunks)
• .github/workflows/scripts/countline.py (1 hunks)
• .github/workflows/scripts/eslint_disable_check.py (1 hunks)
• .github/workflows/scripts/talawa_admin_md_mdx_format_adjuster.py (1 hunks)
• .github/workflows/scripts/validate-coderabbit.sh (1 hunks)
• .github/workflows/stale.yml (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)
• Dockerfile (1 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)
• docs/.gitignore (1 hunks)
• docs/CNAME (1 hunks)
• docs/README.md (1 hunks)
• docs/docs/intro.md (1 hunks)
• docs/docs/tutorial-basics/_category_.json (1 hunks)
• docs/docs/tutorial-basics/congratulations.md (1 hunks)
• docs/docs/tutorial-basics/create-a-blog-post.md (1 hunks)
• docs/docs/tutorial-basics/create-a-document.md (1 hunks)
• docs/docs/tutorial-basics/create-a-page.md (1 hunks)
• docs/docs/tutorial-basics/deploy-your-site.md (1 hunks)
• docs/docs/tutorial-basics/markdown-features.mdx (1 hunks)
• docs/docs/tutorial-extras/_category_.json (1 hunks)
• docs/docs/tutorial-extras/manage-docs-versions.md (1 hunks)
• docs/docs/tutorial-extras/translate-your-site.md (1 hunks)
• docs/docusaurus.config.ts (1 hunks)
• docs/package.json (1 hunks)
• docs/sidebars.ts (1 hunks)
• docs/src/components/HomepageFeatures/index.tsx (1 hunks)
• docs/src/components/HomepageFeatures/styles.module.css (1 hunks)
• docs/src/css/custom.css (1 hunks)
• docs/src/pages/index.module.css (1 hunks)
• docs/src/pages/index.tsx (1 hunks)
• docs/src/pages/markdown-page.md (1 hunks)
• docs/static/CNAME (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)

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

• scripts/mocks/@pdfme/generator.ts
• scripts/mocks/fileMock.js
• scripts/custom-test-env.js
• scripts/githooks/check-localstorage-usage.js
• scripts/githooks/update-toc.js
• setup.ts
• src/App.spec.tsx
• 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

💤 Files with no reviewable changes (13)

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

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

• .node-version
• docs/static/CNAME
• docs/CNAME
• docs/docs/tutorial-extras/category.json
• .dockerignore
• jest-preview.config.ts
• .eslintignore
• .github/workflows/auto-label.json5
• CODEOWNERS
• docs/docs/tutorial-basics/category.json
• config/babel.config.cjs
• public/locales/fr/common.json
• .github/dependabot.yaml
• docs/src/components/HomepageFeatures/styles.module.css
• .prettierignore
• .lintstagedrc.json
• index.html
• public/locales/fr/translation.json
• public/locales/en/translation.json
• .prettierrc
• docs/.gitignore
• public/locales/zh/translation.json
• docs/src/pages/index.module.css
• .env.example
• public/locales/sp/common.json
• public/locales/en/common.json

🧰 Additional context used

🪛 LanguageTool

docs/docs/intro.md

[style] ~43-~43: Consider a shorter alternative to avoid wordiness.
Context: ...nges the directory you're working with. In order to work with your newly created Docusaurus...

(IN_ORDER_TO_PREMIUM)

CODE_OF_CONDUCT.md

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

(ENGLISH_WORD_REPEAT_RULE)

docs/docs/tutorial-basics/markdown-features.mdx

[style] ~98-~98: Consider using a more formal and expressive alternative to ‘awesome’.
Context: ...erous ::: ``` :::tip My tip Use this awesome feature option ::: :::danger Take car...

(AWESOME)

docs/docs/tutorial-basics/deploy-your-site.md

[style] ~31-~31: As an alternative to the over-used intensifier ‘very’, consider replacing this phrase.
Context: ...most anywhere** easily, for free or very small cost (read the **[Deployment Guide](htt...

(EN_WEAK_ADJECTIVE)

docs/docs/tutorial-basics/congratulations.md

[style] ~7-~7: Consider rephrasing this to strengthen your wording.
Context: ...earned the basics of Docusaurus and made some changes to the initial template. Docusauru...

(MAKE_CHANGES)

---

[style] ~13-~13: Using many exclamation marks might seem excessive (in this case: 3 exclamation marks for a text that’s 654 characters long)
Context: ...gy** in this tutorial? [Please report it!](https://github.com/facebook/docusaurus...

(EN_EXCESSIVE_EXCLAMATION)

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)

.github/workflows/README.md

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

(AI_HYDRA_LEO_MISSING_COMMA)

---

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

(ENGLISH_WORD_REPEAT_RULE)

---

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

(E_G)

INSTALLATION.md

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

(AI_HYDRA_LEO_MISSING_COMMA)

---

[typographical] ~39-~39: 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] ~45-~45: 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] ~51-~51: 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] ~52-~52: 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] ~54-~54: 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] ~86-~86: 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] ~100-~100: 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] ~103-~103: 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] ~107-~107: 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] ~114-~114: Possible missing comma found.
Context: ...stall TypeScript, you can use the npm command which comes with node.js: ```bash np...

(AI_HYDRA_LEO_MISSING_COMMA)

docs/README.md

[uncategorized] ~34-~34: Possible missing comma found.
Context: ...ckage installation, use only the yarn package as npm will throw an error. Only `npm...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[uncategorized] ~34-~34: Possible missing article found.
Context: ...package asnpmwill throw an error. Onlynpm` use case here would be to install...

(AI_HYDRA_LEO_MISSING_THE)

---

[grammar] ~46-~46: Possible subject-verb agreement error.
Context: ...v) is required. Other requirements that pertains to the installation of docusaurus can b...

(NNS_THAT_AGREEMENT)

---

[style] ~59-~59: Try using a synonym here to strengthen your writing.
Context: ...the path, double-click to install. Then give access to run the application 1. Instal...

(GIVE_PROVIDE)

---

[style] ~77-~77: Try using a synonym here to strengthen your writing.
Context: ...the path, double-click to install. Then give access to run the application 1. Check...

(GIVE_PROVIDE)

---

[grammar] ~112-~112: The expression “One of the” requires a plural noun.
Context: ...acOS Using Homebrew One of the easiest way to install Yarn on macOS is to use the ...

(ONE_OF_THE_MOST)

---

[uncategorized] ~124-~124: Possible missing comma found.
Context: ...nd in your terminal to install Node and NPM respectively. [Confirm your Linux distr...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[grammar] ~124-~124: Did you mean to use the possessive pronoun “its”?
Context: ...ctively. [Confirm your Linux distro and it's command prompt](https://classic.yarnpkg...

(IT_S_ITS)

---

[uncategorized] ~152-~152: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...ment server that will serve your website and it will reflect the latest changes. Th...

(COMMA_COMPOUND_SENTENCE)

---

[formatting] ~168-~168: Insert a comma after ‘cases’: “In most cases,”?
Context: ...erver. # Building Static HTML Pages In most cases is unnecessary. Running the `developm...

(IN_MOST_CASES_COMMA)

CONTRIBUTING.md

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

(INSERT_PLEASE)

---

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

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

(THE_SUPERLATIVE)

---

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

(UNLIKELY_OPENING_PUNCTUATION)

---

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

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

(IF_THERE_COMMA)

---

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

(RB_LY_COMMA)

---

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

(FIRST_SERVED)

---

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

(ON_SKYPE)

---

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

(EN_WORDINESS_PREMIUM_LAST_BUT_NOT_THE_LEAST)

---

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

(MISSING_TO_BETWEEN_BE_AND_VB)

---

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

(ON_SKYPE)

---

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

(EN_A_VS_AN)

---

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

(DURING_THAT_TIME_COMMA)

---

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

(MAC_OS)

---

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

(BE_VBP_IN)

---

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

(ON_SKYPE)

PR_GUIDELINES.md

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

(UNLIKELY_OPENING_PUNCTUATION)

---

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

(IN_ORDER_TO_PREMIUM)

---

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

(SPLIT_INFINITIVE)

---

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

(EN_WEAK_ADJECTIVE)

---

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

(SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)

---

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

(FIX_RESOLVE)

---

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

(SOONER_OR_LATER)

---

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

(COMMA_COMPOUND_SENTENCE)

---

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

(MAKE_CHANGES)

README.md

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

ISSUE_GUIDELINES.md

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

(UNLIKELY_OPENING_PUNCTUATION)

---

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

(IN_ORDER_TO_PREMIUM)

---

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

(EN_A_VS_AN)

---

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

(PLEASE_COMMA)

---

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

(FIX_RESOLVE)

---

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

(AI_HYDRA_LEO_MISSING_TO)

---

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

(MAKE_STYLE_BETTER)

---

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

(ON_SKYPE)

---

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

(ON_SKYPE)

---

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

(ON_SKYPE)

---

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

(PLEASE_COMMA)

CODE_STYLE.md

[style] ~127-~127: Consider removing “of” to be more concise
Context: ...tories of src assets - This houses all of the static assets used in the project - `...

(ALL_OF_THE)

---

[style] ~128-~128: Consider removing “of” to be more concise
Context: ... in the project - css - This houses all of the css files used in the project - `imag...

(ALL_OF_THE)

---

[style] ~129-~129: Consider removing “of” to be more concise
Context: ... the project - images - This houses all of the images used in the project - scss -...

(ALL_OF_THE)

---

[style] ~130-~130: Consider removing “of” to be more concise
Context: ...in the project - scss - This houses all of the scss files used in the project - `c...

(ALL_OF_THE)

---

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

docs/docs/tutorial-extras/manage-docs-versions.md

[duplication] ~54-~54: Possible typo: you repeated a word.
Context: ...- versioned_docs/version-1.0/hello.md updates http://localhost:3000/docs/hello - docs/hello.md updates http://localhost:3000/docs/next/hello...

(ENGLISH_WORD_REPEAT_RULE)

docs/src/pages/markdown-page.md

[grammar] ~7-~7: Did you mean “to React”?
Context: ...# Markdown page example You don't need React to write simple standalone pages.

(NEEDNT_TO_DO_AND_DONT_NEED_DO)

🪛 markdownlint-cli2 (0.17.2)

DOCUMENTATION.md

25-25: Bare URL used
null

(MD034, no-bare-urls)

INSTALLATION.md

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

(MD014, commands-show-output)

---

89-89: Bare URL used
null

(MD034, no-bare-urls)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

208-208: Bare URL used
null

(MD034, no-bare-urls)

---

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

(MD040, fenced-code-language)

---

216-216: Bare URL used
null

(MD034, no-bare-urls)

---

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

(MD040, fenced-code-language)

---

224-224: Bare URL used
null

(MD034, no-bare-urls)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

300-300: Bare URL used
null

(MD034, no-bare-urls)

---

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

(MD040, fenced-code-language)

---

308-308: Bare URL used
null

(MD034, no-bare-urls)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

docs/README.md

13-13: Link fragments should be valid
null

(MD051, link-fragments)

---

16-16: Link fragments should be valid
null

(MD051, link-fragments)

---

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

(MD014, commands-show-output)

---

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

(MD014, commands-show-output)

---

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

(MD014, commands-show-output)

---

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

(MD014, commands-show-output)

---

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

(MD014, commands-show-output)

---

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

(MD014, commands-show-output)

---

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

(MD014, commands-show-output)

---

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

(MD014, commands-show-output)

---

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

(MD014, commands-show-output)

---

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

(MD014, commands-show-output)

---

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

(MD014, commands-show-output)

---

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

(MD014, commands-show-output)

---

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

(MD014, commands-show-output)

---

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

(MD014, commands-show-output)

---

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

(MD014, commands-show-output)

---

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

(MD014, commands-show-output)

---

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

(MD014, commands-show-output)

---

162-162: Bare URL used
null

(MD034, no-bare-urls)

---

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

(MD014, commands-show-output)

CONTRIBUTING.md

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

158-158: No empty links
null

(MD042, no-empty-links)

---

159-159: No empty links
null

(MD042, no-empty-links)

---

161-161: No empty links
null

(MD042, no-empty-links)

CODE_STYLE.md

57-57: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

73-73: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)

---

75-75: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)

---

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

(MD040, fenced-code-language)

---

92-92: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)

---

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

(MD040, fenced-code-language)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD040, fenced-code-language)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

190-190: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)

---

230-230: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

🪛 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] 33-33: trailing spaces

(trailing-spaces)

---

[error] 35-35: trailing spaces

(trailing-spaces)

---

[error] 40-40: trailing spaces

(trailing-spaces)

---

[error] 45-45: trailing spaces

(trailing-spaces)

---

[error] 70-70: trailing spaces

(trailing-spaces)

.github/workflows/merge-conflict-check.yml

[error] 46-46: 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/stale.yml

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 20-20: trailing spaces

(trailing-spaces)

---

[error] 21-21: trailing spaces

(trailing-spaces)

---

[error] 24-24: trailing spaces

(trailing-spaces)

.github/workflows/push-deploy-website.yml

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 17-17: trailing spaces

(trailing-spaces)

---

[error] 18-18: trailing spaces

(trailing-spaces)

---

[error] 21-21: trailing spaces

(trailing-spaces)

---

[error] 29-29: trailing spaces

(trailing-spaces)

---

[error] 33-33: trailing spaces

(trailing-spaces)

---

[error] 57-57: 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)

.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] 93-93: trailing spaces

(trailing-spaces)

---

[error] 107-107: trailing spaces

(trailing-spaces)

---

[error] 143-143: trailing spaces

(trailing-spaces)

---

[error] 146-146: trailing spaces

(trailing-spaces)

---

[error] 152-152: trailing spaces

(trailing-spaces)

---

[error] 168-168: trailing spaces

(trailing-spaces)

---

[error] 175-175: trailing spaces

(trailing-spaces)

---

[error] 222-222: trailing spaces

(trailing-spaces)

---

[warning] 227-227: too few spaces after comma

(commas)

---

[error] 239-239: trailing spaces

(trailing-spaces)

---

[error] 243-243: trailing spaces

(trailing-spaces)

---

[error] 265-265: trailing spaces

(trailing-spaces)

---

[error] 266-266: trailing spaces

(trailing-spaces)

---

[error] 306-306: trailing spaces

(trailing-spaces)

---

[error] 312-312: trailing spaces

(trailing-spaces)

---

[error] 314-314: trailing spaces

(trailing-spaces)

---

[error] 318-318: trailing spaces

(trailing-spaces)

---

[error] 407-407: trailing spaces

(trailing-spaces)

.github/workflows/issue.yml

[error] 6-6: trailing spaces

(trailing-spaces)

---

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

(indentation)

---

[warning] 66-66: too many blank lines

(1 > 0) (empty-lines)

🪛 Ruff (0.8.2)

.github/workflows/scripts/eslint_disable_check.py

76-77: Use a single if statement instead of nested if statements

(SIM102)

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

.github/workflows/scripts/code_coverage_disable_check.py

95-105: Use a single if statement instead of nested if statements

(SIM102)

---

97-105: Use a single if statement instead of nested if statements

(SIM102)

🪛 actionlint (1.7.4)

.github/workflows/pull-request.yml

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)

---

280-280: input "gcov_ignore" is not defined in action "codecov/codecov-action@v4". available inputs are "codecov_yml_path", "commit_parent", "directory", "disable_file_fixes", "disable_safe_directory", "disable_search", "dry_run", "env_vars", "exclude", "fail_ci_if_error", "file", "files", "flags", "git_service", "handle_no_reports_found", "job_code", "name", "network_filter", "network_prefix", "os", "override_branch", "override_build", "override_build_url", "override_commit", "override_pr", "plugin", "plugins", "report_code", "root_dir", "slug", "token", "url", "use_legacy_upload_endpoint", "use_oidc", "verbose", "version", "working-directory"

(action)

---

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

(shellcheck)

---

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

(shellcheck)

🔇 Additional comments (49)

docs/docs/tutorial-basics/markdown-features.mdx (6)

1-8: LGTM!

The front matter is well-structured, and the introduction provides a clear overview with proper external links.

---

28-41: LGTM!

The Links section effectively demonstrates both URL paths and relative file paths with clear examples.

---

42-59: LGTM!

The Images section effectively demonstrates both absolute and relative image paths with clear examples and proper explanations.

---

60-77: LGTM!

The Code Blocks section effectively demonstrates syntax highlighting with proper examples and rendered output.

---

108-153: LGTM!

The MDX and React Components section effectively demonstrates component integration with a well-implemented interactive example.

---

1-153: Verify alignment with PR objectives.

This documentation file appears to be part of a larger documentation update, but the PR objectives specifically mention fixing language switch functionality. Please clarify if this documentation change is related to the language switch fix or if it should be in a separate PR.

🧰 Tools

🪛 LanguageTool

[style] ~98-~98: Consider using a more formal and expressive alternative to ‘awesome’.
Context: ...erous ::: ``` :::tip My tip Use this awesome feature option ::: :::danger Take car...

(AWESOME)

docs/sidebars.ts (5)

1-4: LGTM! Clean type import and clear comment.

The import statement correctly uses TypeScript's type import syntax, and the comment clearly indicates the Node.js runtime context.

---

5-14: LGTM! Well-documented configuration options.

The JSDoc comments effectively explain the purpose and capabilities of the sidebar configuration.

---

33-34: LGTM! Clean default export.

The export statement follows TypeScript best practices.

---

1-34: Verify alignment with PR objectives.

This file introduces Docusaurus sidebar configuration, which seems unrelated to the PR's stated objective of fixing language switching functionality. Please clarify if this documentation update is intentionally included in this PR or if it should be moved to a separate PR focused on documentation improvements.

Likely an incorrect or invalid review comment.

---

15-31: LGTM! Type-safe configuration with helpful examples.

The sidebar configuration is properly typed with SidebarsConfig and uses the recommended auto-generation approach. The commented example provides valuable guidance for manual configuration.

Let's verify that the docs directory structure exists and is properly organized:

✅ Verification successful

🏁 Script executed:

#!/bin/bash
# Description: Verify docs directory structure for sidebar auto-generation

# Check if docs directory exists and contains markdown files
echo "Checking docs directory structure..."
fd -e md . docs/

# Check if there's an intro/index document (common in Docusaurus)
echo -e "\nChecking for intro document..."
fd -g 'intro.md|index.md' docs/

Length of output: 606

---

Docs directory structure verified and organized as expected.
The auto-generated sidebar in docs/sidebars.ts references the correct docs directory (evidenced by the presence of markdown files such as docs/docs/intro.md and others). Although the search for an "intro" file using the pattern 'intro.md|index.md' returned no output (likely due to pattern interpretation as a glob rather than a regex), the required documentation files do exist in the expected locations.

.gitignore (4)

13-14: LGTM! Good practice for test artifacts.

Correctly ignores test coverage reports and CodeCov artifacts which should not be version controlled.

---

21-21: LGTM! Good security practice.

Correctly prevents accidental commit of sensitive environment variables.

---

31-32: LGTM! Appropriate for debug logs.

Correctly ignores Express debug logs which should not be version controlled.

---

34-37: LGTM! Standard practice for editor files.

Correctly ignores editor-specific files and configurations that should remain local to each developer's environment.

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

1-98: LGTM! Comprehensive localization coverage.

The localization files provide good coverage for the UI elements with appropriate translations. The structure is consistent, and placeholders are properly used for dynamic content (except for the noted issues above).

To ensure all required translations are present, run this script to compare keys between language files:

✅ Verification successful

🏁 Script executed:

#!/bin/bash
# Description: Compare keys between language files to ensure consistency

# Function to extract keys from JSON file
extract_keys() {
    python3 -c "
import json
with open('$1') as f:
    data = json.load(f)
print('\n'.join(sorted(data.keys())))
" > /tmp/keys_$2.txt
}

# Extract keys from all language files
for lang in en hi zh sp; do
    if [ -f "public/locales/${lang}/common.json" ]; then
        extract_keys "public/locales/${lang}/common.json" ${lang}
    fi
done

# Compare keys between files
for lang1 in en hi zh sp; do
    for lang2 in en hi zh sp; do
        if [ "$lang1" != "$lang2" ] && [ -f "/tmp/keys_${lang1}.txt" ] && [ -f "/tmp/keys_${lang2}.txt" ]; then
            echo "Comparing ${lang1} with ${lang2}:"
            diff "/tmp/keys_${lang1}.txt" "/tmp/keys_${lang2}.txt" || true
            echo "---"
        fi
    done
done

Length of output: 3979

---

Localization Keys Are Consistent Across Language Files
The script output shows no differences in the keys between the Hindi file and the other language files (en, zh, sp), confirming that the Hindi localization file has full key coverage and is in sync with its counterparts.

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

1-1: LGTM! Mock implementation is correct.

The mock function is properly implemented using jest.fn(). However, this change appears unrelated to the PR's objective of fixing language switching functionality.

Likely an incorrect or invalid review comment.

.husky/post-merge (1)

1-4: LGTM! Post-merge hook is well implemented.

The script correctly:

1. Uses proper shebang
2. Sources husky.sh
3. Efficiently checks for package.json changes and runs npm install when needed

However, this change appears unrelated to the PR's objective of fixing language switching functionality.

Likely an incorrect or invalid review comment.

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

1-5: LGTM! Mock implementation is correct.

The mock function correctly:

1. Implements createAvatar using jest.fn()
2. Returns an object with toDataUri mock
3. Provides a consistent mock response

However, this change appears unrelated to the PR's objective of fixing language switching functionality.

Likely an incorrect or invalid review comment.

.husky/pre-commit (1)

1-8: Note: Changes unrelated to PR objective.

While the pre-commit hook implementation is generally good, these changes appear unrelated to the PR's objective of fixing language switching functionality.

Likely an incorrect or invalid review comment.

config/vite.config.ts (1)

7-31: LGTM! Well-structured Vite configuration.

The configuration is well-organized and includes all necessary plugins for React development. The use of TypeScript paths, SVG handling, and environment variables demonstrates good practices.

docs/src/pages/index.tsx (1)

10-22: LGTM! Clean and well-structured header component.

The HomepageHeader component follows React best practices with proper hook usage and TypeScript implementation.

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

21-46: LGTM! Comprehensive error handling tests.

The error handling tests are well-structured and cover important edge cases with proper async/await usage.

.coderabbit.yaml (1)

1-19: LGTM!

The configuration follows the schema correctly and enables essential features for code reviews.

public/manifest.json (1)

16-16: Verify the icon path.

The icon path has been updated to include the "images" directory. Please ensure that the file exists at this location.

✅ Verification successful

🏁 Script executed:

#!/bin/bash
# Description: Verify that the icon file exists at the specified path.

# Test: Check if the file exists
fd -t f "logo512.png" public/images/

Length of output: 62

---

Icon file path verified.
The file "logo512.png" exists under the "public/images" directory as expected. No changes are required.

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

1-16: LGTM!

The error messages are properly formatted and use consistent placeholders for dynamic content.

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

2-7: LGTM!

The changes improve consistency with other templates and add helpful information for internship candidates.

Also applies to: 25-28

docs/docs/tutorial-basics/create-a-blog-post.md (1)

1-35: LGTM! Well-structured tutorial with clear examples.

The tutorial provides comprehensive guidance for creating blog posts with proper metadata and formatting.

docs/docs/tutorial-basics/create-a-page.md (1)

1-44: LGTM! Clear and comprehensive tutorial.

The tutorial effectively explains page creation with both React and Markdown, providing clear examples and proper file structure guidance.

docs/docs/tutorial-basics/create-a-document.md (1)

1-58: LGTM! Well-structured document creation guide.

The tutorial provides comprehensive guidance for creating and configuring documents, including sidebar customization and metadata usage.

docs/docs/tutorial-extras/manage-docs-versions.md (1)

1-56: Documentation looks good!

The documentation is well-structured and provides clear instructions for managing documentation versions in Docusaurus.

🧰 Tools

🪛 LanguageTool

[duplication] ~54-~54: Possible typo: you repeated a word.
Context: ...- versioned_docs/version-1.0/hello.md updates http://localhost:3000/docs/hello - docs/hello.md updates http://localhost:3000/docs/next/hello...

(ENGLISH_WORD_REPEAT_RULE)

docs/docs/intro.md (1)

1-48: Documentation looks good!

The tutorial introduction is clear, concise, and provides all necessary information for getting started with Docusaurus.

🧰 Tools

🪛 LanguageTool

[style] ~43-~43: Consider a shorter alternative to avoid wordiness.
Context: ...nges the directory you're working with. In order to work with your newly created Docusaurus...

(IN_ORDER_TO_PREMIUM)

docs/docs/tutorial-extras/translate-your-site.md (1)

1-89: Well-structured translation tutorial!

The tutorial provides clear, step-by-step instructions for site translation with appropriate code examples and cautions.

.github/workflows/stale.yml (1)

29-42: Well-configured stale issue management!

The configuration provides reasonable timeframes and clear messages for managing stale issues and PRs. The exemption for WIP items and milestone-tagged items is a good practice.

.github/workflows/merge-conflict-check.yml (1)

24-65: Excellent implementation of merge conflict detection!

The implementation includes:

• Proper error handling with retries
• Rate limit handling
• Clear status messages
• Appropriate exit codes

🧰 Tools

🪛 YAMLlint (1.35.1)

[error] 46-46: trailing spaces

(trailing-spaces)

.github/workflows/push.yml (1)

42-49: LGTM! Well-configured caching strategy.

The cache configuration is well-structured with:

• Appropriate cache key based on package-lock.json
• Fallback restore-keys for partial matches
• Proper path configuration for npm cache

.github/pull_request_template.md (1)

47-56: LGTM! Well-structured checklist for quality assurance.

The checklist effectively covers:

• CodeRabbit AI review requirements
• Test coverage expectations
• Local test verification

.eslintrc.json (1)

1-157: LGTM! Comprehensive ESLint configuration.

The updated ESLint configuration provides excellent TypeScript support with strict type checking and naming conventions. The addition of Prettier and import plugins will help maintain consistent code style.

CODE_OF_CONDUCT.md (1)

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

The addition of a table of contents with proper HTML comments and section links improves document navigation.

🧰 Tools

🪛 LanguageTool

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

(ENGLISH_WORD_REPEAT_RULE)

package.json (2)

2-3: Verify the major version upgrade.

The version jump from 0.1.0 to 3.0.0 is significant. Please ensure this aligns with semantic versioning principles and that all breaking changes are documented.

---

170-172: Consider Node.js version requirement impact.

Requiring Node.js >=20.x might be too restrictive for some users. Consider if supporting Node.js 18.x LTS is feasible.

✅ Verification successful

🌐 Web query:

What is the current LTS version of Node.js and its end-of-life date?

💡 Result:

The current Long-Term Support (LTS) version of Node.js is v22.x, which entered Active LTS status on October 29, 2024[4][6]. Its end-of-life (EOL) date is April 30, 2027[1][5].

Key Details:

• Active LTS Phase: Runs until October 2025[4][6]
• Maintenance LTS Phase: Extends from October 2025 until final EOL in April 2027[1][4]
• Support Timeline:
  • Security updates guaranteed through April 2027
  • Critical bug fixes until Maintenance phase ends[4][7]

Context for Other Versions:

• Node.js v20.x (previous LTS) entered Maintenance LTS on September 11, 2023[1], with EOL scheduled for April 30, 2026[1][5]
• Node.js v18.x reaches EOL on April 30, 2025[1][10], aligning with Azure SDK's deprecation plans[10]

Production environments should prioritize v22.x for extended support and security coverage through April 2027[1][4][7].

Citations:

• 1: https://www.herodevs.com/blog-posts/node-js-end-of-life-dates-you-should-be-aware-of
• 2: https://www.nearform.com/digital-community/node-js-release-schedule-explained/
• 3: https://dev.to/igahsamuel/nodejs-understanding-the-difference-between-current-and-lts-versions-2dek
• 4: https://nodesource.com/blog/Node.js-v22-Long-Term-Support-LTS
• 5: https://endoflife.software/programming-languages/server-side-scripting/nodejs
• 6: https://nodejs.org/en/blog/release/v22.11.0
• 7: https://nodejs.org/en/about/previous-releases
• 8: https://nodejs.org/en/blog/announcements/nodejs16-eol
• 9: https://nodejs.org/en/blog/announcements/v22-release-announce
• 10: https://devblogs.microsoft.com/azure-sdk/announcing-the-end-of-support-for-node-js-18-x-in-the-azure-sdk-for-javascript/

---

Node.js Engine Requirement is Appropriate

Based on the latest Node.js LTS timeline:

• Node.js v18.x reaches end-of-life on April 30, 2025.
• Node.js v20.x remains supported until April 30, 2026, and the current active LTS is v22.x.

Requiring Node.js ">=20.x" ensures users run a version with extended support and better security, making it reasonable not to support v18.x.

docs/README.md (1)

1-8: Excellent documentation structure!

The introduction and installation overview are clear and well-organized.

CODE_STYLE.md (1)

1-8: Comprehensive code style guide!

The introduction clearly states the purpose and importance of following the code style.

docs/src/css/custom.css (1)

8-47: Well-organized CSS variables!

The root variables are clearly defined and follow a consistent naming pattern.

CONTRIBUTING.md (1)

1-180: LGTM! Well-structured contribution guidelines.

The document provides comprehensive guidance for contributors, including clear sections on code of conduct, getting started resources, and contribution processes.

🧰 Tools

🪛 LanguageTool

[uncategorized] ~5-~5: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ibuting to open source, please read the Open Source Guides on [How to Contribute to Open So...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

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

🪛 markdownlint-cli2 (0.17.2)

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

158-158: No empty links
null

(MD042, no-empty-links)

---

159-159: No empty links
null

(MD042, no-empty-links)

---

161-161: No empty links
null

(MD042, no-empty-links)

INSTALLATION.md (1)

1-383: LGTM! Comprehensive installation guide.

The document provides clear, step-by-step instructions for setting up the project, including both development and Docker-based installations. The guide is well-structured with detailed sections for prerequisites, configuration, and testing.

🧰 Tools

🪛 LanguageTool

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

(AI_HYDRA_LEO_MISSING_COMMA)

---

[typographical] ~39-~39: 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] ~45-~45: 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] ~51-~51: 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] ~52-~52: 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] ~54-~54: 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] ~86-~86: 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] ~100-~100: 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] ~103-~103: 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] ~107-~107: 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] ~114-~114: Possible missing comma found.
Context: ...stall TypeScript, you can use the npm command which comes with node.js: ```bash np...

(AI_HYDRA_LEO_MISSING_COMMA)

🪛 markdownlint-cli2 (0.17.2)

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

(MD014, commands-show-output)

---

89-89: Bare URL used
null

(MD034, no-bare-urls)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

208-208: Bare URL used
null

(MD034, no-bare-urls)

---

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

(MD040, fenced-code-language)

---

216-216: Bare URL used
null

(MD034, no-bare-urls)

---

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

(MD040, fenced-code-language)

---

224-224: Bare URL used
null

(MD034, no-bare-urls)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

300-300: Bare URL used
null

(MD034, no-bare-urls)

---

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

(MD040, fenced-code-language)

---

308-308: Bare URL used
null

(MD034, no-bare-urls)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

schema.graphql (1)

1-1537: Verify PR scope and objectives.

The changes in this PR appear to be much broader than the stated objective of fixing the language switch issue. While the documentation and configuration updates are well-done, please clarify how they relate to the language switch fix.

Could you explain:

1. How these changes address the language switch issue?
2. Why such extensive documentation and schema changes are needed for this fix?

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

1-1510: LGTM! The translation file is well-structured and comprehensive.

The Hindi translations are properly formatted and cover all necessary UI elements. The translations maintain cultural sensitivity and use appropriate formal Hindi that would be well-received by users.

docs/src/pages/markdown-page.md (1)

1-8: LGTM!

The markdown file is well-structured with proper front matter and clear content. The sentence is grammatically correct and effectively conveys the message about standalone pages.

🧰 Tools

🪛 LanguageTool

[grammar] ~7-~7: Did you mean “to React”?
Context: ...# Markdown page example You don't need React to write simple standalone pages.

(NEEDNT_TO_DO_AND_DONT_NEED_DO)

[coderabbitai]

Actionable comments posted: 4

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c831c4d and 08688b6.

📒 Files selected for processing (2)

• public/locales/hi/translation.json (1 hunks)
• public/locales/sp/translation.json (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• public/locales/hi/translation.json

🔇 Additional comments (1)

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

1-1513: Overall assessment of the Spanish translation file.

The translation file is well-structured and comprehensive, but there are a few issues that need attention:

1. Organization name should not be translated
2. Some case-check translations are swapped
3. Missing chat-related translations
4. French text in Spanish translations

Despite these issues, the translations are generally accurate and culturally appropriate.

[coderabbitai]

⚠️ Potential issue

Add missing translations for chat creation.

The "createChat" key appears twice with missing translations.

-    "createChat": "Crear chat"
+    "createChat": "Crear conversación"

Also applies to: 584-584

[coderabbitai]

⚠️ Potential issue

Correct swapped translations for case checks.

The translations for lowercase and uppercase checks are reversed.

-    "lowercase_check": "Al menos una letra mayuscula",
-    "uppercase_check": "Al menos una letra minúscula",
+    "lowercase_check": "Al menos una letra minúscula",
+    "uppercase_check": "Al menos una letra mayúscula",

📝 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

	"lowercase_check": "Al menos una letra mayuscula",
	"uppercase_check": "Al menos una letra minúscula",
	"lowercase_check": "Al menos una letra minúscula",
	"uppercase_check": "Al menos una letra mayuscula",

[coderabbitai]

⚠️ Potential issue

Fix organization name in translation.

The organization name "palisados" should not be translated as it's a proper noun.

-    "fromPalisadoes": "Una aplicación de código abierto de los voluntarios de la Fundación palisados",
+    "fromPalisadoes": "Una aplicación de código abierto de los voluntarios de la Fundación Palisadoes",

📝 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

	"fromPalisadoes": "Una aplicación de código abierto de los voluntarios de la Fundación palisados",
	"fromPalisadoes": "Una aplicación de código abierto de los voluntarios de la Fundación Palisadoes",

[palisadoes]

1. Closing. You have submitted one 1000 files to review.
2. We are working on the develop-postgres branch until further notice