Refactor LeftDrawerOrg Component CSS

[dhruuvarora]

What kind of change does this PR introduce?
This is a refactoring change aimed at improving the maintainability and consistency of the CSS used in the LeftDrawerOrg component.

Issue Number:
Fixes #2900

Did you add tests for your changes?
No, as this change only involves CSS refactoring and does not affect any functionality or logic requiring tests.

Snapshots/Videos:
Not applicable, as the visual output remains unchanged.

If relevant, did you update the documentation?
No documentation updates were required for this change.

Summary:
This PR refactors the CSS in the LeftDrawerOrg component to align with the project's goal of consolidating styles into a global file (app.module.css).
Key changes include:

Removed embedded styles and the LeftDrawerOrg.module.css file.
Merged relevant styles into app.module.css to centralize style management.
Updated the LeftDrawerOrg.tsx component to use class names from the global app.module.css.
The changes improve code maintainability and ensure the CSS follows the standardized pattern being implemented across the project.

Does this PR introduce a breaking change?
No, this refactoring does not introduce any breaking changes. All functionality remains intact, and there are no visual regressions.

Other information:
This change is part of a larger initiative to streamline the CSS structure across the project, making it easier for contributors to add or modify styles in the future. By consolidating styles into a single file, the project improves consistency and reduces redundancy.

Have you read the contributing guide?
Yes

Summary by CodeRabbit

• New Features

  • Introduced a new configuration file for managing YAML language server settings.
  • Added a new .env.example file for environment variable configuration in the Talawa-admin project.
  • Implemented a new GitHub Actions workflow for automated dependency updates.
  • Added comprehensive localization support for multiple languages including English, French, Hindi, Spanish, and Chinese.

• Bug Fixes

  • Enhanced error handling in various scripts and configuration files.

• Documentation

  • Updated installation and contribution guidelines in INSTALLATION.md.
  • Introduced a new document for issue reporting guidelines.

• Style

  • Improved formatting and organization of multiple documentation files.

• Tests

  • Added new test cases for various functionalities and mock implementations.

• Chores

  • Updated various configuration files to enhance project setup and management.

[coderabbitai]

Walkthrough

This pull request introduces a comprehensive set of configuration, workflow, and documentation changes for the Talawa Admin project. The changes span multiple areas including GitHub workflows, linting configurations, environment setup, localization, and project structure. Key modifications include adding new configuration files like .coderabbit.yaml, updating ESLint and Prettier settings, introducing new GitHub Actions workflows, and adding localization files for multiple languages.

Changes

File/Directory	Change Summary
.coderabbit.yaml	New configuration file for YAML language server with review and chat settings
.env.example	Added environment variables for development configuration
.eslintignore, .eslintrc.json	Updated linting configurations and exclusions
.github/workflows/	Added multiple new workflow files for CI/CD, code quality checks, and automation
public/locales/	Added localization files for English, French, Hindi, Spanish, and Chinese
package.json	Major updates to dependencies, scripts, and project configuration
config/	Added Babel and Vite configuration files
scripts/	Added various utility scripts for testing, githooks, and setup

Assessment against linked issues

Objective	Addressed	Explanation
Refactor CSS in LeftDrawerOrg	❓	No direct CSS refactoring evident in this PR

Possibly related issues

• Refactor CSS in src/components/LeftDrawer/LeftDrawer.tsx #2899: Refactoring CSS in LeftDrawer/LeftDrawer.tsx
• Refactor CSS files in src/screens/OrgList #2521: Refactoring CSS files in src/screens/OrgList
• Refactor CSS files in src/screens/OrgContribution #2520: Refactoring CSS files in src/screens/OrgContribution

Possibly related PRs

• refactored OrganizationDashboard css/ closes #2513 #2593, refactored: CSS files in src/screens/OrgSettings(fixes: #2523) #2610, Refactor CSS files in src/screens/OrgContribution (Fixs : #2520) #2674, Refactor CSS files in src/screens/ForgotPassword (fixes #2506) #2914, [REFACTOR] CSS for AddOnEntry.tsx #2933, Refactor CSS in src/components/LeftDrawer (fixes #2899) #2963: PRs focusing on CSS refactoring
• fix failing workflow of TS compilation #2472: Workflow updates for TypeScript compilation
• reverting workflow changes #2498: Workflow-related improvements

Suggested reviewers

• @palisadoes

Poem

🐰 A Rabbit's Configuration Tale 🐰

In workflows and configs, a dance begins,
CodeRabbit weaves magic, where structure wins.
Locales bloom like spring, in languages grand,
Linting and testing, all carefully planned!

Hop, hop, configuration complete! 🌈

Tip

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

---

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

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

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

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

CodeRabbit Commands (Invoked using PR comments)

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

Other keywords and placeholders

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

Documentation and Community

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

[github-actions]

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

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

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

Our policies make our code better.

Reviewers

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

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

Reviewing Your Code

Your reviewer(s) will have the following roles:

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

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

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

Other

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

[coderabbitai]

Actionable comments posted: 20

🧹 Nitpick comments (56)

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

2-2: Consider enhancing error message clarity

Some error messages are too brief and might not provide enough context to users:

• "तलवा-एपीआई सेवा उपलब्ध नहीं है!" could include connectivity check suggestion
• "क्षमा मांगना!" (Sorry!) should include the reason (not authorized)
• "उफ़!" needs more context about the page not found error

Consider expanding these messages to provide more context, similar to the English translations.

Also applies to: 5-5, 8-8

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

5-5: Fix typos and standardize message formatting

There are some inconsistencies in the English messages:

1. Line 5: "Authorised" should be "authorized" (American English)
2. Line 10: "occured" should be "occurred"

Apply these corrections:

-  "notAuthorised": "Sorry! you are not Authorised!",
+  "notAuthorised": "Sorry! You are not authorized!",
-  "errorLoading": "Error occured while loading {{entity}} data"
+  "errorLoading": "Error occurred while loading {{entity}} data"

Also applies to: 10-10

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

1-11: Consider implementing a localization review process

To ensure consistency across all language files:

1. Establish a style guide for error messages across all languages
2. Define minimum required context for each error type
3. Consider cultural differences in error message formatting
4. Implement a review process with native speakers

Would you like me to help create a localization style guide template or set up automated validation for message completeness?

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

83-85: Inconsistent placeholder usage in success messages.

The success messages use different formats for the placeholder:

• Line 83: "{{item}} 添加成功"
• Line 84: "{{item}} 更新成功"
• Line 85: "{{item}} 删除成功"

While these work, consider standardizing the placeholder position for better maintainability.

-  "addedSuccessfully": "{{item}} 添加成功",
-  "updatedSuccessfully": "{{item}} 更新成功",
-  "removedSuccessfully": "{{item}} 删除成功",
+  "addedSuccessfully": "成功添加{{item}}",
+  "updatedSuccessfully": "成功更新{{item}}",
+  "removedSuccessfully": "成功删除{{item}}"

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

Line range hint 164-164: Fix typo in English text.

There's a typo in the word "enable".

-  "manageFeaturesInfo": "Creation Successful ! Please select features that you want to enale for this organization from the plugin store.",
+  "manageFeaturesInfo": "Creation Successful! Please select features that you want to enable for this organization from the plugin store."

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

1-1482: Consider merging duplicate translations with common.json.

There are several translations that appear in both translation.json and common.json. Consider consolidating these to avoid maintenance overhead and potential inconsistencies.

Examples of duplicates:

• Login-related translations
• User profile translations
• Common action buttons

Consider moving shared translations to common.json and keeping only component-specific translations in translation.json. This will make maintenance easier and reduce the risk of inconsistencies.

---

34-34: Fix typo in numeric value check message.

There's a typo in "Atleast".

-  "numeric_value_check": "Atleaset one numeric value",
+  "numeric_value_check": "At least one numeric value"

Also applies to: 35-35

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

1-1483: Consider reorganizing translation keys for better maintainability

The translation file is well-structured but could benefit from a more maintainable organization:

1. Consider using dot notation for nested keys (e.g., user.login.title instead of nested objects)
2. Group common/shared translations under a common namespace
3. Consider splitting the file into smaller modules by feature

---

16-16: Translate remaining English text to Hindi

The following strings are still in English and should be translated to Hindi:

• "Palisadoes" in loginPage.fromPalisadoes
• "Talawa API" in multiple error messages

Also applies to: 383-383, 391-391, 403-403

---

229-230: Add translations for error cases

While the string interpolation is implemented correctly using {{variable}} syntax, consider adding translations for error cases when the variables are undefined or contain unexpected values.

Example error case translations to add:

+"removeUserFromUnknownOrg": "अज्ञात संगठन से उपयोगकर्ता को हटाएं",
+"unknownUserRemoveConfirmation": "क्या आप वाकई एक अज्ञात उपयोगकर्ता को हटाना चाहते हैं?"

.github/workflows/compare_translations.py (4)

1-49: Streamline the docstring for clarity and relevance.
This opening docstring is quite extensive, which may be beneficial in some cases. However, you might consider condensing or splitting the lengthy remarks into smaller sections or separate documentation for easier readability.

---

91-116: Enhance error handling and recursion safeguards.
The flatten_json function works recursively and can handle nested dictionaries well. However, you may consider adding a safeguard for extremely deep or malformed JSON structures to prevent potential runtime issues or stack overflows.

---

127-135: Adopt Python 3's exception chaining.
Static analysis suggests using raise ValueError(...) from e to maintain traceability of the original exception. Here’s a possible adjustment:

-raise ValueError(f"Error decoding JSON from file {filepath}: {e}")
+raise ValueError(f"Error decoding JSON from file {filepath}: {e}") from e

🧰 Tools

🪛 Ruff (0.8.2)

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

(B904)

---

147-157: Skip hidden or system directories containing translations.
Currently, the script removes "en" from the list of language directories. You may also consider ignoring hidden directories (like .git or those prefixed with a dot) or other non-locales directories. This avoids potential confusion or errors if a hidden folder is inadvertently placed in the same directory.

setup.ts (3)

13-21: Ensure proper error handling for file operations.

Here, the code creates or updates the .env file by reading from .env.example. However, if any of these file I/O operations fail, there's no fallback or explicit error handling (e.g., retry or user notification). Consider wrapping these operations with appropriate error checks or try/catch blocks to gracefully handle failures.

---

40-49: Use consistent synchronous or asynchronous I/O.

These lines mix synchronous (fs.readFileSync) and asynchronous (fs.readFile with callback) file operations, which can unintentionally complicate flow control and error handling. Refactoring to a single approach—preferably asynchronous with promises—can improve clarity and potential performance.

---

106-161: Consolidate environment variable updates in a helper utility.

Multiple segments in this block read .env and replace environment variables. This could be refactored into a dedicated helper function (e.g., updateEnvVariable(key, value)) to reduce duplication and streamline maintenance.

.husky/post-merge (1)

1-4: Consider using npm ci for deterministic installs.

Relying on npm install after a merge may install updated dependencies. Using npm ci ensures reproducible builds by installing exactly from your lockfile.

.husky/pre-commit (1)

5-5: Revisit the commented-out lint fix command.

You commented out npm run lint:fix. If automated linting is desired, consider re-enabling it. If not, remove the commented-out line to minimize confusion.

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

11-12: Remove unnecessary newline to adhere to Prettier rules.

Prettier flags the extra blank line here. Consider deleting it to maintain consistent formatting.

10   execSync(command, { stdio: 'inherit' });
11-
12-
13 });

🧰 Tools

🪛 eslint

[error] 11-12: Delete ··⏎

(prettier/prettier)

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

4-7: Fix the TSDoc tag or remove it if it is not valid.
The @pdfme reference in the doc comment may trigger a tsdoc-undefined-tag error. Consider removing or defining this tag to comply with the configured TSDoc rules.

🧰 Tools

🪛 eslint

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

(tsdoc/syntax)

---

9-9: Add explicit return type for the async setup method if required.
Even though this overrides a Jest method and typically returns void, adding a clear return type can address lint warnings and improve code clarity.

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

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

1-11: Centralize or externalize skip list for easier maintenance
Having the skip list defined inline is acceptable for small sets, but as the project grows, consider relocating it to a configuration file (e.g., .tsdocskiprc) to keep it in sync across scripts.

---

37-46: Proper TSDoc detection approach
The regex matches basic multiline TSDoc (/** ... */), which is sufficient for a first pass. If a more robust approach is needed (e.g., ignoring inline JSDoc or detecting advanced tags), consider using a specialized AST parser.

.github/workflows/eslint_disable_check.py (2)

61-61: Rename unused variable dirs to _dirs.

Although Python permits unused variables by convention, it's best practice to prefix them with an underscore to clarify that they're purposefully unused.

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

🧰 Tools

🪛 Ruff (0.8.2)

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

Rename unused dirs to _dirs

(B007)

---

63-64: Consider checking .ts files as well.

Currently, only .tsx files are analyzed (excluding .test.tsx). If your intention is to enforce no eslint-disable in all TypeScript files, consider also scanning .ts files or clarifying that .tsx alone is sufficient.

.github/workflows/countline.py (2)

197-198: Update docstring to reflect actual functionality.

The docstring says "Analyze dart files," but this script appears to analyze general code files or lines of code in lib, src, and test. Update the docstring to prevent confusion.

-"""Analyze dart files."""
+"""Analyze lines of code in lib, src, and test directories."""

---

261-263: Consider extending comment detection.

Currently, lines starting with // or /* won't be fully recognized as comments unless they explicitly start with /. If you want to exclude all comment styles (including multi-line), consider enhancing the filtering logic.

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

31-36: Fix markdown formatting issues

Please address the following markdown issues:

1. Use proper heading syntax instead of bold emphasis
2. Convert the bare URL to a proper markdown link

Apply this diff:

-**Additional details**
+### Additional details
 Add any other context or screenshots about the feature request here.

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

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

🧰 Tools

🪛 Markdownlint (0.37.0)

36-36: null
Bare URL used

(MD034, no-bare-urls)

---

33-33: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

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

25-28: Fix markdown formatting to match bug report template

Please apply the same markdown fixes as the bug report template:

1. Use proper heading syntax
2. Convert the bare URL to a markdown link

Apply this diff:

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

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

🧰 Tools

🪛 Markdownlint (0.37.0)

28-28: null
Bare URL used

(MD034, no-bare-urls)

---

25-25: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

.env.example (1)

24-24: Add security note for RECAPTCHA_SITE_KEY

While this is just a template file, it's good practice to add a note reminding users to keep the RECAPTCHA_SITE_KEY secure and never commit the actual .env file.

-REACT_APP_RECAPTCHA_SITE_KEY=
+# IMPORTANT: Keep this key secure and never commit your actual .env file
+REACT_APP_RECAPTCHA_SITE_KEY=

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

17-17: Fix YAML formatting issues

There are several formatting issues in the workflow file:

• Remove trailing spaces
• Fix indentation levels

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

Also applies to: 20-20, 31-31, 37-37

🧰 Tools

🪛 yamllint (1.35.1)

[error] 17-17: trailing spaces

(trailing-spaces)

.github/pull_request_template.md (1)

22-24: Consider enhancing issue linking format.

While the issue number section is good, consider using a more structured format to ensure consistent parsing:

-**Issue Number:**
-
-Fixes #<!--Add related issue number here.-->
+**Issue Number:** #<!--Add issue number here-->
+
+Resolves: #<!--Add issue number here-->

This format aligns better with GitHub's issue linking keywords and provides clearer structure.

.github/workflows/stale.yml (1)

1-43: Fix YAML formatting issues.

There are several trailing spaces in the file that should be removed.

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

🧰 Tools

🪛 actionlint (1.7.4)

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)

🪛 yamllint (1.35.1)

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 20-20: trailing spaces

(trailing-spaces)

---

[error] 21-21: trailing spaces

(trailing-spaces)

.github/workflows/push.yml (2)

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

While the current configuration is good, consider enabling fail_ci_if_error for stricter quality control.

       with:
         token: ${{ secrets.CODECOV_TOKEN }}
         verbose: true
-        fail_ci_if_error: false
+        fail_ci_if_error: true
         name: '${{env.CODECOV_UNIQUE_NAME}}'

---

1-62: Fix YAML formatting inconsistencies.

There are several formatting issues to address:

• Inconsistent indentation (e.g., line 20)
• Extra blank lines at the end
• Trailing spaces

Consider using a YAML formatter to maintain consistent styling.

🧰 Tools

🪛 yamllint (1.35.1)

[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/README.md (3)

13-15: Fix formatting and grammar in workflow guidelines

The list items need proper formatting and punctuation:

-1. The file roles below are maintained
-1. The sequence of the jobs in the workflows are maintained using [GitHub Action dependencies](https://docs.github.com/en/actions/learn-github-actions/managing-complex-workflows). 
+1. The file roles below are maintained.
+2. The sequence of the jobs in the workflows is maintained using [GitHub Action dependencies](https://docs.github.com/en/actions/learn-github-actions/managing-complex-workflows).

🧰 Tools

🪛 LanguageTool

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

(AI_HYDRA_LEO_MISSING_COMMA)

---

24-24: Fix typo in workflow documentation

There's a duplicate word "to" in the sentence.

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

🧰 Tools

🪛 LanguageTool

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

(ENGLISH_WORD_REPEAT_RULE)

---

35-35: Fix abbreviation format

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

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

🧰 Tools

🪛 LanguageTool

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

(E_G)

.github/workflows/issue.yml (1)

42-48: Improve code readability in label assignment logic

The label assignment logic could be more readable:

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

ISSUE_GUIDELINES.md (3)

5-5: Fix grammar in introduction

The sentence has grammatical issues:

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

🧰 Tools

🪛 LanguageTool

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

(EN_A_VS_AN)

---

44-44: Capitalize "Slack" references

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

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

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

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

Also applies to: 53-53, 57-57

🧰 Tools

🪛 LanguageTool

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

(ON_SKYPE)

---

29-29: Fix duplicate text in guidelines

The sentence contains duplicate text and needs cleanup:

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

README.md (1)

53-53: Fix heading formatting

Remove extra spaces after the hash symbol.

-#  Videos
+# Videos

🧰 Tools

🪛 Markdownlint (0.37.0)

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

(MD019, no-multiple-space-atx)

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

1-77: LGTM! Workflow enhances contribution process

The workflow effectively:

• Communicates PR review policies
• Provides clear guidelines for contributors
• Welcomes first-time contributors

Remove trailing spaces in the YAML file to improve formatting.

🧰 Tools

🪛 yamllint (1.35.1)

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 13-13: trailing spaces

(trailing-spaces)

---

[error] 15-15: trailing spaces

(trailing-spaces)

---

[error] 27-27: trailing spaces

(trailing-spaces)

---

[error] 28-28: trailing spaces

(trailing-spaces)

---

[error] 29-29: trailing spaces

(trailing-spaces)

---

[error] 31-31: trailing spaces

(trailing-spaces)

---

[error] 33-33: trailing spaces

(trailing-spaces)

---

[error] 34-34: trailing spaces

(trailing-spaces)

---

[error] 36-36: trailing spaces

(trailing-spaces)

---

[error] 41-41: trailing spaces

(trailing-spaces)

---

[error] 46-46: trailing spaces

(trailing-spaces)

---

[error] 71-71: trailing spaces

(trailing-spaces)

PR_GUIDELINES.md (1)

31-34: Add language identifiers to code blocks.

Specify the language for the code blocks to enable syntax highlighting:

-```
+```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.37.0)

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

(MD040, fenced-code-language)

CODE_STYLE.md (3)

1-39: Fix grammatical issues in the introduction sections.

The document structure is well-organized, but there are some grammatical issues to address:

• Line 27: Consider adding "please" before "Let us know"
• Line 34: Add a hyphen for the compound adjective "open-source"

---

57-89: Add language specifiers to code blocks.

The code examples are helpful, but they should specify the language for proper syntax highlighting. Add language identifiers to the code blocks, for example:

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

🧰 Tools

🪛 LanguageTool

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

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

🪛 Markdownlint (0.37.0)

57-57: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

73-73: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

75-75: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

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)

---

190-253: Clarify the relationship between CSS modules and SCSS files.

Consider adding a section explaining how CSS modules and SCSS files work together in the project, including:

• When to use CSS modules vs SCSS
• How the compilation process affects both
• Best practices for organizing styles between the two

🧰 Tools

🪛 LanguageTool

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

🪛 Markdownlint (0.37.0)

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)

---

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)

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

214-227: Enhance test coverage reporting configuration.

Consider adding:

1. A step to save test results as artifacts for debugging failures
2. More detailed error messages when coverage thresholds aren't met

      - name: Save test results
        if: always()
        uses: actions/upload-artifact@v3
        with:
          name: test-results
          path: coverage/

CONTRIBUTING.md (2)

158-161: Fix empty markdown links.

The following links are empty and should be fixed:

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

🧰 Tools

🪛 Markdownlint (0.37.0)

158-158: null
No empty links

(MD042, no-empty-links)

---

159-159: null
No empty links

(MD042, no-empty-links)

---

161-161: null
No empty links

(MD042, no-empty-links)

---

73-78: Improve clarity in conflict resolution section.

The conflict resolution section has several grammatical issues:

• Line 73: Add a comma after "Usually"
• Line 77: Replace "Last but not the least" with "Finally"
• Line 77: Capitalize "Slack" as it's a proper noun
• Line 78: Add a comma after "last resort"

🧰 Tools

🪛 LanguageTool

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

DOCUMENTATION.md (2)

14-30: Fix grammatical and formatting issues

A few improvements needed:

1. Line 25: Fix grammar - "should automatically launched" → "should automatically launch"
2. Line 25: Wrap the URL in markdown syntax - http://localhost:3000/ → [http://localhost:3000/](http://localhost:3000/)
3. Line 26: Capitalize "Markdown" as it's a proper noun

-    - 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/](http://localhost:3000/)
-1. Add/modify the markdown documents to the `docs/` directory of the `talawa-docs` repository
+1. Add/modify the Markdown documents to the `docs/` directory of the `talawa-docs` repository

🧰 Tools

🪛 Markdownlint (0.37.0)

25-25: null
Bare URL used

(MD034, no-bare-urls)

🪛 LanguageTool

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

(MD_BASEFORM)

---

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

(MARKDOWN_NNP)

---

31-32: Improve preposition usage

Change "in this repository" to "to this repository" for better clarity.

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

🧰 Tools

🪛 LanguageTool

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

(AI_EN_LECTOR_REPLACEMENT_PREPOSITION)

INSTALLATION.md (2)

1-337: Fix markdown formatting issues

Several markdown formatting improvements needed:

1. Add language identifiers to code blocks (lines 142, 154, 164, 188, 194, 200, 208, 214, 220, 240, 256, 264, 270, 292, 300, 313)
2. Use consistent code block style (fenced instead of indented) for git commands (lines 327, 335)
3. Fix heading increment (h4 used where h3 was expected) at line 321
4. Fix unordered list indentation (lines 33-34)
5. Remove bare URL (line 105)
6. Fix link fragments to use lowercase (line 178)

Example fixes:

-```
+```bash
 npm install

•    git commit -m "commit message" --no-verify
  

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

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

-first install node.js from their website at https://nodejs.org
+first install node.js from their website at https://nodejs.org

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

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

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)

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

[duplication] ~25-~25: Possible typo: you repeated a word
Context: ...](#running-talawa-admin)   - [Accessing 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.js` packages in Windows, Linux and MacOS.  1. For Windows:    1. first install `...

(MAC_OS)

---

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

(ENGLISH_WORD_REPEAT_RULE)

---

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

(MAC_OS)

---

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

(NOUN_VERB_CONFUSION)

---

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

(COMMA_COMPOUND_SENTENCE)

---

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

(NOUN_VERB_CONFUSION)

---

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

(NOUN_VERB_CONFUSION)

---

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

(MD_PRP_QUESTION_MARK)

---

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

(BY_DEFAULT_COMMA)

---

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

(PRP_MD_NN)

</details>

</details>

---

`67-68`: **Fix "setup" vs "set up" usage**

"Setup" is a noun while "set up" is a verb. Fix the usage in these instances:

```diff
-navigate to the folder where you want to setup the repository
+navigate to the folder where you want to set up the repository

-commands to setup your node environment
+commands to set up your node environment

-You may not want to setup reCAPTCHA
+You may not want to set up reCAPTCHA

-If you want to setup Google reCAPTCHA now
+If you want to set up Google reCAPTCHA now

Also applies to: 123-124, 228-232

🧰 Tools

🪛 LanguageTool

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

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b465221 and 080553f.

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

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

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

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

🧰 Additional context used

📓 Learnings (1)

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

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

🪛 LanguageTool

CODE_OF_CONDUCT.md

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

(ENGLISH_WORD_REPEAT_RULE)

ISSUE_GUIDELINES.md

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

(UNLIKELY_OPENING_PUNCTUATION)

---

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

(IN_ORDER_TO_PREMIUM)

---

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

(EN_A_VS_AN)

---

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

(PLEASE_COMMA)

---

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

(AI_HYDRA_LEO_MISSING_COMMA)

---

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

(FIX_RESOLVE)

---

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

(MAKE_STYLE_BETTER)

---

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

(ON_SKYPE)

---

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

(ON_SKYPE)

---

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

(ON_SKYPE)

---

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

(PLEASE_COMMA)

README.md

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

.github/workflows/README.md

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

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)

CONTRIBUTING.md

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

(INSERT_PLEASE)

---

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

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

(THE_SUPERLATIVE)

---

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

(UNLIKELY_OPENING_PUNCTUATION)

---

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

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

(IF_THERE_COMMA)

---

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

(RB_LY_COMMA)

---

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

(FIRST_SERVED)

---

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

(ON_SKYPE)

---

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

(EN_WORDINESS_PREMIUM_LAST_BUT_NOT_THE_LEAST)

---

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

(MISSING_TO_BETWEEN_BE_AND_VB)

---

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

(ON_SKYPE)

---

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

(EN_A_VS_AN)

---

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

(DURING_THAT_TIME_COMMA)

---

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

(MAC_OS)

---

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

(BE_VBP_IN)

---

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

(ON_SKYPE)

INSTALLATION.md

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

(ENGLISH_WORD_REPEAT_RULE)

---

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

(DURING_THAT_TIME_COMMA)

---

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

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

(NOUN_VERB_CONFUSION)

---

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

(MAC_OS)

---

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

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

(MAC_OS)

---

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

(ENGLISH_WORD_REPEAT_RULE)

---

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

(MAC_OS)

---

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

(NOUN_VERB_CONFUSION)

---

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

(COMMA_COMPOUND_SENTENCE)

---

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

(NOUN_VERB_CONFUSION)

---

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

(NOUN_VERB_CONFUSION)

---

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

(MD_PRP_QUESTION_MARK)

---

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

(BY_DEFAULT_COMMA)

---

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

(PRP_MD_NN)

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)

🪛 eslint

scripts/custom-test-env.js

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

(tsdoc/syntax)

---

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

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

---

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

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

scripts/githooks/update-toc.js

[error] 11-12: Delete ··⏎

(prettier/prettier)

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)

jest.config.js

[error] 33-33: Delete ·

(prettier/prettier)

---

[error] 34-34: Insert ,

(prettier/prettier)

🪛 yamllint (1.35.1)

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

[error] 6-6: trailing spaces

(trailing-spaces)

---

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

(indentation)

---

[warning] 66-66: too many blank lines

(1 > 0) (empty-lines)

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

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 20-20: trailing spaces

(trailing-spaces)

---

[error] 21-21: trailing spaces

(trailing-spaces)

🪛 Markdownlint (0.37.0)

README.md

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

(MD019, no-multiple-space-atx)

.github/ISSUE_TEMPLATE/feature-request.md

28-28: null
Bare URL used

(MD034, no-bare-urls)

---

25-25: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

CODE_STYLE.md

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

57-57: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

73-73: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

75-75: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

92-92: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

190-190: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

230-230: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

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

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)

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)

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)

DOCUMENTATION.md

25-25: null
Bare URL used

(MD034, no-bare-urls)

🪛 Ruff (0.8.2)

.github/workflows/eslint_disable_check.py

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

Rename unused dirs to _dirs

(B007)

.github/workflows/compare_translations.py

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

(B904)

🪛 actionlint (1.7.4)

.github/workflows/codeql-codescan.yml

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

(action)

---

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

(action)

---

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

(action)

.github/workflows/issue.yml

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

(action)

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

🔇 Additional comments (39)

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

Line range hint 114-138: LGTM! LeftDrawerOrg translations are complete and consistent.

The Chinese translations for the LeftDrawerOrg component are properly implemented, including all necessary UI elements mentioned in the PR objectives.

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

Line range hint 114-138: LGTM! LeftDrawerOrg translations are complete.

The English translations for the LeftDrawerOrg component are properly implemented and match the Chinese translations.

.github/workflows/compare_translations.py (1)

185-212: Check argument validation before directory operations.
The script gracefully exits if the target directory does not exist. Consider adding a check if the user accidentally points to a file instead of a directory. This extra validation helps avoid potential misconfigurations.

setup.ts (2)

72-76: Ensure a safe exit condition in the connection loop.

The code repeats a while (!isConnected) loop until a valid endpoint is provided. If a user wishes to cancel or if an external error arises, there’s no apparent mechanism to break out of the loop gracefully. Consider adding a condition or prompt to handle exits or retries.

---

171-178: Re-run configuration after updating environment variables.

After modifying ALLOW_LOGS, subsequent logic or scripts may rely on the updated environment. Consider re-initializing dotenv.config() or otherwise ensuring that any processes that run afterward use the new value.

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

1-5: Mock implementation looks good; ensure full coverage in tests.

This straightforward Jest mock is valid. Confirm that all usage paths (e.g., different parameters) are tested, so tests accurately reflect behavior when relying on this mock.

config/vite.config.ts (1)

7-30: Consider verifying base and open configurations for production.
Ensure base and the open option align with production and CI/CD workflows. If you deploy to a subdirectory, confirm the base path is correct.

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

10-13: Warn about mismatched template and inputs usage.
Using the minimum length across template.schemas and inputs might lead to silent truncation. Consider validating that they match more strictly if that’s required by your application logic.

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

13-35: Error handling
The findTsxFiles function gracefully handles directory reading errors, logging them for visibility. This is good practice.

---

48-66: Exit process on TSDoc failures
Exiting with a non-zero status ensures CI fails if any file lacks TSDoc comments—this is a solid approach to enforce documentation coverage.

jest.config.js (5)

1-10: JSX/TSX coverage
Good coverage setup for .tsx? files and logical exclusion of index.tsx. This ensures test coverage is focused on implementation files rather than entry points.

---

11-19: Build pipeline alignment
The transformations for various file types (css, scss, etc.) are appropriately delegated to jest-preview. This neatly aligns with front-end testing best practices.

---

27-35: Module mocks
The moduleNameMapper configuration for mocking external libraries is straightforward and clear. Great job maintaining a test-friendly approach, especially for large external dependencies.

🧰 Tools

🪛 eslint

[error] 33-33: Delete ·

(prettier/prettier)

---

[error] 34-34: Insert ,

(prettier/prettier)

---

36-47: Extensive file extensions coverage
Listing web.js, web.tsx, etc. ensures thorough resolution. This is helpful for frameworks like React Native Web or other specialized bundling setups.

---

52-65: Coverage thresholds
Setting minimum coverage thresholds prompts developers to maintain a certain standard of test coverage. This is beneficial for code quality.

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

1-9: Correct usage of Node shebang
The shebang (#!/usr/bin/env node) and script arguments parsing (--scan-entire-repo) allow for flexible use in various contexts (pre-commit hook vs. full repository scan).

---

10-18: Skipping logic
Using the // SKIP_LOCALSTORAGE_CHECK directive is a non-intrusive way to selectively exclude files from the local storage check. This gives developers a quick override if needed.

🧰 Tools

🪛 eslint

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

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

---

20-37: Handling staged vs. entire repo approach
Automatically switching between scanning all .tsx? files or just staged changes is a great way to minimize overhead while still catching issues.

🧰 Tools

🪛 eslint

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

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

---

43-59: Name-based file skip
Beyond using the skip comment, the script also excludes itself and known test files. This approach is good for avoiding false positives.

🧰 Tools

🪛 eslint

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

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

---

61-78: Robust content checks
The calls to existsSync and subsequent content checks for localStorage.*Item methods ensure we catch any usage, while still handling missing files with logs.

---

80-96: Failing fast
Listing offending files and exiting with a non-zero status code is an effective approach to enforce best practices around local storage usage.

🧰 Tools

🪛 eslint

[error] 89-89: Insert ,

(prettier/prettier)

---

[error] 92-92: Insert ,

(prettier/prettier)

.github/workflows/talawa_admin_md_mdx_format_adjuster.py (4)

1-14: Comprehensive documentation
The script has a clear docstring specifying its compliance with Pylint, Pydocstyle, Pycodestyle, and Flake8. This fosters maintainability.

---

19-44: Regex-based escaping
The approach to escape special MDX characters via regex is straightforward. It handles unescaped occurrences without re-escaping existing sequences, which is important for idempotent transformations.

---

45-65: Conditional file write
Rewriting only if content differs prevents unnecessary file changes—this is considerate of version control history.

---

66-96: Bulk directory scanning
The os.walk usage ensures that all .md files are processed recursively. The script is well-structured to handle large doc directories with minimal overhead.

.github/workflows/eslint_disable_check.py (1)

45-47: Re-examine the error handling strategy.

Catching a generic exception and returning False may hide potential file-read or permission issues. Consider re-raising the exception or providing more specific handling to ensure that actual file errors are surfaced.

.coderabbit.yaml (1)

1-18: Configuration looks good!

No issues or conflicts observed. The settings appear consistent for auto-review and reviewing features.

public/manifest.json (2)

13-13: Verify potential resolution impact of reducing the icon size.

Changing the icon from "192x192" to "16x16" may not offer the best display quality on devices expecting larger icons. Confirm that this small size is intended.

---

16-16: Confirm new path for 512px icon.

Ensure that "images/logo512.png" is a valid location and that the path is correct for your deployment environment.

.gitignore (2)

13-14: LGTM! Well-structured gitignore entries

The additions follow best practices:

• Testing artifacts (coverage/, codecov)
• Environment files (.env)
• Debug logs
• Editor-specific files

Also applies to: 21-21, 31-37

---

3-5: Consider your package manager strategy

The changes look good. However, ignoring lock files (yarn.lock, pnpm-lock.yaml) while presumably using npm (since package-lock.json isn't ignored) suggests a multi-package-manager setup. This is fine if intentional, but ensure your team has agreed on a primary package manager to avoid dependency resolution conflicts.

Let's verify the package manager setup:

✅ Verification successful

Let me verify the package manager configuration further by checking the package.json scripts and dependencies:

---

Lock files are correctly ignored for npm-only setup

The verification confirms that:

• Only package-lock.json is present, indicating npm is the sole package manager in use
• No yarn or pnpm configuration files were found
• Package.json shows standard npm/node configuration with no multi-package-manager setup

The .gitignore entries for yarn.lock and pnpm-lock.yaml are actually good practice even in an npm-only project, as they prevent accidental commits if someone on the team temporarily uses a different package manager. This is a defensive approach and doesn't indicate any issues with the package manager strategy.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for presence of different package manager files
echo "Checking package manager files..."
for file in package-lock.json yarn.lock pnpm-lock.yaml; do
  if [ -f "$file" ]; then
    echo "Found: $file"
  fi
done

Length of output: 388

---

Script:

#!/bin/bash
# Check package.json for package manager related configurations
if [ -f "package.json" ]; then
    echo "Package.json contents:"
    cat package.json | grep -A 5 -B 5 "\"scripts\"\|\"packageManager\"\|\"engines\""
fi

# Look for any yarn or pnpm specific files
echo -e "\nChecking for package manager specific files:"
fd -H ".(yarn|pnpm)rc|.yarnrc.yml|pnpm-workspace.yaml"

Length of output: 1081

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

2-7: LGTM! Metadata updates improve consistency

The capitalization and label changes make the template more consistent and professional.

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

2-7: LGTM! Consistent with bug report template

The metadata changes align well with the bug report template updates.

.github/pull_request_template.md (2)

4-11: LGTM! Clear branching strategy documentation.

The added section effectively communicates the repository's branching strategy and critical PR submission requirements.

---

30-32: LGTM! Good addition of visual documentation requirements.

The new section for snapshots/videos will help reviewers better understand visual changes.

.github/workflows/stale.yml (1)

31-43: LGTM! Well-configured stale management.

The configuration provides:

• Clear messaging for stale and closed items
• Reasonable timeframes (10 days for stale, 180 for close)
• Proper exemptions for WIP items and milestones
• Sensible operation limits

.github/workflows/push.yml (1)

36-49: LGTM! Excellent caching strategy.

The caching configuration is well-structured with:

• Proper cache key based on OS and package-lock
• Appropriate fallback restore-keys
• Clear cache naming

README.md (1)

Line range hint 3-56: LGTM! Documentation improvements

The changes enhance the README's organization and clarity by:

• Adding community engagement section
• Including visual elements (logo)
• Providing structured navigation (TOC)
• Improving documentation links

🧰 Tools

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

DOCUMENTATION.md (1)

1-13: Well-structured documentation header!

The table of contents is properly formatted and provides clear navigation.

[coderabbitai]

⚠️ Potential issue

Complete Spanish translations for all messages

Most of the error messages are still in English instead of Spanish. Only the last two messages ("errorOccurredCouldntCreate" and "errorLoading") are translated.

Please translate the following messages to Spanish:

• "talawaApiUnavailable"
• "notFound"
• "unknownError"
• "notAuthorised"
• "errorSendingMail"
• "emailNotRegistered"
• "notFoundMsg"

Consider using a professional translator or native speaker to ensure accuracy.

[coderabbitai]

🛠️ Refactor suggestion

Add number formatting specifications

Consider adding number formatting specifications for numerical values to ensure consistent display across the application. This is particularly important for:

• Sort order indicators
• Currency amounts
• Contribution totals

Example implementation:

+"numberFormat": {
+  "decimal": ".",
+  "thousand": ",",
+  "currency": "₹"
+}

Also applies to: 802-802

[coderabbitai]

🛠️ Refactor suggestion

Await the async call before assertion.
The current test does not await the generate call, thus result may still be a Promise during the assertion. Use await for accuracy:

- const result = generate({
+ const result = await generate({

📝 Committable suggestion

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

Suggested change

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

[coderabbitai]

🛠️ Refactor suggestion

Consider relative module paths
While referencing absolute paths (e.g., /Users/prathamesh/...) works locally, it might cause issues on other systems. Prefer environment variables or relative paths for portability.

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

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

[coderabbitai]

⚠️ Potential issue

Remove duplicate Font Awesome CSS link

The Font Awesome CSS is linked twice. Remove the second occurrence to avoid unnecessary resource loading.

-    <link
-      rel="stylesheet"
-      href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.3/css/all.min.css"
-      referrerpolicy="no-referrer"
-    />

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

[coderabbitai]

⚠️ Potential issue

Remove duplicate type definition

The OrganizationCustomField type is defined twice with identical fields. Remove one of the duplicate definitions to maintain schema integrity.

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

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

📝 Committable suggestion

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

Suggested change

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

[coderabbitai]

⚠️ Potential issue

Remove duplicate input definition

The AddressInput input type is already defined at lines 43-52. Remove this duplicate definition.

-input AddressInput {
-  city: String
-  countryCode: String
-  dependentLocality: String
-  line1: String
-  line2: String
-  postalCode: String
-  sortingCode: String
-  state: String
-}

[coderabbitai]

⚠️ Potential issue

Remove duplicate type definition

The UserPhone type is already defined at lines 1348-1352. Remove this duplicate definition.

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

[coderabbitai]

⚠️ Potential issue

Remove duplicate enum definition

The AdvertisementType enum is already defined at lines 67-71. Remove this duplicate definition.

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

[coderabbitai]

⚠️ Potential issue

Remove duplicate enum definitions

The following enums are defined twice in the schema:

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

Remove these duplicate definitions to maintain schema integrity.

-enum EducationGrade {
-  GRADE_1
-  GRADE_2
-  GRADE_3
-  GRADE_4
-  GRADE_5
-  GRADE_6
-  GRADE_7
-  GRADE_8
-  GRADE_9
-  GRADE_10
-  GRADE_11
-  GRADE_12
-  GRADUATE
-  KG
-  NO_GRADE
-  PRE_KG
-}

-enum EmploymentStatus {
-  FULL_TIME
-  PART_TIME
-  UNEMPLOYED
-}

-enum Gender {
-  FEMALE
-  MALE
-  OTHER
-}

-enum MaritalStatus {
-  DIVORCED
-  ENGAGED
-  MARRIED
-  SEPERATED
-  SINGLE
-  WIDOWED
-}