Origin/2503

[gurramkarthiknetha]

What kind of change does this PR introduce?

Issue Number:

Fixes #2503

Did you add tests for your changes?

Snapshots/Videos:

If relevant, did you update the documentation?

Summary

This PR refactors the CSS files in src/screens/CommunityProfile and related components to follow the new global CSS design pattern introduced in the project. Specifically:

• Merged all the CSS files from the subdirectory and related components into a single global CSS file (src/style/app.module.css).
• Deleted all the old, now redundant CSS files in the subdirectory and related components.
• Ensured that all remaining relevant files reference only the global CSS file.
• Followed accessibility guidelines to improve the app's usability for colorblind users.

This work builds on the foundational changes made in PR #2466 (Chore/css changes).

Does this PR introduce a breaking change?

Other information

Have you read the contributing guide?

Summary by CodeRabbit

Release Notes

• New Features

  • Introduced a new configuration file for YAML language server settings, including options for reviews and auto-review features.
  • Added a new .env.example file as a template for environment variables required for the Talawa-admin installation setup.
  • Implemented a comprehensive GitHub Actions workflow for managing pull requests, integrating multiple quality checks and validations.
  • Added localization support with new JSON files for English, French, Hindi, Spanish, and Chinese, enhancing accessibility for users.

• Bug Fixes

  • Enhanced error handling and validation in various scripts and workflows.

• Chores

  • Updated documentation files, including installation and contribution guidelines, to improve clarity and usability.
  • Introduced scripts for automated checks and updates, such as local storage usage and table of contents management.

• Style

  • Improved the structure and organization of the README and other documentation files, including a new Table of Contents for easier navigation.

[coderabbitai]

Walkthrough

The changes introduce several new configuration files and scripts aimed at enhancing the Talawa Admin project's development and deployment processes. Key additions include a .coderabbit.yaml for YAML language server settings, a .env.example for environment variable templates, and various GitHub Actions workflows for CI/CD, testing, and issue management. Additionally, several localization JSON files for multiple languages have been added to support internationalization. The project structure has been refined to improve code quality, testing, and user experience.

Changes

File Path	Change Summary
.coderabbit.yaml	New configuration file for YAML language server settings.
.env.example	New template for environment variables required for application setup.
.eslintignore	Added exclusion for src/components/CheckIn/tagTemplate.ts from linting.
.eslintrc.json	Updated ESLint configuration with new plugins, rules, and environment settings.
.github/ISSUE_TEMPLATE/bug-report.md	Updated metadata fields and added sections for additional details and internship candidates.
.github/ISSUE_TEMPLATE/feature-request.md	Updated metadata fields and added a section for internship candidates.
.github/dependabot.yaml	New configuration file for automated dependency updates.
.github/pull_request_template.md	Modified to include branching strategy and additional prompts for contributors.
.github/workflows/README.md	New guidelines for managing workflow files and scripts.
.github/workflows/auto-label.json5	New configuration for label synonyms and default labels in workflows.
.github/workflows/check-tsdoc.js	New script to validate TypeScript files for TSDoc comments.
.github/workflows/ci.yml	Removed Continuous Integration workflow.
.github/workflows/codeql-analysis.yml	Removed CodeQL analysis workflow.
.github/workflows/codeql-codescan.yml	New workflow for automating CodeQL code analysis.
.github/workflows/compare_translations.py	New utility script for comparing translation files.
.github/workflows/countline.py	New script to analyze code lines in specified directories.
.github/workflows/eslint_disable_check.py	New script to check for eslint-disable statements in TypeScript files.
.github/workflows/issue.yml	Updated workflow for issue auto-labeling and greeting new users.
.github/workflows/linter.yml	Removed linter workflow.
.github/workflows/npm-publish.yml	Removed npm publish workflow.
.github/workflows/pull-request-target.yml	New workflow for managing pull requests with greetings and review policies.
.github/workflows/pull-request.yml	New comprehensive workflow for managing pull requests with various checks.
.github/workflows/push.yml	New CI/CD pipeline triggered on push events.
.github/workflows/stale.yml	New workflow for managing stale issues and pull requests.
.github/workflows/talawa_admin_md_mdx_format_adjuster.py	New script for formatting Markdown files for MDX compatibility.
.gitignore	Updated to ignore additional files and directories.
.husky/post-merge	New script to run npm install if package.json changes are detected.
.husky/pre-commit	Added commands for formatting, linting, and type checking before commits.
.lintstagedrc.json	New configuration for linting and formatting tasks on staged files.
.node-version	New specification for Node.js version 22.7.0.
.prettierignore	Updated to ignore specific directories and files.
.prettierrc	Added property for handling line endings in Prettier configuration.
CODEOWNERS	New file to designate code owners for the repository.
CODE_OF_CONDUCT.md	Added Table of Contents for improved navigation.
CODE_STYLE.md	New comprehensive code style guide for contributors.
CONTRIBUTING.md	Updated structure and content for clarity and organization.
DOCUMENTATION.md	New guide for accessing and utilizing project documentation.
Docker_Container/.dockerignore	Removed file specifying ignored paths for Docker builds.
Docker_Container/README.md	Removed setup instructions for Docker container.
Docker_Container/docker-compose.yml	Removed Docker Compose configuration for service named sample.
Docker_Container/dockerfile	Removed Dockerfile for Node.js application setup.
INSTALLATION.md	New document providing setup instructions for the application.
ISSUE_GUIDELINES.md	New document standardizing issue reporting process.
ISSUE_TEMPLATE.md	Removed issue reporting template.
PR-guidelines.md	Removed guidelines for pull requests.
PR_GUIDELINES.md	New comprehensive guidelines for submitting pull requests.
PULL_REQUEST_TEMPLATE.md	Removed pull request template.
README.md	Enhanced structure and content for community engagement and documentation clarity.
config/babel.config.cjs	New Babel configuration for JavaScript compilation.
config/vite.config.ts	New Vite configuration for building React applications.
index.html	New HTML file defining the structure of the web page.
schema.graphql	New comprehensive GraphQL schema with various types and directives.
scripts/__mocks__/@dicebear/collection.ts	New Jest mock function for testing.
scripts/__mocks__/@dicebear/core.ts	New mock function for avatar creation in tests.
scripts/__mocks__/@pdfme/generator.test.ts	New test suite for the generate function in the PDF generator.
scripts/__mocks__/@pdfme/generator.ts	New mock function simulating PDF generation.
scripts/__mocks__/fileMock.js	New mock file for testing file imports.
scripts/custom-test-env.js	New custom testing environment for Jest.
scripts/githooks/check-localstorage-usage.js	New script to check for localStorage usage in JavaScript files.
scripts/githooks/update-toc.js	New script to update the table of contents in Markdown files.
setup.ts	New setup script for configuring environment variables and application settings.

Assessment against linked issues

Objective	Addressed	Explanation
Refactor CSS files in src/screens/CommunityProfile (2503)	❌	No CSS refactoring changes were made.
Refactor CSS files in src/screens/Requests (2525)	❌	No CSS refactoring changes were made.
Refactor CSS files in src/screens/Users (2528)	❌	No CSS refactoring changes were made.
Refactor CSS files in src/screens/MemberDetail (2511)	❌	No CSS refactoring changes were made.
Refactor CSS files in src/screens/UserPortal (2527)	❌	No CSS refactoring changes were made.

Possibly related issues

• Refactor CSS files in src/screens/Requests #2525: Refactoring CSS files in src/screens/Requests aligns with ongoing efforts to streamline CSS into a global file.
• Refactor CSS files in src/screens/Users #2528: Refactoring CSS files in src/screens/Users is part of the initiative to improve UI/UX for color blind users.
• Refactor CSS files in src/screens/MemberDetail #2511: Refactoring CSS files in src/screens/MemberDetail is relevant to the same UI/UX improvements.
• Refactor CSS files in src/screens/UserPortal #2527: Refactoring CSS files in src/screens/UserPortal is part of the overall CSS streamlining efforts.
• Refactor CSS files in src/screens/EventManagement #2504: Refactoring CSS files in src/screens/EventManagement is connected to the broader goal of enhancing accessibility.
• Refactor CSS files in src/screens/OrgSettings #2523: Refactoring CSS files in src/screens/OrgSettings aims to improve usability for color blind users.
• Refactor CSS files in src/screens/Leaderboard #2508: Refactoring CSS files in src/screens/Leaderboard is relevant to the ongoing UI/UX improvements.
• Refactor CSS files in src/screens/BlockUser #2502: Refactoring CSS files in src/screens/BlockUser is part of the same initiative to enhance accessibility.
• Refactor CSS files in src/screens/OrgContribution #2520: Refactoring CSS files in src/screens/OrgContribution aligns with the UI/UX improvement goals.

Possibly related PRs

• coderabbit yaml file #1991: Introduces a .coderabbit.yaml configuration file, similar to changes in this PR.
• develop branch - coderabbit yaml file #1997: Adds a .coderabbit.yaml file with configuration settings, reinforcing relevance.
• Fixes: Translations Are Not Correctly Tested in Our PR Workflow  #2263: Modifies compare_translations.py, potentially linking to review features in the main PR.
• feat: Workflow changes which will label issues automatically as per #2256 #2390: Introduces automated labeling based on keywords, relevant to review processes.
• Upgrade @pdfme/generator to 5.0.0 #2413: Upgrades @pdfme/generator, which may relate to document generation processes.
• added docker check to workflow #2414: Adds a Docker check to workflows, potentially relevant to the new configuration settings.
• Added GitHub PR Workflow Check: Talawa Admin app starts (No Docker) #2452: Adds a check for application startup without Docker, relating to overall configuration.
• Updated pr template with checklist #2454: Updates the pull request template to include review checklists, aligning with the main PR.
• Updated pr template for develop-postgress branch #2458: Similar updates to the pull request template, reinforcing review processes.
• fix failing workflow of TS compilation #2472: Addresses failing workflows related to TypeScript compilation, connecting to review settings.
• reverting workflow changes #2498: Reverts workflow changes, which may relate to overall configuration settings.

Suggested labels

ignore-sensitive-files-pr

Suggested reviewers

• pranshugupta54
• varshith257
• palisadoes

🐰 In the land of code, where changes abound,
A YAML file spins, with settings profound.
New scripts and workflows, all neatly aligned,
For Talawa's journey, a path well-defined.
With each little tweak, our project will grow,
Together we hop, to new heights we’ll go! 🌟

---

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

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

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

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

CodeRabbit Commands (Invoked using PR comments)

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

Other keywords and placeholders

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

Documentation and Community

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

[github-actions]

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

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

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

Our policies make our code better.

Reviewers

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

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

Reviewing Your Code

Your reviewer(s) will have the following roles:

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

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

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

Other

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

[coderabbitai]

Actionable comments posted: 35

🧹 Outside diff range and nitpick comments (40)

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

1-11: Enhance header documentation and fix formatting

The current header only references an external README without providing immediate context. Consider:

1. Adding a brief description of the workflow's purpose
2. Including any prerequisites or important notes
3. Removing trailing spaces

-##############################################################################
-##############################################################################
-#
-# NOTE!
-#
-# Please read the README.md file in this directory that defines what should 
-# be placed in this file
-#
-##############################################################################
-##############################################################################
+# CodeQL Security Analysis Workflow
+#
+# This workflow performs automated code scanning using GitHub's CodeQL engine
+# to identify potential security vulnerabilities in JavaScript code.
+#
+# For detailed configuration options, see: .github/workflows/README.md

🧰 Tools

🪛 yamllint (1.35.1)

[error] 6-6: trailing spaces

(trailing-spaces)

---

21-30: Enhance job security configuration

The current configuration is good but could be improved with additional security measures:

 jobs:
   CodeQL:
-    if: ${{ github.actor != 'dependabot[bot]' }}
+    if: |
+      github.actor != 'dependabot[bot]' &&
+      github.event.pull_request.head.repo.full_name == github.repository
     name: Analyse Code With CodeQL
     runs-on: ubuntu-latest
+    permissions:
+      security-events: write
+      actions: read
+      contents: read
     strategy:
       fail-fast: false
       matrix:
         language: [ 'javascript' ]

.github/workflows/eslint_disable_check.py (1)

61-61: Rename unused loop variable dirs to _

The loop variable dirs is not used within the loop body. To indicate that it's intentionally unused, rename it to _ to improve code clarity.

Apply this diff to fix the issue:

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

🧰 Tools

🪛 Ruff (0.8.0)

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

Rename unused dirs to _dirs

(B007)

setup.ts (3)

43-49: Use fs.promises with async/await instead of callbacks

In an async function, it's preferable to use fs.promises with await to maintain readability and avoid nesting callbacks.

Apply this diff to refactor the code:

 const port = dotenv.parse(fs.readFileSync('.env')).PORT;

-fs.readFile('.env', 'utf8', (err, data) => {
-  const result = data.replace(`PORT=${port}`, `PORT=${customPort}`);
-  fs.writeFileSync('.env', result, 'utf8');
-});
+const data = await fs.promises.readFile('.env', 'utf8');
+const result = data.replace(`PORT=${port}`, `PORT=${customPort}`);
+await fs.promises.writeFile('.env', result, 'utf8');

Repeat this pattern for other similar occurrences in the code.

---

111-117: Consistently use fs.promises with async/await

Replace the callback-based fs.readFile with await fs.promises.readFile to maintain consistency and improve code readability.

Apply this diff:

 const useRecaptcha = dotenv.parse(
   fs.readFileSync('.env'),
 ).REACT_APP_USE_RECAPTCHA;

-fs.readFile('.env', 'utf8', (err, data) => {
-  const result = data.replace(
-    `REACT_APP_USE_RECAPTCHA=${useRecaptcha}`,
-    `REACT_APP_USE_RECAPTCHA=yes`,
-  );
-  fs.writeFileSync('.env', result, 'utf8');
-});
+const data = await fs.promises.readFile('.env', 'utf8');
+const result = data.replace(
+  `REACT_APP_USE_RECAPTCHA=${useRecaptcha}`,
+  `REACT_APP_USE_RECAPTCHA=yes`,
+);
+await fs.promises.writeFile('.env', result, 'utf8');

---

181-182: Correct the grammar in the success message

Change "setup" to "set up" to use the correct verb form in the success message.

Apply this diff:

-'\nCongratulations! Talawa Admin has been successfully setup! 🥂🎉',
+'\nCongratulations! Talawa Admin has been successfully set up! 🥂🎉',

.github/workflows/countline.py (1)

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

It's recommended to use utf-8 encoding to support a wider range of characters and ensure compatibility with most text files.

Apply this diff:

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

.husky/pre-commit (2)

1-1: Add Husky script initialization

The pre-commit hook is missing the Husky script initialization, which ensures that Husky functions correctly.

Apply this diff:

+#!/bin/sh
+. "$(dirname "$0")/_/husky.sh"
+
 npm run format:fix
 # npm run lint:fix
 npm run lint-staged
 npm run typecheck
 npm run update:toc

 git add .

---

8-8: Avoid adding all changes indiscriminately

Running git add . after the pre-commit tasks may stage unintended changes. It's safer to only stage specific files that were modified by the scripts.

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

11-12: Remove unnecessary empty line to satisfy Prettier formatting

There is an extra empty line at lines 11-12, which violates Prettier formatting rules as indicated by the static analysis tool.

Apply this diff:

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

🧰 Tools

🪛 eslint

[error] 11-12: Delete ··⏎

(prettier/prettier)

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

4-7: Improve JSDoc documentation

The JSDoc comment should follow TypeScript documentation standards and include proper tags.

/**
- * A custom environment to set the TextEncoder and TextDecoder variables, that is required by @pdfme during testing.
- * Providing a polyfill to the environment for the same
+ * A custom Jest test environment that provides TextEncoder and TextDecoder polyfills.
+ * These polyfills are required by the PDF generation library during testing.
+ * @extends {Environment}
 */

🧰 Tools

🪛 eslint

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

(tsdoc/syntax)

---

8-16: Add TypeScript types for better type safety

Consider converting this file to TypeScript for better type safety and IDE support.

- export default class CustomTestEnvironment extends Environment {
-   async setup() {
+ export default class CustomTestEnvironment extends Environment {
+   async setup(): Promise<void> {

🧰 Tools

🪛 eslint

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

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

---

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

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

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

11-11: Remove commented debug code

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

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

---

10-13: Improve error messages for better debugging

The error message could be more specific about which input was empty.

- throw new Error('Template or inputs cannot be empty.');
+ throw new Error(
+   `Validation failed: ${template.schemas.length === 0 ? 'template schemas' : 'inputs'} cannot be empty.`
+ );

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

4-47: Add test data constants and missing test case

Consider these improvements:

1. Centralize test data
2. Add positive test case verifying the PDF header

// Add at the top of the describe block
const validTemplate = { schemas: [{ name: 'field1' }] } as Template;
const validInputs = [{ field1: 'value1' }];
const emptyTemplate = { schemas: [] } as Template;
const emptyInputs: Record<string, string>[] = [];

// Add new test case
test('should generate PDF with correct header', async () => {
  const result = await generate({
    template: validTemplate,
    inputs: validInputs,
  });
  
  // Verify PDF header bytes (%PDF)
  expect(result.slice(0, 4)).toEqual(new Uint8Array([0x25, 0x50, 0x44, 0x46]));
  expect(result.length).toBeGreaterThan(4);
});

.github/workflows/stale.yml (2)

6-6: Remove trailing whitespace

There are trailing spaces on lines 6, 20, and 21 that should be removed.

Also applies to: 20-21

🧰 Tools

🪛 yamllint (1.35.1)

[error] 6-6: trailing spaces

(trailing-spaces)

---

31-34: Consider customizing stale messages

The stale and close messages could be more specific to your project's needs:

1. Reference the CSS refactoring context
2. Point to documentation about UI/accessibility standards
3. Mention how to verify changes don't break accessibility

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

4-11: Document the purpose of skipped files

Add comments explaining why each file is excluded from TSDoc validation. This helps maintain the skip list over time.

 // List of files to skip
+// Files that don't require TSDoc comments because:
+// - index.tsx: Only exports components
+// - EventActionItems.tsx: Simple presentational component
+// [Add reasons for other files...]
 const filesToSkip = [
     'index.tsx', 
     'EventActionItems.tsx',
     'OrgPostCard.tsx',
     'UsersTableItem.tsx',
     'FundCampaignPledge.tsx'
 ];

---

41-41: Improve TSDoc detection regex

The current regex might have false positives. Consider using a more robust pattern that ensures:

1. The comment is at the start of a declaration
2. It follows TSDoc format with @param, @returns, etc.

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

.github/workflows/push.yml (1)

6-6: Fix YAML formatting issues

There are several YAML formatting issues that should be addressed:

• Remove trailing spaces
• Fix indentation (2 spaces expected)
• Remove extra blank lines at the end

Also applies to: 17-18, 20-20, 50-50, 62-62

🧰 Tools

🪛 yamllint (1.35.1)

[error] 6-6: trailing spaces

(trailing-spaces)

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

65-69: Enhance localStorage detection

The current check might miss indirect localStorage usage. Consider:

1. Checking for variable assignments of localStorage
2. Checking for destructured usage
3. Using AST parsing for more accurate detection

if (
  content.includes('localStorage.getItem') ||
  content.includes('localStorage.setItem') ||
- content.includes('localStorage.removeItem')
+ content.includes('localStorage.removeItem') ||
+ content.includes('const storage = localStorage') ||
+ content.includes('const { getItem, setItem } = localStorage')
)

---

83-85: Enhance error message with more context

The error message could be more informative by including:

1. The custom hook import path
2. Code examples of correct usage

- console.error('\x1b[31m%s\x1b[0m', '\nError: Found usage of localStorage');
- console.error('\nFiles with localStorage usage:');
+ console.error('\x1b[31m%s\x1b[0m', '\nError: Direct localStorage usage detected');
+ console.error('\nPlease import useLocalStorage from "@hooks/useLocalStorage"');
+ console.error('\nAffected files:');

.github/workflows/issue.yml (2)

42-55: Simplify label management logic

The current implementation can be simplified using array methods.

- 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 currentLabels = labels.data.map(l => l.name);
+ const labelsToAdd = [];
+ 
+ if (currentLabels.includes('dependencies')) {
+   labelsToAdd.push('good first issue', 'security');
+ } else if (currentLabels.some(l => ['security', 'ui/ux'].includes(l))) {
+   labelsToAdd.push('good first issue');
+ }
+ 
+ if (labelsToAdd.length > 0) {
+   await github.rest.issues.addLabels({
+     ...apiParams,
+     labels: labelsToAdd
+   });
+ }

---

15-15: Fix YAML formatting issues

There are YAML formatting issues that should be addressed:

• Fix indentation (4 spaces expected for types)
• Remove extra blank lines at the end

Also applies to: 66-66

🧰 Tools

🪛 yamllint (1.35.1)

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

(indentation)

.github/workflows/talawa_admin_md_mdx_format_adjuster.py (1)

45-65: Consider adding logging and progress tracking.

The file processing functionality could benefit from:

1. Logging mechanism to track processed files
2. Progress indicator for large directories
3. Error handling for file permission issues

+import logging
+from tqdm import tqdm

 def process_file(filepath):
+    logging.info(f"Processing file: {filepath}")
     try:
         with open(filepath, 'r', encoding='utf-8') as file:
             content = file.read()
 
         # Escape MDX characters
         new_content = escape_mdx_characters(content)
 
         # Write the processed content back to the file only if there is a change
         if new_content != content:
+            logging.info(f"Changes detected in {filepath}")
             with open(filepath, 'w', encoding='utf-8') as file:
                 file.write(new_content)
+    except PermissionError:
+        logging.error(f"Permission denied: {filepath}")
+    except Exception as e:
+        logging.error(f"Error processing {filepath}: {str(e)}")

ISSUE_GUIDELINES.md (1)

5-5: Fix grammatical and formatting issues.

Several improvements needed:

1. Line 5: "a issues" should be "an issue"
2. Line 29: Remove duplicate "for similar deficiencies in the code"
3. Lines 44,53,57: "slack" should be capitalized as "Slack"

-In order to give everyone a chance to submit a issues reports
+In order to give everyone a chance to submit an issue report

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

-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
+1. Join our `#talawa-github` Slack channel

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

Also applies to: 29-29, 44-44, 53-53, 57-57

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

README.md (2)

Line range hint 3-56: This file appears unrelated to the PR objectives.

The PR description focuses on CSS refactoring for improving UI/UX, particularly for colorblind users. However, these README updates seem unrelated to those objectives.

Please clarify how these documentation updates relate to the CSS refactoring objectives or consider submitting them in a separate PR.

🧰 Tools

🪛 Markdownlint (0.35.0)

22-22: Missing link or image reference definition: "pfd"
Reference links and images should use a label that is defined

(MD052, reference-links-images)

🪛 LanguageTool

[uncategorized] ~22-~22: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...university students to work on selected open source projects. They are mentored by software...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

53-53: Fix markdown formatting.

Remove extra space after the hash in the heading.

-#  Videos
+# Videos

🧰 Tools

🪛 Markdownlint (0.35.0)

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

(MD019, no-multiple-space-atx)

PR_GUIDELINES.md (2)

31-34: Add language specifiers to code blocks

Code blocks should specify the language for proper syntax highlighting.

Update the code blocks:

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

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

Also applies to: 39-42

🧰 Tools

🪛 Markdownlint (0.35.0)

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

(MD040, fenced-code-language)

---

56-56: Improve clarity in the reviewer removal section

The sentence about code quality could be clearer and more concise.

Suggested revision:

-Removing assigned reviewers from your Pull Request will cause it to be closed. The quality of our code is very important to us. Therefore we make experienced maintainers of our code base review your code.
+Removing assigned reviewers from your Pull Request will cause it to be closed. Code quality is crucial, which is why experienced maintainers must 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)

package.json (1)

8-70: Review dependency version constraints

Several dependencies use the caret (^) version range which could lead to unexpected breaking changes. Consider using exact versions or tighter version ranges for critical dependencies, especially for the Apollo and MUI packages.

CODE_STYLE.md (2)

53-55: Improve clarity of fragment and class usage guidelines

The sentences have grammatical issues. Consider rewording to:

• "All Return fragments should be wrapped in empty tags"
• "Direct use of custom classes is discouraged; use CSS modules along with Bootstrap classes instead"

🧰 Tools

🪛 LanguageTool

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

(AI_EN_LECTOR_REPLACEMENT_NOUN_NUMBER)

---

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

(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)

---

58-69: Enhance code examples with language specifiers

The code blocks are missing language specifiers which affects syntax highlighting. Add appropriate language specifiers (e.g., jsx, typescript) to improve readability.

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

Also applies to: 73-115

🧰 Tools

🪛 Markdownlint (0.35.0)

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

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

225-226: Review coverage threshold requirement

The minimum coverage requirement of 95% is quite high and might be challenging to maintain. Consider starting with a lower threshold (e.g., 80%) and gradually increasing it as test coverage improves.

CONTRIBUTING.md (1)

Line range hint 321-334: Fix heading level inconsistency and code block formatting.

1. The heading "pre-commit hook" and "post-merge hook" should use h3 (###) instead of h4 (####) for consistent hierarchy.
2. The code blocks at lines 327 and 335 should use fenced code blocks with language specifiers.

Apply these changes:

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

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

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

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

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

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

24-28: Fix markdown formatting issues

There are a few formatting issues to address:

1. The bare URL should be properly formatted as a markdown link
2. The section title should use proper heading syntax

Apply these changes:

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

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

🧰 Tools

🪛 Markdownlint (0.35.0)

28-28: null
Bare URL used

(MD034, no-bare-urls)

---

25-25: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

DOCUMENTATION.md (1)

21-29: Fix grammar and formatting issues

There are several issues to address:

1. Grammar error in "The process in easy"
2. Modal verb usage with "should automatically launched"
3. Typo in "brower"
4. Bare URL for localhost

Apply these changes:

-The process in easy:
+The process is easy:
-A local version of `docs.talawa.io` should automatically launched in your browser at http://localhost:3000/
+A local version of `docs.talawa.io` should automatically launch in your browser at `http://localhost:3000`
-Always monitor the local website in your brower to make sure the changes are acceptable.
+Always monitor the local website in your browser to make sure the changes are acceptable.

🧰 Tools

🪛 Markdownlint (0.35.0)

25-25: null
Bare URL used

(MD034, no-bare-urls)

🪛 LanguageTool

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

(MD_BASEFORM)

---

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

(MARKDOWN_NNP)

.github/workflows/README.md (3)

24-24: Fix typo in workflow description

There's a word repetition in the action description.

Apply this change:

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

🧰 Tools

🪛 LanguageTool

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

(ENGLISH_WORD_REPEAT_RULE)

---

35-35: Fix abbreviation format

The abbreviation format needs to be corrected.

Apply this change:

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

🧰 Tools

🪛 LanguageTool

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

(E_G)

---

41-47: Consider adding version requirements for Python tools

The script guidelines mention several Python tools but don't specify version requirements. This could lead to inconsistent results across different environments.

Consider adding minimum version requirements for each tool:

• Pycodestyle
• Pydocstyle
• Pylint
• Flake8

Would you like me to help create a requirements-dev.txt file with the specific versions?

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between f9e10b8 and 90b1d16.

⛔ Files ignored due to path filters (75)

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

📒 Files selected for processing (82)

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

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

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

💤 Files with no reviewable changes (13)

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

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

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

🧰 Additional context used

🪛 eslint

scripts/custom-test-env.js

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

(tsdoc/syntax)

---

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

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

---

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

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

jest.config.js

[error] 33-33: Delete ·

(prettier/prettier)

---

[error] 34-34: Insert ,

(prettier/prettier)

scripts/githooks/update-toc.js

[error] 11-12: Delete ··⏎

(prettier/prettier)

scripts/githooks/check-localstorage-usage.js

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

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

---

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

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

---

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

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

---

[error] 89-89: Insert ,

(prettier/prettier)

---

[error] 92-92: Insert ,

(prettier/prettier)

🪛 yamllint (1.35.1)

.github/workflows/pull-request-target.yml

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 13-13: trailing spaces

(trailing-spaces)

---

[error] 15-15: trailing spaces

(trailing-spaces)

---

[error] 27-27: trailing spaces

(trailing-spaces)

---

[error] 28-28: trailing spaces

(trailing-spaces)

---

[error] 29-29: trailing spaces

(trailing-spaces)

---

[error] 31-31: trailing spaces

(trailing-spaces)

---

[error] 33-33: trailing spaces

(trailing-spaces)

---

[error] 34-34: trailing spaces

(trailing-spaces)

---

[error] 36-36: trailing spaces

(trailing-spaces)

---

[error] 41-41: trailing spaces

(trailing-spaces)

---

[error] 46-46: trailing spaces

(trailing-spaces)

---

[error] 71-71: trailing spaces

(trailing-spaces)

.github/workflows/codeql-codescan.yml

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 17-17: trailing spaces

(trailing-spaces)

---

[error] 20-20: trailing spaces

(trailing-spaces)

---

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

(indentation)

---

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

(indentation)

.github/workflows/stale.yml

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 20-20: trailing spaces

(trailing-spaces)

---

[error] 21-21: trailing spaces

(trailing-spaces)

.github/workflows/pull-request.yml

[error] 49-49: trailing spaces

(trailing-spaces)

---

[error] 60-60: trailing spaces

(trailing-spaces)

---

[error] 63-63: trailing spaces

(trailing-spaces)

---

[error] 92-92: trailing spaces

(trailing-spaces)

---

[error] 126-126: trailing spaces

(trailing-spaces)

---

[error] 129-129: trailing spaces

(trailing-spaces)

---

[error] 150-150: trailing spaces

(trailing-spaces)

---

[error] 157-157: trailing spaces

(trailing-spaces)

---

[error] 197-197: trailing spaces

(trailing-spaces)

---

[error] 201-201: trailing spaces

(trailing-spaces)

---

[error] 204-204: trailing spaces

(trailing-spaces)

---

[error] 205-205: trailing spaces

(trailing-spaces)

---

[error] 213-213: trailing spaces

(trailing-spaces)

---

[error] 243-243: trailing spaces

(trailing-spaces)

---

[error] 249-249: trailing spaces

(trailing-spaces)

---

[error] 251-251: trailing spaces

(trailing-spaces)

.github/workflows/push.yml

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 17-17: trailing spaces

(trailing-spaces)

---

[error] 18-18: trailing spaces

(trailing-spaces)

---

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

(indentation)

---

[error] 21-21: trailing spaces

(trailing-spaces)

---

[error] 50-50: trailing spaces

(trailing-spaces)

---

[warning] 62-62: too many blank lines

(1 > 0) (empty-lines)

.github/workflows/issue.yml

[error] 6-6: trailing spaces

(trailing-spaces)

---

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

(indentation)

---

[warning] 66-66: too many blank lines

(1 > 0) (empty-lines)

🪛 Markdownlint (0.35.0)

README.md

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

(MD019, no-multiple-space-atx)

INSTALLATION.md

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

(MD001, heading-increment)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD014, commands-show-output)

---

105-105: null
Bare URL used

(MD034, no-bare-urls)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD046, code-block-style)

---

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

(MD046, code-block-style)

---

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

(MD051, link-fragments)

---

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

(MD051, link-fragments)

CODE_STYLE.md

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

57-57: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

73-73: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

75-75: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

92-92: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

190-190: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

230-230: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

CONTRIBUTING.md

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

158-158: null
No empty links

(MD042, no-empty-links)

---

159-159: null
No empty links

(MD042, no-empty-links)

---

161-161: null
No empty links

(MD042, no-empty-links)

PR_GUIDELINES.md

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

.github/ISSUE_TEMPLATE/bug-report.md

36-36: null
Bare URL used

(MD034, no-bare-urls)

---

33-33: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

.github/ISSUE_TEMPLATE/feature-request.md

28-28: null
Bare URL used

(MD034, no-bare-urls)

---

25-25: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

DOCUMENTATION.md

25-25: null
Bare URL used

(MD034, no-bare-urls)

🪛 LanguageTool

README.md

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

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)

INSTALLATION.md

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

(ENGLISH_WORD_REPEAT_RULE)

---

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

(DURING_THAT_TIME_COMMA)

---

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

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

(NOUN_VERB_CONFUSION)

---

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

(MAC_OS)

---

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

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

(MAC_OS)

---

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

(ENGLISH_WORD_REPEAT_RULE)

---

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

(MAC_OS)

---

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

(NOUN_VERB_CONFUSION)

---

[uncategorized] ~158-~158: Possible missing comma found.
Context: ...ions in "setup" can be done manually as well and here's how to do it. - [Creating .e...

(AI_HYDRA_LEO_MISSING_COMMA)

---

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

(COMMA_COMPOUND_SENTENCE)

---

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

(NOUN_VERB_CONFUSION)

---

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

(NOUN_VERB_CONFUSION)

---

[uncategorized] ~234-~234: Possible missing comma found.
Context: ... service you set up during talawa-api installation as shown in this screenshot: ![reCAPTC...

(AI_HYDRA_LEO_MISSING_COMMA)

---

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

(MD_PRP_QUESTION_MARK)

---

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

(BY_DEFAULT_COMMA)

---

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

(AI_HYDRA_LEO_MISSING_COMMA)

---

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

(PRP_MD_NN)

CODE_STYLE.md

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

(AI_EN_LECTOR_REPLACEMENT_NOUN_NUMBER)

---

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

(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)

---

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

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

---

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

(ALL_OF_THE)

---

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

(ALL_OF_THE)

---

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

(ALL_OF_THE)

---

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

(ALL_OF_THE)

---

[grammar] ~134-~134: The singular proper name ‘Sass’ must be used with a third-person or a past tense verb.
Context: ...rms - _talawa.scss - Partial Sass file for Talawa - _utilities.scss - Pa...

(HE_VERB_AGR)

---

[grammar] ~135-~135: The singular proper name ‘Sass’ must be used with a third-person or a past tense verb.
Context: ... - _utilities.scss - Partial Sass file for utilities - _variables.scss -...

(HE_VERB_AGR)

---

[grammar] ~136-~136: The singular proper name ‘Sass’ must be used with a third-person or a past tense verb.
Context: ... - _variables.scss - Partial Sass file for variables - app.scss - Main S...

(HE_VERB_AGR)

---

[style] ~141-~141: Consider removing “of” to be more concise
Context: ...views/screens Constant - This houses all of the constants used in the project `GraphQl...

(ALL_OF_THE)

---

[style] ~143-~143: Consider removing “of” to be more concise
Context: ...in the project GraphQl - This houses all of the GraphQL queries and mutations used in t...

(ALL_OF_THE)

---

[style] ~145-~145: Consider removing “of” to be more concise
Context: ...in the project screens - This houses all of the views/screens to be navigated through i...

(ALL_OF_THE)

---

[style] ~147-~147: Consider removing “of” to be more concise
Context: ... in Talawa-Admin state - This houses all of the state management code for the project ...

(ALL_OF_THE)

---

[uncategorized] ~165-~165: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...following order: - React imports - Third party imports - Local imports If there is...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

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

(AI_EN_LECTOR_MISSING_DETERMINER_A)

---

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

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)

CONTRIBUTING.md

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

(INSERT_PLEASE)

---

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

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

(THE_SUPERLATIVE)

---

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

(UNLIKELY_OPENING_PUNCTUATION)

---

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

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

(IF_THERE_COMMA)

---

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

(RB_LY_COMMA)

---

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

(FIRST_SERVED)

---

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

(ON_SKYPE)

---

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

(EN_WORDINESS_PREMIUM_LAST_BUT_NOT_THE_LEAST)

---

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

(MISSING_TO_BETWEEN_BE_AND_VB)

---

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

(ON_SKYPE)

---

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

(EN_A_VS_AN)

---

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

(DURING_THAT_TIME_COMMA)

---

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

(MAC_OS)

---

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

(AI_HYDRA_LEO_MISSING_COMMA)

---

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

(AI_HYDRA_LEO_MISSING_COMMA)

---

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

(AI_HYDRA_LEO_MISSING_THE)

---

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

(AI_HYDRA_LEO_MISSING_THE)

---

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

(ON_SKYPE)

PR_GUIDELINES.md

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

(UNLIKELY_OPENING_PUNCTUATION)

---

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

(IN_ORDER_TO_PREMIUM)

---

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

(SPLIT_INFINITIVE)

---

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

(EN_WEAK_ADJECTIVE)

---

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

(SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)

---

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

(FIX_RESOLVE)

---

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

(SOONER_OR_LATER)

---

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

(COMMA_COMPOUND_SENTENCE)

---

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

(MAKE_CHANGES)

.github/workflows/README.md

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

(AI_HYDRA_LEO_MISSING_COMMA)

---

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

(ENGLISH_WORD_REPEAT_RULE)

---

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

(E_G)

CODE_OF_CONDUCT.md

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

(ENGLISH_WORD_REPEAT_RULE)

DOCUMENTATION.md

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

(MD_BASEFORM)

---

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

(MARKDOWN_NNP)

---

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

(AI_EN_LECTOR_REPLACEMENT_PREPOSITION)

🪛 actionlint (1.7.4)

.github/workflows/codeql-codescan.yml

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

(action)

---

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

(action)

---

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

(action)

.github/workflows/stale.yml

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

(action)

.github/workflows/pull-request.yml

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

(expression)

---

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

(shellcheck)

---

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

(expression)

.github/workflows/issue.yml

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

(action)

🪛 Ruff (0.8.0)

.github/workflows/eslint_disable_check.py

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

Rename unused dirs to _dirs

(B007)

.github/workflows/compare_translations.py

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

(B904)

🔇 Additional comments (18)

.gitignore (4)

13-14: LGTM! Improved test coverage configuration

The changes to the coverage directory pattern and addition of codecov are good improvements:

• Using coverage/ is more standard and explicit
• Adding codecov supports better CI integration

---

Line range hint 21-25: LGTM! Comprehensive environment file protection

Good security practice to ignore all variants of environment files to prevent accidental commits of sensitive information.

---

31-37: LGTM! Standard ignore patterns for logs and editor files

The additions follow common practices:

• Ignoring debug logs prevents cluttering the repository
• Ignoring editor-specific files keeps the repository clean and prevents conflicts between different IDEs

---

3-5: Consider standardizing on a single package manager

The inclusion of both yarn.lock and pnpm-lock.yaml suggests multiple package managers might be in use. This could lead to dependency resolution conflicts and inconsistent installations across development environments.

Let's check if multiple lock files exist in the repository:

Consider standardizing on a single package manager across the project to ensure consistent dependency resolution and avoid potential conflicts.

✅ Verification successful

Ignoring lock files is appropriate for this project setup

The repository currently uses npm as evidenced by the presence of only package-lock.json. Adding yarn.lock and pnpm-lock.yaml to .gitignore is a proactive measure to prevent accidental commits of lock files from other package managers, which is a good practice when working in teams where developers might have different local setups.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for the presence of different package manager lock files
echo "Checking for package manager lock files..."
find . -maxdepth 1 -type f \( -name "package-lock.json" -o -name "yarn.lock" -o -name "pnpm-lock.yaml" \)

Length of output: 218

---

Script:

#!/bin/bash
# Let's check package.json to see which package manager is specified
echo "Checking package.json for package manager configuration..."
cat package.json | jq -r '.packageManager // empty'

# Also check if there are any package manager related scripts
echo -e "\nChecking package manager related scripts..."
cat package.json | jq -r '.scripts | to_entries | .[] | select(.key | contains("npm") or contains("yarn") or contains("pnpm")) | .key'

Length of output: 420

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

1-98: Verify translation completeness and consistency

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

✅ Verification successful

Translation keys are consistent across all language files

The verification shows that all locale files (en, fr, hi, sp, zh) have exactly the same set of translation keys in both common.json and errors.json files. No missing or inconsistent keys were found.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for missing or inconsistent translation keys across language files

# Get all locale directories
echo "Checking translation keys consistency across language files..."
for locale_dir in public/locales/*; do
  if [ -d "$locale_dir" ]; then
    locale=$(basename "$locale_dir")
    echo "Checking $locale locale..."
    
    # Compare common.json keys if exists
    if [ -f "$locale_dir/common.json" ]; then
      echo "Keys in $locale/common.json:"
      jq 'keys' "$locale_dir/common.json"
    fi
    
    # Compare errors.json keys if exists
    if [ -f "$locale_dir/errors.json" ]; then
      echo "Keys in $locale/errors.json:"
      jq 'keys' "$locale_dir/errors.json"
    fi
  fi
done

Length of output: 10464

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

1-1482: Well-structured Hindi translations

The Hindi translations are well-organized with logical grouping and proper translations. The file structure with nested objects helps maintain clarity and organization.

.husky/post-merge (1)

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

The command git diff HEAD^ HEAD --exit-code -- ./package.json || npm install may not detect changes in package.json correctly in all scenarios, especially with merge commits or when there are multiple parents. Consider using git diff-tree -r HEAD@{1} HEAD -- ./package.json or checking for unstaged changes to package.json to ensure accurate detection.

public/manifest.json (2)

13-13: Verify the icon size and file consistency for logo192.png

The icon logo192.png is set with "sizes": "16x16", which may be inconsistent with the actual image dimensions and file name. Typically, logo192.png corresponds to a 192x192 icon. Please ensure that the sizes attribute matches the actual icon dimensions.

---

16-16: Ensure correct path for logo512.png

The source path for logo512.png has been changed to "src": "images/logo512.png". Confirm that the file exists at the new location and that all references to this icon are updated accordingly.

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

9-15: LGTM! Well-structured polyfill implementation

The implementation correctly:

1. Calls the parent class's setup method
2. Checks for undefined before adding polyfills
3. Properly extends the global object

🧰 Tools

🪛 eslint

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

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

---

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

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

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

3-22: LGTM! Well-implemented mock generator

The implementation:

1. Has proper TypeScript types
2. Validates inputs
3. Creates realistic mock PDF data
4. Returns a Promise as expected

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

21-46: LGTM! Comprehensive error case testing

The error case tests are well-structured and cover all invalid input combinations.

.github/workflows/talawa_admin_md_mdx_format_adjuster.py (1)

1-96: ⚠️ Potential issue

This file appears unrelated to the PR objectives.

The PR description indicates CSS refactoring for improving UI/UX, particularly for colorblind users. However, this new Python script for MDX formatting seems unrelated to those objectives.

Please clarify how this MDX formatting script relates to the CSS refactoring objectives or consider submitting it in a separate PR.

package.json (1)

33-33: ⚠️ Potential issue

Consider supporting LTS Node.js versions

The workflow requires Node.js v22.x which is currently not an LTS version. Consider supporting the current LTS version (v20.x) for better stability and wider adoption.

-          node-version: '22.x'
+          node-version: '20.x'

Likely invalid or redundant comment.

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

2-7: LGTM! Metadata updates improve consistency

The metadata changes improve clarity by using proper capitalization and consistent label naming.

DOCUMENTATION.md (2)

4-13: LGTM! Well-structured table of contents

The table of contents is clear and properly formatted using markdown.

---

31-32: LGTM! Clear directive about documentation location

The emphasis on not adding markdown files to this repository is clear and important.

🧰 Tools

🪛 LanguageTool

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

(AI_EN_LECTOR_REPLACEMENT_PREPOSITION)

CODE_OF_CONDUCT.md (1)

3-20: LGTM! Well-structured Table of Contents.

The addition of a Table of Contents with proper section links improves document navigation and readability.

🧰 Tools

🪛 LanguageTool

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

(ENGLISH_WORD_REPEAT_RULE)

[coderabbitai]

🛠️ Refactor suggestion

Optimize workflow triggers and fix naming convention

1. The workflow name should follow kebab-case convention
2. Consider limiting the branches to reduce unnecessary runs
3. Remove trailing spaces in branch patterns

-name: codeql codescan workflow
+name: codeql-security-scan

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

📝 Committable suggestion

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

Suggested change

	name: codeql codescan workflow
	on:
	pull_request:
	branches:
	- '**'
	push:
	branches:
	- '**'
	name: codeql-security-scan
	on:
	pull_request:
	branches:
	- 'main'
	- 'develop'
	push:
	branches:
	- 'main'
	- 'develop'

🧰 Tools

🪛 yamllint (1.35.1)

[error] 17-17: trailing spaces

(trailing-spaces)

---

[error] 20-20: trailing spaces

(trailing-spaces)

[coderabbitai]

⚠️ Potential issue

Update CodeQL actions and fix configuration

Several issues need to be addressed:

1. CodeQL action versions are outdated
2. Debug mode should not be enabled in production
3. Step indentation is inconsistent

     steps:
-       - name: Checkout repository
-         uses: actions/checkout@v4
+      - name: Checkout repository
+        uses: actions/checkout@v4

-       - name: Initialize CodeQL
-         uses: github/codeql-action/init@v2
-         with:
-          languages: ${{ matrix.language }}
-          debug: true
+      - name: Initialize CodeQL
+        uses: github/codeql-action/init@v3
+        with:
+          languages: ${{ matrix.language }}
+          debug: false

-       - name: Autobuild
-         uses: github/codeql-action/autobuild@v2
+      - name: Autobuild
+        uses: github/codeql-action/autobuild@v3

-       - name: Perform CodeQL Analysis
-         uses: github/codeql-action/analyze@v2
+      - name: Perform CodeQL Analysis
+        uses: github/codeql-action/analyze@v3

📝 Committable suggestion

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

Suggested change

	- name: Checkout repository
	uses: actions/checkout@v4
	- name: Initialize CodeQL
	uses: github/codeql-action/init@v2
	with:
	languages: ${{ matrix.language }}
	debug: true
	- name: Autobuild
	uses: github/codeql-action/autobuild@v2
	- name: Perform CodeQL Analysis
	uses: github/codeql-action/analyze@v2
	- name: Checkout repository
	uses: actions/checkout@v4
	- name: Initialize CodeQL
	uses: github/codeql-action/init@v3
	with:
	languages: ${{ matrix.language }}
	debug: false
	- name: Autobuild
	uses: github/codeql-action/autobuild@v3
	- name: Perform CodeQL Analysis
	uses: github/codeql-action/analyze@v3

🧰 Tools

🪛 actionlint (1.7.4)

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

(action)

---

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

(action)

---

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

(action)

🪛 yamllint (1.35.1)

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

(indentation)

---

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

(indentation)

[coderabbitai]

⚠️ Potential issue

French translations need improvement

Several translation issues need to be addressed:

1. Incomplete messages:
   • "notAuthorised": "Désolé!" needs completion
   • "notFoundMsg": "Oops!" needs completion
2. Inconsistent punctuation:
   • "talawaApiUnavailable": Unnecessary space before exclamation mark
3. Missing context:
   • "talawaApiUnavailable": Should include network connectivity check message like in English version

Suggested improvements:

-  "talawaApiUnavailable": "Le service Talawa-API n'est pas disponible !. ",
+  "talawaApiUnavailable": "Le service Talawa-API n'est pas disponible ! Vérifiez qu'il est en cours d'exécution et votre connectivité réseau.",
-  "notAuthorised": "Désolé! ",
+  "notAuthorised": "Désolé ! Vous n'êtes pas autorisé !",
-  "notFoundMsg": "Oops! ",
+  "notFoundMsg": "Oops ! La page demandée n'a pas été trouvée !"

📝 Committable suggestion

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

Suggested change

	{
	"talawaApiUnavailable": "Le service Talawa-API n'est pas disponible !. ",
	"notFound": "Pas trouvé",
	"unknownError": "Une erreur inconnue est survenue. {{msg}}",
	"notAuthorised": "Désolé! ",
	"errorSendingMail": "Erreur lors de l'envoi du courrier",
	"emailNotRegistered": "Email non enregistré",
	"notFoundMsg": "Oops! ",
	"errorOccurredCouldntCreate": "Une erreur s'est produite. Impossible de créer {{entity}}",
	"errorLoading": "Une erreur s'est produite lors du chargement des données {{entity}}"
	}
	{
	"talawaApiUnavailable": "Le service Talawa-API n'est pas disponible ! Vérifiez qu'il est en cours d'exécution et votre connectivité réseau.",
	"notFound": "Pas trouvé",
	"unknownError": "Une erreur inconnue est survenue. {{msg}}",
	"notAuthorised": "Désolé ! Vous n'êtes pas autorisé !",
	"errorSendingMail": "Erreur lors de l'envoi du courrier",
	"emailNotRegistered": "Email non enregistré",
	"notFoundMsg": "Oops ! La page demandée n'a pas été trouvée !",
	"errorOccurredCouldntCreate": "Une erreur s'est produite. Impossible de créer {{entity}}",
	"errorLoading": "Une erreur s'est produite lors du chargement des données {{entity}}"
	}

[coderabbitai]

⚠️ Potential issue

Fix text formatting and grammar issues

Several text issues need to be addressed:

1. Punctuation:
   • Remove double punctuation (!.)
2. Grammar and spelling:
   • "Authorised" should be "Authorized" in American English
   • "occured" should be "occurred"
3. Capitalization:
   • Inconsistent capitalization in error messages

Suggested improvements:

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

📝 Committable suggestion

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

Suggested change

	{
	"talawaApiUnavailable": "Talawa-API service is unavailable!. Is it running? Check your network connectivity too.",
	"notFound": "Not found",
	"unknownError": "An unknown error occurred. Please try again later. {{msg}}",
	"notAuthorised": "Sorry! you are not Authorised!",
	"errorSendingMail": "Error sending mail",
	"emailNotRegistered": "Email not registered",
	"notFoundMsg": "Oops! The Page you requested was not found!",
	"errorOccurredCouldntCreate": "An error occurred. Couldn't create {{entity}}",
	"errorLoading": "Error occured while loading {{entity}} data"
	}
	{
	"talawaApiUnavailable": "Talawa-API service is unavailable! Is it running? Check your network connectivity too.",
	"notFound": "Not found",
	"unknownError": "An unknown error occurred. Please try again later. {{msg}}",
	"notAuthorised": "Sorry! You are not authorized!",
	"errorSendingMail": "Error sending mail",
	"emailNotRegistered": "Email not registered",
	"notFoundMsg": "Oops! The Page you requested was not found!",
	"errorOccurredCouldntCreate": "An error occurred. Couldn't create {{entity}}",
	"errorLoading": "Error occurred while loading {{entity}} data"
	}

[coderabbitai]

🛠️ Refactor suggestion

Improve Chinese translations and key formatting

1. Translation improvements needed:

   • "admin": "行政" is too generic, consider "管理员" for consistency with "admins"

2. Key formatting:

   • Keys with spaces (e.g., "My Organizations", "Action Items") should use camelCase or snake_case for consistency

Suggested improvements:

-  "admin": "行政",
+  "admin": "管理员",
-  "My Organizations": "我的组织",
+  "myOrganizations": "我的组织",
-  "Action Items": "行动项目",
+  "actionItems": "行动项目"

Also applies to: 54-68

[coderabbitai]

⚠️ Potential issue

Fix shell script security issue

The script is vulnerable to word splitting and globbing issues. Additionally, the environment variable reference is incorrect.

-          CHANGED_FILES: ${{ steps.changed_files.outputs.all_changed_files }}
+          CHANGED_FILES: ${{ steps.changed-files.outputs.all_changed_files }}
-        run: npx eslint ${CHANGED_FILES} && python .github/workflows/eslint_disable_check.py
+        run: npx eslint "${CHANGED_FILES}" && python .github/workflows/eslint_disable_check.py

📝 Committable suggestion

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

Suggested change

	CHANGED_FILES: ${{ steps.changed_files.outputs.all_changed_files }}
	run: npx eslint ${CHANGED_FILES} && python .github/workflows/eslint_disable_check.py
	CHANGED_FILES: ${{ steps.changed-files.outputs.all_changed_files }}
	run: npx eslint "${CHANGED_FILES}" && python .github/workflows/eslint_disable_check.py

🧰 Tools

🪛 actionlint (1.7.4)

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

(expression)

---

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

(shellcheck)

[coderabbitai]

⚠️ Potential issue

Improve security of branch name handling

Direct use of GitHub context variables in shell scripts poses a security risk. Pass these values through environment variables.

-        if: ${{ github.event.pull_request.base.ref == github.event.pull_request.head.ref }}
+        env:
+          SOURCE_BRANCH: ${{ github.event.pull_request.head.ref }}
+          TARGET_BRANCH: ${{ github.event.pull_request.base.ref }}
         run: |
-          echo "Source Branch ${{ github.event.pull_request.head.ref }}"
-          echo "Target Branch ${{ github.event.pull_request.base.ref }}"
+          echo "Source Branch $SOURCE_BRANCH"
+          echo "Target Branch $TARGET_BRANCH"
           echo "Error: Source and Target Branches are the same. Please ensure they are different."
           exit 1

📝 Committable suggestion

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

Suggested change

	run: |
	echo "Source Branch ${{ github.event.pull_request.head.ref }}"
	echo "Target Branch ${{ github.event.pull_request.base.ref }}"
	echo "Error: Source and Target Branches are the same. Please ensure they are different."
	exit 1
	env:
	SOURCE_BRANCH: ${{ github.event.pull_request.head.ref }}
	TARGET_BRANCH: ${{ github.event.pull_request.base.ref }}
	run: |
	echo "Source Branch $SOURCE_BRANCH"
	echo "Target Branch $TARGET_BRANCH"
	echo "Error: Source and Target Branches are the same. Please ensure they are different."
	exit 1

🧰 Tools

🪛 actionlint (1.7.4)

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)

[coderabbitai]

🛠️ Refactor suggestion

Add language specifiers to code blocks.

All code blocks should specify their language for proper syntax highlighting. Add appropriate language specifiers (e.g., bash, env, etc.) to the code blocks.

Example fix for one code block:

-```
+```bash
npm install

Also applies to: 154-156, 164-166, 188-190, 194-196, 200-202, 208-210, 214-216, 220-222, 240-242, 256-258, 264-266, 270-272, 292-294, 300-303, 313-315

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

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

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

(MD040, fenced-code-language)

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit -->

[coderabbitai]

🛠️ Refactor suggestion

Format bare URL properly.

The nodejs.org URL should be properly formatted as a markdown link.

Apply this change:

-first install `node.js` from their website at https://nodejs.org
+first install `node.js` from their website at [nodejs.org](https://nodejs.org)

📝 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

	1. first install `node.js` from their website at https://nodejs.org
	1. first install `node.js` from their website at [nodejs.org](https://nodejs.org)

🧰 Tools

🪛 Markdownlint (0.35.0)

105-105: null
Bare URL used

(MD034, no-bare-urls)

[coderabbitai]

🛠️ Refactor suggestion

Format section header and URL properly.

1. Use proper markdown heading syntax for the "Potential internship candidates" section.
2. Format the URL as a markdown link.

Apply these changes:

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

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

📝 Committable suggestion

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

Suggested change

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

🧰 Tools

🪛 Markdownlint (0.35.0)

36-36: null
Bare URL used

(MD034, no-bare-urls)

---

33-33: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

[palisadoes]

This PR has too many submitted files.

Please ensure the following:

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

Closing