Upgraded package react-i18next

[Suswetha6]

What kind of change does this PR introduce?
I've changed the react-i18 package from 11.18.6 to 12.3.1

Fixes #2096

Summary by CodeRabbit

• New Features

  • Introduced a structured configuration file for AI integration, enhancing automation in code reviews.
  • Added environment variable template for local development setup, streamlining configuration.
  • Implemented new GraphQL queries for organizations, plugins, fundraising, and user management, expanding data retrieval capabilities.
  • Created custom scrollbar styles for improved user experience.

• Documentation

  • Updated issue templates for bugs and feature requests to enhance clarity and usability.
  • Added guidelines for GitHub workflows and contributing to streamline development processes.

• Style

  • Established global styles and component-specific styles for improved UI consistency across the application.

[github-actions]

Our Pull Request Approval Process

We have these basic policies to make the approval process smoother for our volunteer team.

Testing Your Code

Please make sure your code passes all tests. Our test code coverage system will fail if these conditions occur:

1. The overall code coverage drops below the target threshold of the repository
2. Any file in the pull request has code coverage levels below the repository threshold
3. Merge conflicts

The process helps maintain the overall reliability of the code base and is a prerequisite for getting your PR approved. Assigned reviewers regularly review the PR queue and tend to focus on PRs that are passing.

Reviewers

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

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

Reviewing Your Code

Your reviewer(s) will have the following roles:

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

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

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

Other

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

[github-actions]

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

[coderabbitai]

Walkthrough

The changes include the introduction of new configuration files and updates to existing files that enhance the project's code review, dependency management, and styling capabilities. Key additions involve structured settings for AI-assisted code reviews, environment variable templates, updated linting rules, and styling files for various UI components, improving both the development workflow and the user interface.

Changes

File Path	Change Summary
.coderabbit.yaml	New configuration file for AI integration, specifying language settings, review options, and automation.
.env.example	New template for environment variables, detailing essential configurations for local development.
.eslintignore, .eslintrc.json	Updates to linting configuration, including new rules and exclusions for specific files.
.github/.../bug-report.md, .github/.../feature-request.md	Modifications to issue templates for improved clarity and additional sections for user guidance.
.github/dependabot.yaml	New configuration for automated dependency updates for npm packages.
.github/pull_request_template.md	Enhanced pull request template with additional prompts for contributors.
.github/workflows/...	New workflows for CodeQL scanning and documentation for managing GitHub workflows.
src/GraphQl/Queries/...	New GraphQL query files for organizations and plugins, expanding data retrieval capabilities.
src/assets/scss/...	Introduction of SCSS files for styling various UI components, establishing global styles and variables.

Assessment against linked issues

Objective	Addressed	Explanation
Upgrade package react-i18next from 11.18.6 to 12.3.1 (#[2096])	❓	The PR does not explicitly mention the upgrade.
Ensure all necessary files are updated to accommodate the upgrade (#[2096])	❓	It is unclear if all related files have been updated.

🐇✨
In the code's burrow, changes hop,
New queries and styles, a lovely crop.
Reviews automated, templates refined,
A vibrant project, all aligned!
With each commit, we leap with glee,
A thriving garden for all to see! 🌼

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as PR comments)

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

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.

[coderabbitai]

Actionable comments posted: 30

Outside diff range, codebase verification and nitpick comments (27)

src/Constant/constant.ts (1)

1-1: Consider adding a comment to explain the purpose of the constant.

The constant AUTH_TOKEN is correctly defined but might need a comment explaining its purpose.

Consider adding a comment like this:

+// Placeholder for authentication token
export const AUTH_TOKEN = '';

src/assets/scss/components/_carousel.scss (5)

1-5: Define consistent naming conventions for SCSS variables.

Ensure that the naming conventions for SCSS variables are consistent and descriptive. For example, consider using a prefix like $carousel- for all related variables.

---

7-14: Define consistent naming conventions for SCSS variables.

Ensure that the naming conventions for SCSS variables are consistent and descriptive. For example, consider using a prefix like $carousel- for all related variables.

---

16-19: Define consistent naming conventions for SCSS variables.

Ensure that the naming conventions for SCSS variables are consistent and descriptive. For example, consider using a prefix like $carousel- for all related variables.

---

21-24: Define consistent naming conventions for SCSS variables.

Ensure that the naming conventions for SCSS variables are consistent and descriptive. For example, consider using a prefix like $carousel- for all related variables.

---

26-27: Define consistent naming conventions for SCSS variables.

Ensure that the naming conventions for SCSS variables are consistent and descriptive. For example, consider using a prefix like $carousel- for all related variables.

README.md (1)

55-56: LGTM!

The videos section is correctly expanded, providing valuable resources for new contributors. Consider adding a hyphen in "new open source contributors" for grammatical correctness.

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

Tools

LanguageTool

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

src/App.tsx (1)

51-185: Update references from App to app.

The function App has been renamed to app, but references to App remain in the codebase. Please update the following instances to ensure consistency:

• src/index.tsx: Update the import and usage of App.
• src/App.test.tsx: Update the import and usage of App.

Analysis chain

Verify the function usage in the codebase.

The function App has been renamed to app. Ensure that all references to the App component are updated accordingly.

Run the following script to verify the function usage:

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify all references to the `App` component are updated to `app`.

# Test: Search for the function usage. Expect: Only occurrences of the new name.
rg --type js --type tsx -A 5 $'App'

Length of output: 62

---

Script:

#!/bin/bash
# Description: Verify all references to the `App` component are updated to `app`.

# Test: Search for the function usage. Expect: Only occurrences of the new name.
rg --type-add 'tsx:*.tsx' --type js --type tsx -A 5 $'App'

Length of output: 8182

CODE_STYLE.md (5)

127-137: Stylistic improvements: Remove unnecessary "of" for conciseness.

Consider removing “of” to be more concise.

Apply this diff to improve conciseness:

- `assets` - This houses all of the static assets used in the project
- `css` - This houses all of the css files used in the project
- `images` - This houses all of the images used in the project
- `scss` - This houses all of the scss files used in the project
+ `assets` - This houses all the static assets used in the project
+ `css` - This houses all the css files used in the project
+ `images` - This houses all the images used in the project
+ `scss` - This houses all the scss files used in the project

Tools

LanguageTool

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

Markdownlint

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)

---

141-149: Stylistic improvements: Remove unnecessary "of" for conciseness.

Consider removing “of” to be more concise.

Apply this diff to improve conciseness:

- `Constant` - This houses all of the constants used in the project
- `GraphQl` - This houses all of the GraphQL queries and mutations used in the project
- `screens` - This houses all of the views/screens to be navigated through in Talawa-Admin
- `state` - This houses all of the state management code for the project
+ `Constant` - This houses all the constants used in the project
+ `GraphQl` - This houses all the GraphQL queries and mutations used in the project
+ `screens` - This houses all the views/screens to be navigated through in Talawa-Admin
+ `state` - This houses all the state management code for the project

Tools

LanguageTool

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

---

190-211: Use headings instead of emphasis.

Emphasis is used instead of headings. Consider using headings for better readability.

Apply this diff to use headings:

- **File Structure**
+ ## File Structure

Tools

Markdownlint

190-190: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

230-253: Use headings instead of emphasis.

Emphasis is used instead of headings. Consider using headings for better readability.

Apply this diff to use headings:

- **How to compile Sass file**
+ ## How to compile Sass file

Tools

Markdownlint

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)

---

239-253: Specify language for fenced code blocks.

Fenced code blocks should have a language specified for better syntax highlighting.

Apply this diff to specify the language:

- ```
+ ```bash

Tools

Markdownlint

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

CONTRIBUTING.md (3)

27-30: Grammatical improvement: Add "please" for politeness.

Consider adding “please” to be more polite.

Apply this diff to improve politeness:

- Let us know immediately if you have unacceptable experiences in this area.
+ Please let us know immediately if you have unacceptable experiences in this area.

Tools

LanguageTool

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

---

37-47: Grammatical improvement: Use hyphen for compound adjective.

Consider using a hyphen for the compound adjective “open-source”.

Apply this diff to improve grammar:

- extremely helpful for new open source contributors.
+ extremely helpful for new open-source contributors.

---

65-68: Grammatical improvement: Use hyphen for compound adjective.

Consider using a hyphen for the compound adjective “production-ready”.

Apply this diff to improve grammar:

- Where the stable production ready code lies.
+ Where the stable production-ready code lies.

Tools

LanguageTool

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

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~68-~68: 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)

schema.graphql (8)

5-20: Consider adding descriptions for the fields.

The type ActionItem is well-defined, but adding descriptions for the fields would improve clarity and documentation.

Add descriptions for the fields to enhance documentation.

---

22-30: Consider adding descriptions for the fields.

The type ActionItemCategory is well-defined, but adding descriptions for the fields would improve clarity and documentation.

Add descriptions for the fields to enhance documentation.

---

32-41: Consider adding descriptions for the fields.

The type Address is well-defined, but adding descriptions for the fields would improve clarity and documentation.

Add descriptions for the fields to enhance documentation.

---

43-52: Consider adding descriptions for the fields.

The input AddressInput is well-defined, but adding descriptions for the fields would improve clarity and documentation.

Add descriptions for the fields to enhance documentation.

---

54-65: Consider adding descriptions for the fields.

The type Advertisement is well-defined, but adding descriptions for the fields would improve clarity and documentation.

Add descriptions for the fields to enhance documentation.

---

73-76: Consider adding descriptions for the fields.

The type AdvertisementEdge is well-defined, but adding descriptions for the fields would improve clarity and documentation.

Add descriptions for the fields to enhance documentation.

---

78-82: Consider adding descriptions for the fields.

The type AdvertisementsConnection is well-defined, but adding descriptions for the fields would improve clarity and documentation.

Add descriptions for the fields to enhance documentation.

---

84-93: Consider adding descriptions for the fields.

The type AgendaCategory is well-defined, but adding descriptions for the fields would improve clarity and documentation.

Add descriptions for the fields to enhance documentation.

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

2-25: Fix typographical errors.

There are some typographical errors in the values. Apply this diff to fix them:

- "atleast_8_char_long": "Atleast 8 Character long",
+ "atleast_8_char_long": "At least 8 characters long",
- "atleast_6_char_long": "Atleast 6 Character long",
+ "atleast_6_char_long": "At least 6 characters long",
- "Password_and_Confirm_password_mismatches.": "Password and Confirm password mismatches.",
+ "Password_and_Confirm_password_mismatch": "Password and Confirm password mismatch.",
- "Something_went_wrong": "Something went wrong, Please try after sometime.",
+ "Something_went_wrong": "Something went wrong, Please try again later.",
- "lowercase_check": "Atleast one lowercase letter",
+ "lowercase_check": "At least one lowercase letter",
- "uppercase_check": "Atleast one uppercase letter",
+ "uppercase_check": "At least one uppercase letter",
- "numeric_value_check": "Atleaset one numeric value",
+ "numeric_value_check": "At least one numeric value",
- "special_char_check": "Atleast one special character",
+ "special_char_check": "At least one special character"

---

27-41: Fix typographical errors.

There are some typographical errors in the values. Apply this diff to fix them:

- "atleast_8_char_long": "Atleast 8 Character long",
+ "atleast_8_char_long": "At least 8 characters long",
- "Password_and_Confirm_password_mismatches.": "Password and Confirm password mismatches.",
+ "Password_and_Confirm_password_mismatch": "Password and Confirm password mismatch.",
- "Something_went_wrong": "Something went wrong, Please try after sometime.",
+ "Something_went_wrong": "Something went wrong, Please try again later."

---

80-108: Fix typographical error.

There is a typographical error in one of the values. Apply this diff to fix it:

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

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 75d2e55 and 122e885.

Files ignored due to path filters (68)

• 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/profiledefault.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/defaultImg.png is excluded by !**/*.png
• src/assets/images/palisadoes_logo.png is excluded by !**/*.png
• src/assets/images/talawa-logo-200x200.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/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/angleLeft.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/eventDashboard.svg is excluded by !**/*.svg
• src/assets/svgs/eventStats.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/Twitter-Logo.svg is excluded by !**/*.svg
• src/assets/svgs/social-icons/Youtube-Logo.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 (103)

• .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/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/md_mdx_format_adjuster.py (1 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)
• .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)
• INSTALLATION.md (1 hunks)
• ISSUE_GUIDELINES.md (1 hunks)
• PR_GUIDELINES.md (1 hunks)
• README.md (3 hunks)
• jest-preview.config.ts (1 hunks)
• jest.config.js (1 hunks)
• package.json (2 hunks)
• public/index.html (1 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/config-overrides/custom_build.js (1 hunks)
• scripts/config-overrides/custom_start.js (1 hunks)
• scripts/config-overrides/index.js (1 hunks)
• scripts/config-overrides/package.json (1 hunks)
• scripts/custom-test-env.js (1 hunks)
• scripts/githooks/check-localstorage-usage.js (1 hunks)
• scripts/githooks/update-toc.js (1 hunks)
• scripts/test.js (1 hunks)
• setup.ts (1 hunks)
• src/App.test.tsx (1 hunks)
• src/App.tsx (1 hunks)
• src/Constant/constant.spec.ts (1 hunks)
• src/Constant/constant.ts (1 hunks)
• src/GraphQl/Mutations/ActionItemCategoryMutations.ts (1 hunks)
• src/GraphQl/Mutations/ActionItemMutations.ts (1 hunks)
• src/GraphQl/Mutations/AgendaCategoryMutations.ts (1 hunks)
• src/GraphQl/Mutations/AgendaItemMutations.ts (1 hunks)
• src/GraphQl/Mutations/CampaignMutation.ts (1 hunks)
• src/GraphQl/Mutations/CommentMutations.ts (1 hunks)
• src/GraphQl/Mutations/EventAttendeeMutations.ts (1 hunks)
• src/GraphQl/Mutations/FundMutation.ts (1 hunks)
• src/GraphQl/Mutations/OrganizationMutations.ts (1 hunks)
• src/GraphQl/Mutations/PledgeMutation.ts (1 hunks)
• src/GraphQl/Mutations/VenueMutations.ts (1 hunks)
• src/GraphQl/Mutations/mutations.ts (1 hunks)
• src/GraphQl/Queries/ActionItemCategoryQueries.ts (1 hunks)
• src/GraphQl/Queries/ActionItemQueries.ts (1 hunks)
• src/GraphQl/Queries/AgendaCategoryQueries.ts (1 hunks)
• src/GraphQl/Queries/AgendaItemQueries.ts (1 hunks)
• src/GraphQl/Queries/OrganizationQueries.ts (1 hunks)
• src/GraphQl/Queries/PlugInQueries.ts (1 hunks)
• src/GraphQl/Queries/Queries.ts (1 hunks)
• src/GraphQl/Queries/fundQueries.ts (1 hunks)
• src/assets/css/scrollStyles.css (1 hunks)
• src/assets/scss/_general.scss (1 hunks)
• src/assets/scss/_talawa.scss (1 hunks)
• src/assets/scss/_variables.scss (1 hunks)
• src/assets/scss/app.scss (1 hunks)
• src/assets/scss/components/_accordion.scss (1 hunks)
• src/assets/scss/components/_alert.scss (1 hunks)
• src/assets/scss/components/_badge.scss (1 hunks)
• src/assets/scss/components/_breadcrumb.scss (1 hunks)
• src/assets/scss/components/_buttons.scss (1 hunks)
• src/assets/scss/components/_card.scss (1 hunks)
• src/assets/scss/components/_carousel.scss (1 hunks)

Files not processed due to max files limit (43)

• src/assets/scss/components/_close.scss
• src/assets/scss/components/_dropdown.scss
• src/assets/scss/components/_list-group.scss
• src/assets/scss/components/_modal.scss
• src/assets/scss/components/_nav.scss
• src/assets/scss/components/_navbar.scss
• src/assets/scss/components/_offcanvas.scss
• src/assets/scss/components/_pagination.scss
• src/assets/scss/components/_placeholder.scss
• src/assets/scss/components/_progress.scss
• src/assets/scss/components/_spinners.scss
• src/assets/scss/content/_table.scss
• src/assets/scss/content/_typography.scss
• src/assets/scss/forms/_check-radios.scss
• src/assets/scss/forms/_floating-label.scss
• src/assets/scss/forms/_form-control.scss
• src/assets/scss/forms/_input-group.scss
• src/assets/scss/forms/_range.scss
• src/assets/scss/forms/_select.scss
• src/assets/scss/forms/_validation.scss
• src/assets/svgs/social-icons/index.tsx
• src/components/ActionItems/ActionItemsContainer.module.css
• src/components/ActionItems/ActionItemsContainer.test.tsx
• src/components/ActionItems/ActionItemsContainer.tsx
• src/components/ActionItems/ActionItemsContainerMocks.ts
• src/components/ActionItems/ActionItemsContainerProps.ts
• src/components/ActionItems/ActionItemsModal.test.tsx
• src/components/ActionItems/ActionItemsModal.tsx
• src/components/ActionItems/ActionItemsModalBody.tsx
• src/components/ActionItems/ActionItemsWrapper.module.css
• src/components/ActionItems/ActionItemsWrapper.test.tsx
• src/components/ActionItems/ActionItemsWrapper.tsx
• src/components/AddOn/AddOn.test.tsx
• src/components/AddOn/AddOn.tsx
• src/components/AddOn/core/AddOnEntry/AddOnEntry.module.css
• src/components/AddOn/core/AddOnEntry/AddOnEntry.test.tsx
• src/components/AddOn/core/AddOnEntry/AddOnEntry.tsx
• src/components/AddOn/core/AddOnEntry/AddOnEntryMocks.ts
• src/components/AddOn/core/AddOnRegister/AddOnRegister.module.css
• src/components/AddOn/core/AddOnRegister/AddOnRegister.test.tsx
• src/components/AddOn/core/AddOnRegister/AddOnRegister.tsx
• src/components/AddOn/core/AddOnStore/AddOnStore.module.css
• src/components/AddOn/core/AddOnStore/AddOnStore.test.tsx

Files skipped from review due to trivial changes (25)

• .env.example
• .eslintignore
• .github/ISSUE_TEMPLATE/feature-request.md
• .github/dependabot.yaml
• .github/workflows/README.md
• .husky/post-merge
• .husky/pre-commit
• .lintstagedrc.json
• .node-version
• .prettierignore
• CODEOWNERS
• public/locales/en/errors.json
• public/locales/fr/common.json
• public/locales/fr/errors.json
• public/locales/hi/common.json
• public/locales/zh/common.json
• scripts/mocks/@dicebear/collection.ts
• scripts/mocks/@dicebear/core.ts
• scripts/config-overrides/package.json
• src/assets/css/scrollStyles.css
• src/assets/scss/_general.scss
• src/assets/scss/_talawa.scss
• src/assets/scss/_variables.scss
• src/assets/scss/components/_alert.scss
• src/assets/scss/components/_badge.scss

Additional context used

Learnings (2)

src/GraphQl/Mutations/FundMutation.ts (2)

Learnt from: GlenDsza
PR: PalisadoesFoundation/talawa-admin#2064
File: src/screens/OrganizationFunds/FundDeleteModal.tsx:1-2
Timestamp: 2024-06-30T21:44:39.912Z
Learning: The folder containing mutation queries in the codebase is named `GraphQl`, not `graphql`.

Learnt from: GlenDsza
PR: PalisadoesFoundation/talawa-admin#2064
File: src/screens/OrganizationFundCampaign/CampaignDeleteModal.tsx:4-5
Timestamp: 2024-06-30T21:17:16.481Z
Learning: The folder containing mutation queries in the codebase is named `GraphQl`, not `graphql`.

src/GraphQl/Mutations/CampaignMutation.ts (1)

Learnt from: GlenDsza
PR: PalisadoesFoundation/talawa-admin#2064
File: src/screens/OrganizationFundCampaign/CampaignDeleteModal.tsx:4-5
Timestamp: 2024-06-30T21:17:16.481Z
Learning: The folder containing mutation queries in the codebase is named `GraphQl`, not `graphql`.

Biome

scripts/test.js

[error] 1-1: Redundant use strict directive.

The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.

(lint/suspicious/noRedundantUseStrict)

LanguageTool

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)

ISSUE_GUIDELINES.md

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

(UNLIKELY_OPENING_PUNCTUATION)

---

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

(IN_ORDER_TO_PREMIUM)

---

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

(EN_A_VS_AN)

---

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

(PLEASE_COMMA)

---

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

(FIX_RESOLVE)

---

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

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)

CODE_OF_CONDUCT.md

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

(ENGLISH_WORD_REPEAT_RULE)

CODE_STYLE.md

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

(ALL_OF_THE)

---

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

(ALL_OF_THE)

---

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

(ALL_OF_THE)

---

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

(ALL_OF_THE)

---

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

(HE_VERB_AGR)

---

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

(HE_VERB_AGR)

---

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

(HE_VERB_AGR)

---

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

(ALL_OF_THE)

---

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

(ALL_OF_THE)

---

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

(ALL_OF_THE)

---

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

(ALL_OF_THE)

---

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

CONTRIBUTING.md

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

(INSERT_PLEASE)

---

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

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

(THE_SUPERLATIVE)

---

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

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~68-~68: 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] ~72-~72: Consider adding a comma.
Context: ...ultiple developers are working on issues there is bound to be a conflict of interest (...

(IF_THERE_COMMA)

---

[typographical] ~72-~72: 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] ~72-~72: 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)

---

[uncategorized] ~72-~72: Possible missing comma found.
Context: ...esolved in a First Come First Serve basis however there are certain exceptions to...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[uncategorized] ~74-~74: Possible missing comma found.
Context: ... an extension or in conflict with other PRs it is important to ask the author of th...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[grammar] ~74-~74: 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] ~76-~76: ‘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] ~76-~76: 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] ~76-~76: 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] ~76-~76: 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] ~77-~77: 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] ~134-~134: The operating system from Apple is written “macOS”.
Context: ...r packages can be found for Windows and MacOS. 6. The currently acceptable c...

(MAC_OS)

---

[uncategorized] ~163-~163: Possible missing comma found.
Context: ...o add all changes). 1. After adding the changes you need to commit them using `git comm...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[grammar] ~164-~164: 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] ~177-~177: 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] ~24-~24: Possible typo: you repeated a word
Context: ...](#running-talawa-admin) - Accessing Talawa-Admin - [Talawa-Admin Registration](#talawa-admin-registratio...

(ENGLISH_WORD_REPEAT_RULE)

---

[typographical] ~54-~54: 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] ~60-~60: 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] ~66-~66: 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] ~67-~67: 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] ~69-~69: 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] ~98-~98: 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] ~112-~112: Possible typo: you repeated a word
Context: ... 5. Save the document. 6. Exit notepad 7. Exit PowerShell 8. This will ens...

(ENGLISH_WORD_REPEAT_RULE)

---

[grammar] ~115-~115: 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] ~119-~119: 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 ...

(NOUN_VERB_CONFUSION)

---

[uncategorized] ~158-~158: 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] ~203-~203: 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] ~207-~207: 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] ~221-~221: 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] ~236-~236: 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] ~286-~286: 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)

Markdownlint

DOCUMENTATION.md

25-25: null
Bare URL used

(MD034, no-bare-urls)

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)

CODE_STYLE.md

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

57-57: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

73-73: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

75-75: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

92-92: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

190-190: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

230-230: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

CONTRIBUTING.md

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

157-157: null
No empty links

(MD042, no-empty-links)

---

158-158: null
No empty links

(MD042, no-empty-links)

---

160-160: null
No empty links

(MD042, no-empty-links)

INSTALLATION.md

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

(MD001, heading-increment)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD014, commands-show-output)

---

101-101: null
Bare URL used

(MD034, no-bare-urls)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD046, code-block-style)

---

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

(MD046, code-block-style)

---

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

---

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

actionlint

.github/workflows/push.yml

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

(shellcheck)

---

128-128: shellcheck reported issue in this script: SC2046:warning:1:24: Quote this to prevent word splitting

(shellcheck)

---

128-128: shellcheck reported issue in this script: SC2005:style:1:24: Useless echo? Instead of 'echo $(cmd)', just use 'cmd'

(shellcheck)

---

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

(shellcheck)

---

128-128: shellcheck reported issue in this script: SC2046:warning:2:20: Quote this to prevent word splitting

(shellcheck)

---

128-128: shellcheck reported issue in this script: SC2005:style:2:20: Useless echo? Instead of 'echo $(cmd)', just use 'cmd'

(shellcheck)

---

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

(shellcheck)

---

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

(shellcheck)

---

145-145: the runner of "actions/upload-artifact@v2" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

.github/workflows/pull-request.yml

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

(expression)

---

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

(shellcheck)

---

73-73: "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)

---

190-190: shellcheck reported issue in this script: SC2043:warning:1:13: This loop will only ever run once. Bad quoting or missing glob/expansion?

(shellcheck)

Additional comments not posted (377)

.prettierrc (1)

2-3: LGTM!

The addition of "endOfLine": "auto" improves compatibility across different operating systems.

The code changes are approved.

jest-preview.config.ts (1)

1-5: LGTM!

The Jest configuration correctly maps module names starting with @mui/ to the corresponding directory in node_modules.

The code changes are approved.

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

1-10: LGTM!

The translations are correctly formatted and provide meaningful error messages in Chinese.

The code changes are approved.

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

1-2: LGTM!

The imports are correct and necessary for the script's functionality.

The code changes are approved.

---

4-6: LGTM!

The code correctly reads and filters markdown files in the current directory.

The code changes are approved.

---

8-12: LGTM!

The code correctly updates the table of contents for each markdown file using markdown-toc.

The code changes are approved.

---

14-14: LGTM!

The success message is appropriate and informative.

The code changes are approved.

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

2-2: LGTM!

The translation for talawaApiUnavailable is correct and appropriate.

The code changes are approved.

---

3-3: LGTM!

The translation for notFound is correct and appropriate.

The code changes are approved.

---

4-4: LGTM!

The translation for unknownError is correct and appropriate.

The code changes are approved.

---

5-5: LGTM!

The translation for notAuthorised is correct and appropriate.

The code changes are approved.

---

6-6: LGTM!

The translation for errorSendingMail is correct and appropriate.

The code changes are approved.

---

7-7: LGTM!

The translation for emailNotRegistered is correct and appropriate.

The code changes are approved.

---

8-8: LGTM!

The translation for notFoundMsg is correct and appropriate.

The code changes are approved.

---

9-9: LGTM!

The translation for errorOccurredCouldntCreate is correct and appropriate.

The code changes are approved.

src/Constant/constant.ts (5)

2-2: LGTM!

The constant BACKEND_URL is correctly defined.

The code changes are approved.

---

3-3: LGTM!

The constant RECAPTCHA_SITE_KEY is correctly defined.

The code changes are approved.

---

4-4: LGTM!

The constant REACT_APP_USE_RECAPTCHA is correctly defined.

The code changes are approved.

---

5-5: LGTM!

The constant REACT_APP_CUSTOM_PORT is correctly defined.

The code changes are approved.

---

6-7: LGTM!

The constant REACT_APP_BACKEND_WEBSOCKET_URL is correctly defined.

The code changes are approved.

.coderabbit.yaml (12)

2-2: LGTM!

The language setting is correctly configured.

The code changes are approved.

---

3-3: LGTM!

The early access setting is correctly configured.

The code changes are approved.

---

5-5: LGTM!

The profile setting is correctly configured.

The code changes are approved.

---

6-6: LGTM!

The request changes workflow setting is correctly configured.

The code changes are approved.

---

7-7: LGTM!

The high level summary setting is correctly configured.

The code changes are approved.

---

8-8: LGTM!

The poem setting is correctly configured.

The code changes are approved.

---

9-9: LGTM!

The review status setting is correctly configured.

The code changes are approved.

---

10-10: LGTM!

The collapse walkthrough setting is correctly configured.

The code changes are approved.

---

12-12: LGTM!

The enabled setting is correctly configured.

The code changes are approved.

---

13-13: LGTM!

The drafts setting is correctly configured.

The code changes are approved.

---

14-15: LGTM!

The base branches setting is correctly configured.

The code changes are approved.

---

16-17: LGTM!

The chat setting is correctly configured.

The code changes are approved.

src/assets/scss/components/_breadcrumb.scss (11)

1-1: LGTM!

The $breadcrumb-font-size variable is correctly configured.

The code changes are approved.

---

2-2: LGTM!

The $breadcrumb-padding-y variable is correctly configured.

The code changes are approved.

---

3-3: LGTM!

The $breadcrumb-padding-x variable is correctly configured.

The code changes are approved.

---

4-4: LGTM!

The $breadcrumb-item-padding-x variable is correctly configured.

The code changes are approved.

---

5-5: LGTM!

The $breadcrumb-margin-bottom variable is correctly configured.

The code changes are approved.

---

6-6: LGTM!

The $breadcrumb-bg variable is correctly configured.

The code changes are approved.

---

7-7: LGTM!

The $breadcrumb-divider-color variable is correctly configured.

The code changes are approved.

---

8-8: LGTM!

The $breadcrumb-active-color variable is correctly configured.

The code changes are approved.

---

9-9: LGTM!

The $breadcrumb-divider variable is correctly configured.

The code changes are approved.

---

10-10: LGTM!

The $breadcrumb-divider-flipped variable is correctly configured.

The code changes are approved.

---

11-11: LGTM!

The $breadcrumb-border-radius variable is correctly configured.

The code changes are approved.

public/manifest.json (2)

13-13: Verify the impact of the size change.

The size attribute for logo192.png has been changed from "192x192" to "16x16". Ensure that this change does not negatively impact the application's display of the image.

---

16-16: Verify the impact of the source path change.

The source path for logo512.png has been changed from "logo512.png" to "images/logo512.png". Ensure that this change does not negatively impact the application's reference to the image.

.gitignore (4)

3-5: LGTM!

The new entries for package manager lock files are appropriate.

The code changes are approved.

---

13-14: LGTM!

The new entries for testing coverage reports and related files are appropriate.

The code changes are approved.

---

Line range hint 21-26: LGTM!

The new entries for environment configuration files are appropriate.

The code changes are approved.

---

35-37: LGTM!

The new entries for development environment files and temporary swap files are appropriate.

The code changes are approved.

scripts/config-overrides/custom_build.js (2)

1-3: LGTM!

The initial setup correctly imports necessary modules.

The code changes are approved.

---

4-9: LGTM!

The default and custom build commands are correctly defined.

The code changes are approved.

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

2-2: LGTM!

The error message for talawaApiUnavailable is correctly translated and appropriate.

The code changes are approved.

---

3-3: LGTM!

The error message for notFound is correctly translated and appropriate.

The code changes are approved.

---

4-4: LGTM!

The error message for unknownError is correctly translated and appropriate.

The code changes are approved.

---

5-5: LGTM!

The error message for notAuthorised is correctly translated and appropriate.

The code changes are approved.

---

6-6: LGTM!

The error message for errorSendingMail is correctly translated and appropriate.

The code changes are approved.

---

7-7: LGTM!

The error message for emailNotRegistered is correctly translated and appropriate.

The code changes are approved.

---

8-8: LGTM!

The error message for notFoundMsg is correctly translated and appropriate.

The code changes are approved.

---

9-9: LGTM!

The error message for errorOccurredCouldntCreate is correctly translated and appropriate.

The code changes are approved.

src/assets/scss/app.scss (7)

2-2: LGTM!

The import statement for Bootstrap SCSS functions is correct.

The code changes are approved.

---

3-3: LGTM!

The import statement for Bootstrap SCSS mixins is correct.

The code changes are approved.

---

6-6: LGTM!

The import statement for custom SCSS variables is correct.

The code changes are approved.

---

9-9: LGTM!

The import statement for Bootstrap SCSS variables is correct.

The code changes are approved.

---

10-10: LGTM!

The import statement for Bootstrap SCSS variables-dark is correct.

The code changes are approved.

---

11-11: LGTM!

The import statement for Bootstrap SCSS is correct.

The code changes are approved.

---

14-14: LGTM!

The import statement for custom SCSS overrides is correct.

The code changes are approved.

src/GraphQl/Queries/ActionItemCategoryQueries.ts (2)

1-1: LGTM!

The import statement for graphql-tag is correct.

The code changes are approved.

---

10-18: LGTM!

The GraphQL query ACTION_ITEM_CATEGORY_LIST is correctly defined and includes necessary fields.

The code changes are approved.

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

1-1: LGTM!

The import statement for jest-environment-jsdom is correct.

The code changes are approved.

---

2-2: LGTM!

The import statement for TextEncoder and TextDecoder from util is correct.

The code changes are approved.

---

8-16: LGTM!

The class CustomTestEnvironment is correctly implemented and necessary for providing a polyfill for TextEncoder and TextDecoder.

The code changes are approved.

scripts/config-overrides/custom_start.js (4)

1-3: LGTM!

The code correctly loads environment variables and imports the necessary module for spawning child processes.

The code changes are approved.

---

4-6: LGTM!

The code correctly sets a default value for the PORT environment variable.

The code changes are approved.

---

7-9: LGTM!

The code correctly defines the commands for starting the application.

The code changes are approved.

---

10-19: LGTM!

The code correctly uses the spawn function to execute the commands based on the value of the ALLOW_LOGS environment variable.

The code changes are approved.

src/GraphQl/Queries/AgendaCategoryQueries.ts (3)

1-2: LGTM!

The code correctly imports the gql function.

The code changes are approved.

---

3-9: LGTM!

The JSDoc comment is well-written and provides useful information about the query.

The code changes are approved.

---

10-23: LGTM!

The query is correctly defined and follows best practices for GraphQL queries.

The code changes are approved.

src/GraphQl/Mutations/AgendaItemMutations.ts (4)

1-2: LGTM!

The code correctly imports the gql function.

The code changes are approved.

---

3-10: LGTM!

The mutation is correctly defined and follows best practices for GraphQL mutations.

The code changes are approved.

---

12-18: LGTM!

The mutation is correctly defined and follows best practices for GraphQL mutations.

The code changes are approved.

---

20-31: LGTM!

The mutation is correctly defined and follows best practices for GraphQL mutations.

The code changes are approved.

src/assets/scss/components/_card.scss (1)

1-19: LGTM!

The SCSS variables for card components are well-defined and follow a consistent naming convention.

The code changes are approved.

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

2-6: LGTM!

The changes to the title, labels, and assignees improve consistency and follow typical conventions in issue tracking systems.

The code changes are approved.

---

31-34: LGTM!

The new sections "Additional details" and "Potential internship candidates" enhance the template by providing additional context and relevant information for users.

The code changes are approved.

scripts/config-overrides/index.js (1)

1-29: LGTM!

The webpack configuration overrides are well-structured and add useful logging and progress tracking features to the webpack build process.

The code changes are approved.

src/Constant/constant.spec.ts (4)

9-12: LGTM!

The test for AUTH_TOKEN is correctly implemented.

The code changes are approved.

---

14-16: LGTM!

The test for BACKEND_URL is correctly implemented.

The code changes are approved.

---

18-22: LGTM!

The test for RECAPTCHA_SITE_KEY is correctly implemented.

The code changes are approved.

---

24-28: LGTM!

The test for REACT_APP_USE_RECAPTCHA is correctly implemented.

The code changes are approved.

public/index.html (5)

5-5: LGTM!

The favicon link change to favicon_palisadoes.ico is likely part of a rebranding or visual update.

The code changes are approved.

---

8-8: LGTM!

The apple touch icon link change to point back to favicon.ico may suggest a simplification or standardization of icon usage across different platforms.

The code changes are approved.

---

10-11: LGTM!

The addition of preconnect directives for Google Fonts and its associated font files optimizes loading times.

The code changes are approved.

---

12-15: LGTM!

The addition of the Google Fonts stylesheet link for the "Outfit" font family enhances typographic options for the site.

The code changes are approved.

---

16-21: Remove duplicate Font Awesome stylesheet link.

Two identical links to Font Awesome's CSS library have been added. The duplicate link should be removed to avoid unnecessary resource loading.

Apply this diff to remove the duplicate link:

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

src/GraphQl/Mutations/ActionItemCategoryMutations.ts (2)

10-16: LGTM!

The CREATE_ACTION_ITEM_CATEGORY_MUTATION is correctly implemented.

The code changes are approved.

---

26-39: LGTM!

The UPDATE_ACTION_ITEM_CATEGORY_MUTATION is correctly implemented.

The code changes are approved.

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

1-13: LGTM!

The header and workflow name are informative and descriptive.

The code changes are approved.

---

14-20: LGTM!

The triggers are correctly defined to ensure code scanning on all branches.

The code changes are approved.

---

21-28: LGTM!

The job definition is correctly set up for CodeQL analysis.

The code changes are approved.

---

29-43: LGTM!

The steps are correctly defined for the CodeQL analysis workflow.

The code changes are approved.

src/GraphQl/Mutations/AgendaCategoryMutations.ts (3)

9-15: LGTM!

The mutation is correctly defined with the necessary input parameters.

The code changes are approved.

---

23-27: LGTM!

The mutation is correctly defined with the necessary ID parameter.

The code changes are approved.

---

36-45: LGTM!

The mutation is correctly defined with the necessary ID and input parameters.

The code changes are approved.

src/GraphQl/Mutations/CommentMutations.ts (3)

11-28: LGTM!

The mutation is correctly defined with the necessary parameters.

The code changes are approved.

---

37-43: LGTM!

The mutation is correctly defined with the necessary ID parameter.

The code changes are approved.

---

52-58: LGTM!

The mutation is correctly defined with the necessary ID parameter.

The code changes are approved.

src/GraphQl/Queries/AgendaItemQueries.ts (2)

1-37: LGTM!

The AgendaItemByOrganization query is well-structured and follows GraphQL syntax correctly.

The code changes are approved.

---

39-73: LGTM!

The AgendaItemByEvent query is well-structured and follows GraphQL syntax correctly.

The code changes are approved.

.github/workflows/issue.yml (2)

1-26: LGTM!

The Opened-issue-label job is correctly configured to add a label to newly opened issues. The upgrade to auto-label action version v2.3.0 is appropriate.

The code changes are approved.

---

27-34: LGTM!

The Issue-Greeting job is correctly configured to send a greeting message to users when they create their first issue. The use of the first-interaction action is appropriate.

The code changes are approved.

scripts/test.js (6)

3-6: LGTM!

The environment variable setup is correct and necessary for the testing environment.

The code changes are approved.

---

8-13: LGTM!

The handling of unhandled promise rejections is correct and improves the robustness of the script.

The code changes are approved.

---

15-16: LGTM!

The import of react-scripts/config/env.js is correct and necessary for reading environment variables.

The code changes are approved.

---

18-19: LGTM!

The imports of jest and execSync are correct and necessary for running tests and executing commands.

The code changes are approved.

---

23-39: LGTM!

The checks for Git and Mercurial repositories are correct and necessary for determining the watch mode.

The code changes are approved.

---

41-52: LGTM!

The setup for watch mode and running tests using jest is correct and necessary for the testing workflow.

The code changes are approved.

src/GraphQl/Mutations/EventAttendeeMutations.ts (3)

11-17: LGTM! But ensure parameter validation and sanitization.

The mutation is correctly implemented. However, ensure that userId and eventId are validated and sanitized before being used.

---

27-33: LGTM! But ensure parameter validation and sanitization.

The mutation is correctly implemented. However, ensure that userId and eventId are validated and sanitized before being used.

---

43-49: LGTM! But ensure parameter validation and sanitization.

The mutation is correctly implemented. However, ensure that userId and eventId are validated and sanitized before being used.

.github/pull_request_template.md (2)

1-12: LGTM!

The section provides clear guidelines on the branching strategy and submission instructions.

---

Line range hint 14-53: LGTM!

The section provides clear and important prompts for contributors to ensure comprehensive information is provided.

DOCUMENTATION.md (4)

1-2: LGTM!

The introduction is clear and concise.

The section is approved.

---

4-12: LGTM!

The table of contents is clear and well-structured.

The section is approved.

---

14-19: LGTM!

The information on where to find the documentation is clear and well-structured.

The section is approved.

---

31-32: Fix grammatical issue.

The section is well-structured but needs a grammatical correction.

Apply this diff to fix the issue:

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

Likely invalid or redundant comment.

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)

src/GraphQl/Mutations/VenueMutations.ts (3)

1-33: LGTM!

The mutation is correctly implemented and well-documented.

The mutation is approved.

---

35-65: LGTM!

The mutation is correctly implemented and well-documented.

The mutation is approved.

---

67-79: LGTM!

The mutation is correctly implemented and well-documented.

The mutation is approved.

src/GraphQl/Queries/fundQueries.ts (3)

1-37: LGTM!

The query is correctly implemented and well-documented.

The query is approved.

---

39-56: LGTM!

The query is correctly implemented and well-documented.

The query is approved.

---

58-81: LGTM!

The query is correctly implemented and well-documented.

The query is approved.

src/assets/scss/components/_accordion.scss (4)

1-11: LGTM!

The SCSS variables for accordion padding, color, background, border width, border color, and border radius are well-defined.

The code changes are approved.

---

13-17: LGTM!

The SCSS variables for accordion body padding and button padding are consistent and well-defined.

The code changes are approved.

---

18-27: LGTM!

The SCSS variables for accordion button color, background, transition, active background, active color, focus border color, and focus box shadow are well-defined.

The code changes are approved.

---

29-36: LGTM!

The SCSS variables for accordion icon width, color, active color, transition, transform, and button icon URLs are well-defined.

The code changes are approved.

.github/workflows/stale.yml (4)

1-11: LGTM!

The comments are clear and provide useful information.

The code changes are approved.

---

12-17: LGTM!

The workflow name and schedule trigger are well-defined.

The code changes are approved.

---

18-21: LGTM!

The permissions for issues and pull requests are correctly set to write.

The code changes are approved.

---

22-43: LGTM!

The job to mark stale issues and pull requests is well-defined and includes all necessary configurations.

The code changes are approved.

jest.config.js (6)

1-5: LGTM!

The Jest configuration roots, coverage collection, and setup files are well-defined.

The code changes are approved.

---

6-11: LGTM!

The test match patterns and test environment are well-defined.

The code changes are approved.

---

12-20: LGTM!

The transform configurations for various file types are well-defined.

The code changes are approved.

---

21-31: LGTM!

The module paths and module name mappings are well-defined.

The code changes are approved.

---

32-47: LGTM!

The module file extensions and watch plugins are well-defined.

The code changes are approved.

---

48-67: LGTM!

The configurations for reset mocks, coverage path ignore patterns, coverage threshold, and test path ignore patterns are well-defined.

The code changes are approved.

src/assets/scss/components/_buttons.scss (7)

1-7: LGTM!

The variables are correctly defined, and the comment for $btn-white-space is helpful.

The code changes are approved.

---

9-16: LGTM!

The variables for small and large button styling are correctly defined.

The code changes are approved.

---

17-26: LGTM!

The variables for button border width, font weight, box shadow, focus width, focus box shadow, disabled opacity, and active box shadow are correctly defined.

The code changes are approved.

---

28-35: LGTM!

The variables for button link colors and border radius are correctly defined.

The code changes are approved.

---

37-41: LGTM!

The variable for button transition is correctly defined.

The code changes are approved.

---

43-50: LGTM!

The variables for button hover and active states are correctly defined.

The code changes are approved.

---

52-73: LGTM!

The button styles for primary, secondary, success, warning, and info buttons, as well as outline buttons, are correctly defined.

The code changes are approved.

src/GraphQl/Mutations/PledgeMutation.ts (3)

1-2: LGTM!

The import statement for graphql-tag is correct.

The code changes are approved.

---

3-36: LGTM!

The GraphQL mutation to create a pledge and the detailed documentation are correctly defined.

The code changes are approved.

---

38-84: LGTM!

The GraphQL mutations to update and delete a pledge and the detailed documentation are correctly defined.

The code changes are approved.

src/GraphQl/Mutations/FundMutation.ts (3)

1-2: LGTM!

The import statement for graphql-tag is correct.

The code changes are approved.

---

3-36: LGTM!

The GraphQL mutation to create a new fund and the detailed documentation are correctly defined.

The code changes are approved.

---

38-85: LGTM!

The GraphQL mutations to update and remove a fund and the detailed documentation are correctly defined.

The code changes are approved.

src/GraphQl/Mutations/CampaignMutation.ts (3)

1-37: LGTM!

The CREATE_CAMPAIGN_MUTATION is correctly defined and covers all necessary parameters for creating a fundraising campaign.

The code changes are approved.

---

39-73: LGTM!

The UPDATE_CAMPAIGN_MUTATION is correctly defined and covers all necessary parameters for updating a fundraising campaign.

The code changes are approved.

---

75-87: LGTM!

The DELETE_CAMPAIGN_MUTATION is correctly defined and covers the necessary parameter for deleting a fundraising campaign.

The code changes are approved.

src/GraphQl/Mutations/ActionItemMutations.ts (3)

1-33: LGTM!

The CREATE_ACTION_ITEM_MUTATION is correctly defined and covers all necessary parameters for creating an action item.

The code changes are approved.

---

35-71: LGTM!

The UPDATE_ACTION_ITEM_MUTATION is correctly defined and covers all necessary parameters for updating an action item.

The code changes are approved.

---

73-85: LGTM!

The DELETE_ACTION_ITEM_MUTATION is correctly defined and covers the necessary parameter for deleting an action item.

The code changes are approved.

src/GraphQl/Queries/ActionItemQueries.ts (2)

1-66: LGTM!

The ACTION_ITEM_LIST query is correctly defined and covers all necessary parameters for retrieving action items by organization.

The code changes are approved.

---

68-103: LGTM!

The ACTION_ITEM_LIST_BY_EVENTS query is correctly defined and covers the necessary parameter for retrieving action items by event.

The code changes are approved.

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

10-18: LGTM!

The function is correctly implemented with proper error handling.

The code changes are approved.

---

43-78: LGTM!

The function is correctly implemented with proper error handling.

The code changes are approved.

---

80-96: LGTM!

The logic block is correctly implemented with proper error handling.

The code changes are approved.

.github/workflows/md_mdx_format_adjuster.py (4)

20-44: LGTM!

The function correctly escapes special characters for MDX compatibility.

The code changes are approved.

---

46-65: LGTM!

The function correctly processes a single Markdown file for MDX compatibility.

The code changes are approved.

---

67-95: LGTM!

The function correctly processes all Markdown files in a given directory for MDX compatibility.

The code changes are approved.

---

96-97: LGTM!

The script correctly calls the main function if run as the main module.

The code changes are approved.

ISSUE_GUIDELINES.md (3)

8-19: LGTM!

The table of contents is clear and correctly formatted.

The code changes are approved.

---

48-51: LGTM!

The section is clear and correctly formatted.

The code changes are approved.

---

1-3: Fix punctuation mark.

Remove the loose punctuation mark at the end of the first line.

-# Issue Report Guidelines
-:+1::tada: First off, thanks for taking the time to contribute! :tada::+1:
+# Issue Report Guidelines
+:+1::tada: First off, thanks for taking the time to contribute! :tada::+1:

Apply this diff to fix the punctuation mark.

Likely invalid or redundant comment.

Tools

LanguageTool

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

(UNLIKELY_OPENING_PUNCTUATION)

src/App.test.tsx (4)

2-13: LGTM!

The imports are correctly added and necessary for the tests.

The code changes are approved.

---

17-23: LGTM!

The mock modules are correctly added and necessary for the tests.

The code changes are approved.

---

25-67: LGTM!

The mock data and utility functions are correctly added and necessary for the tests.

The code changes are approved.

---

69-110: LGTM!

The test cases are correctly implemented and necessary for testing the App component.

The code changes are approved.

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

1-14: LGTM!

The file header and metadata are correctly defined.

The code changes are approved.

---

16-73: LGTM!

The job definition and steps are correctly structured and well-defined.

The code changes are approved.

---

21-68: LGTM!

The PR review policy step is correctly implemented and the message is comprehensive.

The code changes are approved.

---

69-73: LGTM!

The greeting message step is correctly implemented and the message is informative.

The code changes are approved.

README.md (3)

3-5: LGTM!

The community invitation link and logo image source are correctly added and updated.

The code changes are approved.

---

24-32: LGTM!

The table of contents is correctly added and improves navigation within the document.

The code changes are approved.

---

45-51: LGTM!

The documentation references are correctly restructured and updated, improving clarity and accessibility.

The code changes are approved.

.github/workflows/eslint_disable_check.py (6)

1-28: LGTM!

The file header and imports are correctly defined.

The code changes are approved.

---

29-42: LGTM!

The has_eslint_disable function is correctly implemented and follows best practices.

The code changes are approved.

---

43-68: LGTM!

The check_eslint function is correctly implemented and follows best practices.

The code changes are approved.

---

70-84: LGTM!

The arg_parser_resolver function is correctly implemented and follows best practices.

The code changes are approved.

---

86-115: LGTM!

The main function is correctly implemented and follows best practices.

The code changes are approved.

---

117-118: LGTM!

The script entry point is correctly implemented.

The code changes are approved.

.eslintrc.json (4)

4-4: LGTM!

Adding the Node.js environment is appropriate for recognizing Node.js global variables and syntax.

The code changes are approved.

---

14-16: LGTM!

Adding "plugin:@typescript-eslint/recommended" and "eslint-config-prettier" enhances TypeScript linting and integrates Prettier with ESLint.

The code changes are approved.

---

32-39: LGTM!

Adding "import", "eslint-plugin-tsdoc", and "prettier" plugins expands linting capabilities for import management, TypeScript documentation, and code formatting.

The code changes are approved.

---

Line range hint 41-140: LGTM!

The new and updated rules enforce stricter coding standards and TypeScript best practices.

The code changes are approved.

package.json (5)

2-5: LGTM!

Updating the project name, version, and adding "type": "module" reflects a significant upgrade and reorganization of the project.

The code changes are approved.

---

8-59: LGTM!

The changes in the dependencies section indicate a shift towards more modern tooling and practices.

The code changes are approved.

---

62-76: LGTM!

The new scripts for serving, building, testing, linting, formatting, and type checking enhance the development workflow.

The code changes are approved.

---

97-133: LGTM!

The changes in the devDependencies section reflect a shift towards more modern tooling and practices.

The code changes are approved.

---

134-142: LGTM!

The new resolutions and engines sections ensure compatibility with specific versions of dependencies and Node.js.

The code changes are approved.

PR_GUIDELINES.md (5)

1-5: Consider stylistic improvements.

The introduction is clear and concise, but consider these stylistic improvements:

• Remove the punctuation mark after "Guidelines" in line 2.
• Replace "In order to" with "To" in line 5.

[style]
Apply this diff to improve the style:

-# Pull Request Guidelines
-:+1::tada: First off, thanks for taking the time to contribute! :tada::+1: In order to give everyone a chance to submit a pull request and contribute to the Talawa project, we have put restrictions in place. This section outlines the guidelines that should be imposed upon pull requests in the Talawa project.
+# Pull Request Guidelines
+:+1::tada: First off, thanks for taking the time to contribute! :tada::+1: To give everyone a chance to submit a pull request and contribute to the Talawa project, we have put restrictions in place. This section outlines the guidelines that should be imposed upon pull requests in the Talawa project.

Tools

LanguageTool

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

---

7-17: LGTM!

The Table of Contents section is clear and concise.

The code changes are approved.

---

19-24: LGTM!

The Pull Requests and Issues section is clear and concise.

The code changes are approved.

---

25-42: Specify a language for fenced code blocks.

The Linting and Formatting section is clear and concise, but specifying a language for fenced code blocks improves readability.
[style]
Apply this diff to specify a language for fenced code blocks:

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

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

Tools

Markdownlint

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)

---

44-69: Consider stylistic improvements.

The Testing and Pull Request Processing sections are clear and concise, but consider these stylistic improvements:

• Avoid split infinitives in line 46.
• Replace "very important" with "crucial" in line 56.
• Add a comma after "Therefore" in line 56.
• Replace "fix" with "resolve" in line 59.
• Replace "sooner or later" with "eventually" in line 64.
• Add a comma before "and" in line 64.
• Shorten "make changes" to "update" in line 65.

[style]
Apply this diff to improve the style:

-1. All pull requests must have test units. If, for some reason, it is not possible to add tests, please let us know and explain why. In that case, you'll need to tell us what steps you followed to manually test your changes.
+1. All pull requests must have test units. If, for some reason, it is not possible to add tests, please let us know and explain why. In that case, you'll need to tell us what steps you followed to test your changes manually.

-1. Removing assigned reviewers from your Pull Request will cause it to be closed. The quality of our code is very important to us. Therefore we make experienced maintainers of our code base review your code.
+1. Removing assigned reviewers from your Pull Request will cause it to be closed. The quality of our code is crucial to us. Therefore, we make experienced maintainers of our code base review your code.

-1. Upon successful push to the fork, check if all tests are passing; if not, fix the issues and then create a pull request.
+1. Upon successful push to the fork, check if all tests are passing; if not, resolve the issues and then create a pull request.

-1. Please do not @mention contributors and mentors. Sometimes it takes time before we can review your pull request or answer your questions, but we'll get to it sooner or later. @mentioning someone just adds to the pile of notifications we get and it won't make us look at your issue faster.
+1. Please do not @mention contributors and mentors. Sometimes it takes time before we can review your pull request or answer your questions, but we'll get to it eventually. @mentioning someone just adds to the pile of notifications we get, and it won't make us look at your issue faster.

-1. Do not force push. If you make changes to your pull request, please simply add a new commit, as that makes it easy for us to review your new changes.
+1. Do not force push. If you update your pull request, please simply add a new commit, as that makes it easy for us to review your new changes.

Tools

LanguageTool

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

CODE_OF_CONDUCT.md (1)

3-19: LGTM!

The Table of Contents (ToC) is well-structured and improves navigation and accessibility.

The code changes are approved.

Tools

LanguageTool

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

(ENGLISH_WORD_REPEAT_RULE)

.github/workflows/compare_translations.py (4)

63-89: LGTM!

The compare_translations function is well-implemented and correctly identifies missing and mismatched keys.

The code changes are approved.

---

92-110: LGTM!

The load_translation function is well-implemented and correctly handles file reading and JSON parsing.

The code changes are approved.

---

112-157: LGTM!

The check_translations function is well-implemented and correctly compares translations across different languages.

The code changes are approved.

---

159-186: LGTM!

The main function is well-implemented and correctly parses command-line arguments and checks translations.

The code changes are approved.

.github/workflows/push.yml (6)

43-47: Ensure cache key uniqueness.

The cache key should be unique enough to avoid cache collisions. Consider including the node-version in the key.

- key: ${{ runner.os }}-code-coverage-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}
+ key: ${{ runner.os }}-code-coverage-${{ env.cache-name }}-${{ matrix.node-version }}-${{ hashFiles('**/package-lock.json') }}

Verify that the cache key is unique enough to avoid collisions.

---

19-21: Verify the usage of CODECOV_UNIQUE_NAME.

Ensure that CODECOV_UNIQUE_NAME is correctly used and provides meaningful information.

Verify that CODECOV_UNIQUE_NAME is correctly used and provides meaningful information.

Also applies to: 53-59

---

87-91: Ensure cache key uniqueness.

The cache key should be unique enough to avoid cache collisions. Consider including the node-version in the key.

- key: ${{ runner.os }}-generate-docs-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}
+ key: ${{ runner.os }}-generate-docs-${{ env.cache-name }}-${{ matrix.node-version }}-${{ hashFiles('**/package-lock.json') }}

Verify that the cache key is unique enough to avoid collisions.

---

105-108: Verify the usage of typedoc and typedoc-plugin-markdown.

Ensure that typedoc and typedoc-plugin-markdown are correctly used and provide meaningful documentation.

Verify that typedoc and typedoc-plugin-markdown are correctly used and provide meaningful documentation.

---

160-160: Verify the usage of TALAWA_DOCS_SYNC.

Ensure that TALAWA_DOCS_SYNC is correctly used and provides meaningful information.

Verify that TALAWA_DOCS_SYNC is correctly used and provides meaningful information.

---

175-175: Verify the usage of dmnemec/[email protected].

Ensure that dmnemec/[email protected] is correctly used and provides meaningful functionality.

Verify that dmnemec/[email protected] is correctly used and provides meaningful functionality.

src/GraphQl/Mutations/OrganizationMutations.ts (10)

12-26: LGTM!

The mutation is correctly defined and follows GraphQL best practices.

The code changes are approved.

---

34-38: LGTM!

The mutation is correctly defined and follows GraphQL best practices.

The code changes are approved.

---

46-50: LGTM!

The mutation is correctly defined and follows GraphQL best practices.

The code changes are approved.

---

60-76: LGTM!

The mutation is correctly defined and follows GraphQL best practices.

The code changes are approved.

---

78-86: LGTM!

The mutation is correctly defined and follows GraphQL best practices.

The code changes are approved.

---

88-106: LGTM!

The mutation is correctly defined and follows GraphQL best practices.

The code changes are approved.

---

109-122: LGTM!

The mutation is correctly defined and follows GraphQL best practices.

The code changes are approved.

---

125-140: LGTM!

The mutation is correctly defined and follows GraphQL best practices.

The code changes are approved.

---

143-165: LGTM!

The subscription is correctly defined and follows GraphQL best practices.

The code changes are approved.

---

167-183: LGTM!

The subscription is correctly defined and follows GraphQL best practices.

The code changes are approved.

src/GraphQl/Queries/OrganizationQueries.ts (8)

15-72: LGTM!

The query is correctly defined and follows GraphQL best practices.

The code changes are approved.

---

74-109: LGTM!

The query is correctly defined and follows GraphQL best practices.

The code changes are approved.

---

122-169: LGTM!

The query is correctly defined and follows GraphQL best practices.

The code changes are approved.

---

178-207: LGTM!

The query is correctly defined and follows GraphQL best practices.

The code changes are approved.

---

216-245: LGTM!

The query is correctly defined and follows GraphQL best practices.

The code changes are approved.

---

254-267: LGTM!

The query is correctly defined and follows GraphQL best practices.

The code changes are approved.

---

275-289: LGTM!

The query is correctly defined and follows GraphQL best practices.

The code changes are approved.

---

297-320: LGTM!

The query is correctly defined and follows GraphQL best practices.

The code changes are approved.

src/GraphQl/Queries/PlugInQueries.ts (10)

9-19: LGTM!

The PLUGIN_GET query is correctly structured and follows GraphQL syntax.

The code changes are approved.

---

27-45: LGTM!

The ADVERTISEMENTS_GET query is correctly structured and follows GraphQL syntax.

The code changes are approved.

---

59-100: LGTM!

The ORGANIZATION_EVENTS_CONNECTION query is correctly structured and follows GraphQL syntax.

The code changes are approved.

---

111-133: LGTM!

The DIRECT_CHAT_MESSAGES_BY_CHAT_ID query is correctly structured and follows GraphQL syntax.

The code changes are approved.

---

135-167: LGTM!

The DIRECT_CHAT_BY_ID query is correctly structured and follows GraphQL syntax.

The code changes are approved.

---

169-196: LGTM!

The GROUP_CHAT_BY_ID query is correctly structured and follows GraphQL syntax.

The code changes are approved.

---

222-262: LGTM!

The DIRECT_CHATS_LIST query is correctly structured and follows GraphQL syntax.

The code changes are approved.

---

264-299: LGTM!

The GROUP_CHAT_LIST query is correctly structured and follows GraphQL syntax.

The code changes are approved.

---

307-311: LGTM!

The IS_SAMPLE_ORGANIZATION_QUERY query is correctly structured and follows GraphQL syntax.

The code changes are approved.

---

320-328: LGTM!

The ORGANIZATION_CUSTOM_FIELDS query is correctly structured and follows GraphQL syntax.

The code changes are approved.

.github/workflows/countline.py (7)

1-32: LGTM!

The script header and imports are correctly structured and follow Python standards.

The code changes are approved.

---

35-55: LGTM!

The _valid_filename function is correctly implemented and follows Python standards.

The code changes are approved.

---

58-78: LGTM!

The _valid_extension function is correctly implemented and follows Python standards.

The code changes are approved.

---

81-119: LGTM!

The _valid_exclusions function is correctly implemented and follows Python standards.

The code changes are approved.

---

122-142: LGTM!

The _filepaths_in_directories function is correctly implemented and follows Python standards.

The code changes are approved.

---

145-195: LGTM!

The _arg_parser_resolver function is correctly implemented and follows Python standards.

The code changes are approved.

---

197-294: LGTM!

The main function is correctly implemented and follows Python standards.

The code changes are approved.

src/App.tsx (1)

1-45: LGTM!

The import statements are correctly structured and follow JavaScript/React standards.

The code changes are approved.

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

19-21: Security: Avoid using untrusted data directly in environment variables.

The CODECOV_UNIQUE_NAME environment variable uses ${{ github.run_id }} and ${{ github.run_number }} directly. Ensure these values are sanitized or validated.

Ensure that these values are safe to use directly in environment variables.

---

38-41: Security: Ensure the script is safe to execute.

The script countline.py is being executed with chmod +x and then run. Ensure the script is safe and does not contain any malicious code.

Review the countline.py script to ensure it is safe to execute.

---

61-64: Security: Ensure the script is safe to execute.

The script check-localstorage-usage.js is being executed with chmod +x and then run. Ensure the script is safe and does not contain any malicious code.

Review the check-localstorage-usage.js script to ensure it is safe to execute.

---

66-69: Security: Ensure the script is safe to execute.

The script compare_translations.py is being executed with chmod +x and then run. Ensure the script is safe and does not contain any malicious code.

Review the compare_translations.py script to ensure it is safe to execute.

---

79-120: LGTM!

The job is correctly implemented to check for unauthorized file changes.

The code changes are approved.

---

121-148: LGTM!

The job is correctly implemented to check if the number of changed files is acceptable.

The code changes are approved.

---

149-164: LGTM!

The job is correctly implemented to check for eslint-disable comments.

The code changes are approved.

CODE_STYLE.md (5)

24-38: LGTM!

The section is correctly implemented.

The code changes are approved.

---

40-45: LGTM!

The section is correctly implemented.

The code changes are approved.

---

47-77: LGTM!

The section is correctly implemented.

The code changes are approved.

Tools

Markdownlint

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)

---

118-121: LGTM!

The section is correctly implemented.

The code changes are approved.

---

152-183: LGTM!

The section is correctly implemented.

The code changes are approved.

Tools

LanguageTool

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

Markdownlint

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)

---

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)

CONTRIBUTING.md (1)

7-23: LGTM!

The section is correctly implemented.

The code changes are approved.

INSTALLATION.md (2)

1-3: LGTM!

The introduction is clear and concise.

The section is approved.

---

37-50: LGTM!

The installation steps summary is clear and concise.

The section is approved.

src/GraphQl/Queries/Queries.ts (8)

5-29: LGTM!

The CHECK_AUTH query is well-structured and correctly implemented.

The query is approved.

---

32-61: LGTM!

The ORGANIZATION_LIST query is well-structured and correctly implemented.

The query is approved.

---

64-103: LGTM!

The ORGANIZATION_CONNECTION_LIST query is well-structured and correctly implemented.

The query is approved.

---

106-201: LGTM!

The USER_LIST query is well-structured and correctly implemented.

The query is approved.

---

202-220: LGTM!

The USER_LIST_FOR_TABLE query is well-structured and correctly implemented.

The query is approved.

---

222-263: LGTM!

The USER_LIST_REQUEST query is well-structured and correctly implemented.

The query is approved.

---

265-290: LGTM!

The EVENT_DETAILS query is well-structured and correctly implemented.

The query is approved.

---

292-302: LGTM!

The EVENT_ATTENDEES query is well-structured and correctly implemented.

The query is approved.

src/GraphQl/Mutations/mutations.ts (6)

3-9: LGTM!

The UNBLOCK_USER_MUTATION is well-structured and correctly implemented.

The mutation is approved.

---

13-19: LGTM!

The BLOCK_USER_MUTATION is well-structured and correctly implemented.

The mutation is approved.

---

23-29: LGTM!

The REJECT_ORGANIZATION_REQUEST_MUTATION is well-structured and correctly implemented.

The mutation is approved.

---

33-39: LGTM!

The ACCEPT_ORGANIZATION_REQUEST_MUTATION is well-structured and correctly implemented.

The mutation is approved.

---

43-67: LGTM!

The UPDATE_ORGANIZATION_MUTATION is well-structured and correctly implemented.

The mutation is approved.

---

85-121: LGTM!

The UPDATE_USER_MUTATION is well-structured and correctly implemented.

The mutation is approved.

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

2-25: LGTM!

The translations for the login page are correctly implemented.

The code changes are approved.

---

27-41: LGTM!

The translations for the user login page are correctly implemented.

The code changes are approved.

---

43-47: LGTM!

The translations for the latest events are correctly implemented.

The code changes are approved.

---

48-52: LGTM!

The translations for the latest posts are correctly implemented.

The code changes are approved.

---

53-55: LGTM!

The translations for the list navbar are correctly implemented.

The code changes are approved.

---

56-59: LGTM!

The translations for the left drawer are correctly implemented.

The code changes are approved.

---

61-79: LGTM!

The translations for the left drawer organization are correctly implemented.

The code changes are approved.

---

80-108: LGTM!

The translations for the organization list are correctly implemented.

The code changes are approved.

---

110-112: LGTM!

The translations for the organization list card are correctly implemented.

The code changes are approved.

---

114-116: LGTM!

The translations for the pagination list are correctly implemented.

The code changes are approved.

schema.graphql (2)

1-3: LGTM!

The directives @auth and @role are correctly defined.

The code changes are approved.

---

67-71: LGTM!

The enum AdvertisementType is correctly defined.

The code changes are approved.

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

43-46: LGTM!

The keys and values are correctly defined.

The code changes are approved.

---

48-51: LGTM!

The keys and values are correctly defined.

The code changes are approved.

---

53-54: LGTM!

The key and value are correctly defined.

The code changes are approved.

---

56-59: LGTM!

The keys and values are correctly defined.

The code changes are approved.

---

61-78: LGTM!

The keys and values are correctly defined.

The code changes are approved.

---

110-112: LGTM!

The keys and values are correctly defined.

The code changes are approved.

---

114-116: LGTM!

The keys and values are correctly defined.

The code changes are approved.

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

2-25: LGTM!

The translations for the loginPage segment are accurate and contextually appropriate.

The translations are approved.

---

27-41: LGTM!

The translations for the userLoginPage segment are accurate and contextually appropriate.

The translations are approved.

---

43-46: LGTM!

The translations for the latestEvents segment are accurate and contextually appropriate.

The translations are approved.

---

48-51: LGTM!

The translations for the latestPosts segment are accurate and contextually appropriate.

The translations are approved.

---

53-54: LGTM!

The translations for the listNavbar segment are accurate and contextually appropriate.

The translations are approved.

---

56-59: LGTM!

The translations for the leftDrawer segment are accurate and contextually appropriate.

The translations are approved.

---

61-78: LGTM!

The translations for the leftDrawerOrg segment are accurate and contextually appropriate.

The translations are approved.

---

80-108: LGTM!

The translations for the orgList segment are accurate and contextually appropriate.

The translations are approved.

---

110-112: LGTM!

The translations for the orgListCard segment are accurate and contextually appropriate.

The translations are approved.

---

114-116: LGTM!

The translations for the paginationList segment are accurate and contextually appropriate.

The translations are approved.

---

118-129: LGTM!

The translations for the requests segment are accurate and contextually appropriate.

The translations are approved.

---

131-153: LGTM!

The translations for the users segment are accurate and contextually appropriate.

The translations are approved.

---

155-165: LGTM!

The translations for the communityProfile segment are accurate and contextually appropriate.

The translations are approved.

---

167-181: LGTM!

The translations for the dashboard segment are accurate and contextually appropriate.

The translations are approved.

---

183-201: LGTM!

The translations for the organizationPeople segment are accurate and contextually appropriate.

The translations are approved.

---

203-205: LGTM!

The translations for the userListCard segment are accurate and contextually appropriate.

The translations are approved.

---

207-211: LGTM!

The translations for the orgAdminListCard segment are accurate and contextually appropriate.

The translations are approved.

---

213-217: LGTM!

The translations for the orgPeopleListCard segment are accurate and contextually appropriate.

The translations are approved.

---

219-248: LGTM!

The translations for the organizationEvents segment are accurate and contextually appropriate.

The translations are approved.

---

250-284: LGTM!

The translations for the organizationActionItems segment are accurate and contextually appropriate.

The translations are approved.

---

286-301: LGTM!

The translations for the organizationAgendaCategory segment are accurate and contextually appropriate.

The translations are approved.

---

303-335: LGTM!

The translations for the agendaItems segment are accurate and contextually appropriate.

The translations are approved.

---

337-363: LGTM!

The translations for the eventListCard segment are accurate and contextually appropriate.

The translations are approved.

---

365-387: LGTM!

The translations for the funds segment are accurate and contextually appropriate.

The translations are approved.

---

389-411: LGTM!

The translations for the fundCampaign segment are accurate and contextually appropriate.

The translations are approved.

---

413-439: LGTM!

The translations for the pledges segment are accurate and contextually appropriate.

The translations are approved.

---

441-467: LGTM!

The translations for the orgPost segment are accurate and contextually appropriate.

The translations are approved.

---

469-474: LGTM!

The translations for the postNotFound segment are accurate and contextually appropriate.

The translations are approved.

---

476-482: LGTM!

The translations for the userNotFound segment are accurate and contextually appropriate.

The translations are approved.

---

484-501: LGTM!

The translations for the orgPostCard segment are accurate and contextually appropriate.

The translations are approved.

---

503-517: LGTM!

The translations for the blockUnblockUser segment are accurate and contextually appropriate.

The translations are approved.

---

519-526: LGTM!

The translations for the eventManagement segment are accurate and contextually appropriate.

The translations are approved.

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

2-25: LGTM!

The translations for the login page appear to be accurate and contextually correct.

The code changes are approved.

---

27-41: LGTM!

The translations for the user login page appear to be accurate and contextually correct.

The code changes are approved.

---

43-47: LGTM!

The translations for the latest events appear to be accurate and contextually correct.

The code changes are approved.

---

48-52: LGTM!

The translations for the latest posts appear to be accurate and contextually correct.

The code changes are approved.

---

53-55: LGTM!

The translations for the list navbar appear to be accurate and contextually correct.

The code changes are approved.

---

56-60: LGTM!

The translations for the left drawer appear to be accurate and contextually correct.

The code changes are approved.

---

61-79: LGTM!

The translations for the left drawer organization appear to be accurate and contextually correct.

The code changes are approved.

---

80-109: LGTM!

The translations for the organization list appear to be accurate and contextually correct.

The code changes are approved.

---

110-113: LGTM!

The translations for the organization list card appear to be accurate and contextually correct.

The code changes are approved.

---

114-117: LGTM!

The translations for the pagination list appear to be accurate and contextually correct.

The code changes are approved.

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

2-43: LGTM!

The translations for the login page are accurate and contextually correct.

The code changes are approved.

---

45-75: LGTM!

The translations for the user login page are accurate and contextually correct.

The code changes are approved.

---

77-81: LGTM!

The translations for the latest events section are accurate and contextually correct.

The code changes are approved.

---

82-86: LGTM!

The translations for the latest posts section are accurate and contextually correct.

The code changes are approved.

---

87-91: LGTM!

The translations for the list navbar are accurate and contextually correct.

The code changes are approved.

---

93-100: LGTM!

The translations for the left drawer menu are accurate and contextually correct.

The code changes are approved.

---

102-124: LGTM!

The translations for the left drawer menu specific to organizations are accurate and contextually correct.

The code changes are approved.

---

126-162: LGTM!

The translations for the organization list are accurate and contextually correct.

The code changes are approved.

---

164-168: LGTM!

The translations for the organization list card are accurate and contextually correct.

The code changes are approved.

---

170-172: LGTM!

The translations for the pagination list are accurate and contextually correct.

The code changes are approved.

---

174-189: LGTM!

The translations for the requests section are accurate and contextually correct.

The code changes are approved.

---

191-230: LGTM!

The translations for the users section are accurate and contextually correct.

The code changes are approved.

---

232-242: LGTM!

The translations for the community profile section are accurate and contextually correct.

The code changes are approved.

---

244-263: LGTM!

The translations for the dashboard section are accurate and contextually correct.

The code changes are approved.

---

265-295: LGTM!

The translations for the organization people section are accurate and contextually correct.

The code changes are approved.

---

297-301: LGTM!

The translations for the user list card are accurate and contextually correct.

The code changes are approved.

---

303-311: LGTM!

The translations for the organization admin list card are accurate and contextually correct.

The code changes are approved.

---

313-321: LGTM!

The translations for the organization people list card are accurate and contextually correct.

The code changes are approved.

---

323-359: LGTM!

The translations for the organization events section are accurate and contextually correct.

The code changes are approved.

---

361-399: LGTM!

The translations for the organization action items section are accurate and contextually correct.

The code changes are approved.

---

401-416: LGTM!

The translations for the organization agenda category section are accurate and contextually correct.

The code changes are approved.

---

418-450: LGTM!

The translations for the agenda items section are accurate and contextually correct.

The code changes are approved.

---

452-488: LGTM!

The translations for the event list card are accurate and contextually correct.

The code changes are approved.

---

490-512: LGTM!

The translations for the funds section are accurate and contextually correct.

The code changes are approved.

---

514-536: LGTM!

The translations for the fund campaign section are accurate and contextually correct.

The code changes are approved.

---

538-566: LGTM!

The translations for the pledges section are accurate and contextually correct.

The code changes are approved.

---

569-596: LGTM!

The translations for the organization post section are accurate and contextually correct.

The code changes are approved.

---

598-603: LGTM!

The translations for the post not found section are accurate and contextually correct.

The code changes are approved.

---

605-612: LGTM!

The translations for the user not found section are accurate and contextually correct.

The code changes are approved.

---

614-635: LGTM!

The translations for the organization post card are accurate and contextually correct.

The code changes are approved.

---

637-656: LGTM!

The translations for the block/unblock user section are accurate and contextually correct.

The code changes are approved.

---

658-665: LGTM!

The translations for the event management section are accurate and contextually correct.

The code changes are approved.

[coderabbitai]

Add error handling for the spawn function.

The conditional build process is correctly implemented, but it could be improved by handling potential errors from the spawn function.

Apply this diff to add error handling:

 if (process.env.ALLOW_LOGS === "YES") {
-  spawn(react_app_rewired_build, { stdio: 'inherit', shell: true });
+  const buildProcess = spawn(react_app_rewired_build, { stdio: 'inherit', shell: true });
+  buildProcess.on('error', (err) => {
+    console.error('Failed to start subprocess:', err);
+  });
 }
 else {
-  spawn(react_script_build, { stdio: 'inherit', shell: true });
+  const buildProcess = spawn(react_script_build, { stdio: 'inherit', shell: true });
+  buildProcess.on('error', (err) => {
+    console.error('Failed to start subprocess:', err);
+  });
 }

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

	if (process.env.ALLOW_LOGS === "YES") {
	spawn(react_app_rewired_build, { stdio: 'inherit', shell: true });
	}
	else {
	spawn(react_script_build, { stdio: 'inherit', shell: true });
	}
	if (process.env.ALLOW_LOGS === "YES") {
	const buildProcess = spawn(react_app_rewired_build, { stdio: 'inherit', shell: true });
	buildProcess.on('error', (err) => {
	console.error('Failed to start subprocess:', err);
	});
	}
	else {
	const buildProcess = spawn(react_script_build, { stdio: 'inherit', shell: true });
	buildProcess.on('error', (err) => {
	console.error('Failed to start subprocess:', err);
	});
	}

[coderabbitai]

Remove redundant use strict directive.

The use strict directive is redundant in JavaScript modules.

Apply this diff to remove the redundant use strict directive:

-'use strict';

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

'use strict';

Tools

Biome

[error] 1-1: Redundant use strict directive.

The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.

(lint/suspicious/noRedundantUseStrict)

[coderabbitai]

Fix grammatical issues and bare URL.

The section is well-structured but needs some grammatical corrections and the bare URL should be fixed.

Apply this diff to fix the issues:

-The process in easy:
+The process is easy:
1. Install `talawa-docs` on your system
1. Launch Docusaurus on your system according to the `talawa-docs` documentation.
-    - A local version of `docs.talawa.io` should automatically launched in your browser at http://localhost:3000/
+    - 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. If adding a file, then you will also need to edit the `sidebars.js` which is used to generate the [docs.talawa.io](https://docs.talawa.io/) menus.
-1. Always monitor the local website in your brower to make sure the changes are acceptable.
+1. Always monitor the local website in your browser to make sure the changes are acceptable.
    - You'll be able to see errors that you can use for troubleshooting in the CLI window you used to launch the local website.

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

	## How to use Docusaurus
	The process in easy:
	1. Install `talawa-docs` on your system
	1. Launch docusaurus on your system according to the `talawa-docs`documentation.
	- A local version of `docs.talawa.io` should automatically launched in your browser at http://localhost:3000/
	1. Add/modify the markdown documents to the `docs/` directory of the `talawa-docs` repository
	1. If adding a file, then you will also need to edit the `sidebars.js` which is used to generate the [docs.talawa.io](https://docs.talawa.io/) menus.
	1. Always monitor the local website in your brower to make sure the changes are acceptable.
	- You'll be able to see errors that you can use for troubleshooting in the CLI window you used to launch the local website.
	## How to use Docusaurus
	The process is easy:
	1. Install `talawa-docs` on your system
	1. Launch Docusaurus on your system according to the `talawa-docs` documentation.
	- A local version of `docs.talawa.io` should automatically launch in your browser at [http://localhost:3000](http://localhost:3000/)
	1. Add/modify the Markdown documents to the `docs/` directory of the `talawa-docs` repository
	1. If adding a file, then you will also need to edit the `sidebars.js` which is used to generate the [docs.talawa.io](https://docs.talawa.io/) menus.
	1. Always monitor the local website in your browser to make sure the changes are acceptable.
	- You'll be able to see errors that you can use for troubleshooting in the CLI window you used to launch the local website.

Tools

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)

Markdownlint

25-25: null
Bare URL used

(MD034, no-bare-urls)

[coderabbitai]

Avoid duplicate keys.

The key settings is duplicated, which might cause issues during translation.

Consider removing or renaming one of the duplicate keys.

Also applies to: 66-66

[coderabbitai]

Avoid duplicate keys.

The key settings is duplicated, which might cause issues during translation.

Consider removing or renaming one of the duplicate keys.

Also applies to: 66-66

[coderabbitai]

Fix typographical and grammatical issues.

There are several typographical and grammatical issues in the prerequisites section.

Apply this diff to fix the issues:

- In this section we'll explain how to set up all the prerequisite software packages to get you up and running.
+ In this section, we'll explain how to set up all the prerequisite software packages to get you up and running.

- Basic `git` knowledge is required for open source contribution so make sure you're comfortable with it.
+ Basic `git` knowledge is required for open-source contribution, so make sure you're comfortable with it.

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

	# Prerequisites
	In this section we'll explain how to set up all the prerequisite software packages to get you up and running.
	## Install git
	The easiest way to get the latest copies of our code is to install the `git` package on your computer.
	Follow the setup guide for `git` on official [git docs](https://git-scm.com/downloads). Basic `git` knowledge is required for open source contribution so make sure you're comfortable with it. [Here's](https://youtu.be/apGV9Kg7ics) a good tutorial to get started with `git` and `github`.
	# Prerequisites
	In this section, we'll explain how to set up all the prerequisite software packages to get you up and running.
	## Install git
	The easiest way to get the latest copies of our code is to install the `git` package on your computer.
	Follow the setup guide for `git` on official [git docs](https://git-scm.com/downloads). Basic `git` knowledge is required for open-source contribution, so make sure you're comfortable with it. [Here's](https://youtu.be/apGV9Kg7ics) a good tutorial to get started with `git` and `github`.

Tools

LanguageTool

[typographical] ~54-~54: 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] ~60-~60: 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)

[coderabbitai]

Fix typographical and grammatical issues.

There are several typographical and grammatical issues in the post-configuration steps section.

Apply this diff to fix the issues:

- By default `talawa-admin` runs on port `4321` on your system's localhost.
+ By default, `talawa-admin` runs on port `4321` on your system's localhost.

- The first time you navigate to the running talawa-admin's website you'll land at talawa-admin registration page.
+ The first time you navigate to the running talawa-admin's website, you'll land at the talawa-admin registration page.

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

	# Post Configuration Steps
	It's now time to start Talawa-Admin and get it running
	## Running Talawa-Admin
	Run the following command to start `talawa-admin` development server:
	```
	npm run serve
	```
	## Accessing Talawa-Admin
	By default `talawa-admin` runs on port `4321` on your system's localhost. It is available on the following endpoint:
	```
	http://localhost:4321/
	```
	If you have specified a custom port number in your `.env` file, Talawa-Admin will run on the following endpoint:
	```
	http://localhost:${{customPort}}/
	```
	Replace `${{customPort}}` with the actual custom port number you have configured in your `.env` file.
	## Talawa-Admin Registration
	The first time you navigate to the running talawa-admin's website you'll land at talawa-admin registration page. Sign up using whatever credentials you want and create the account. Make sure to remember the email and password you entered because they'll be used to sign you in later on.
	## Talawa-Admin Login
	Now sign in to talawa-admin using the `email` and `password` you used to sign up.
	# Post Configuration Steps
	It's now time to start Talawa-Admin and get it running
	## Running Talawa-Admin
	Run the following command to start `talawa-admin` development server:
	```
	npm run serve
	```
	## Accessing Talawa-Admin
	By default, `talawa-admin` runs on port `4321` on your system's localhost. It is available on the following endpoint:
	```
	http://localhost:4321/
	```
	If you have specified a custom port number in your `.env` file, Talawa-Admin will run on the following endpoint:
	```
	http://localhost:${{customPort}}/
	```
	Replace `${{customPort}}` with the actual custom port number you have configured in your `.env` file.
	## Talawa-Admin Registration
	The first time you navigate to the running talawa-admin's website, you'll land at the talawa-admin registration page. Sign up using whatever credentials you want and create the account. Make sure to remember the email and password you entered because they'll be used to sign you in later on.
	## Talawa-Admin Login
	Now sign in to talawa-admin using the `email` and `password` you used to sign up.

Tools

LanguageTool

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

(BY_DEFAULT_COMMA)

Markdownlint

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

[coderabbitai]

Fix typographical and grammatical issues.

There are several typographical and grammatical issues in the node.js installation section.

Apply this diff to fix the issues:

- Best way to install and manage `node.js` is making use of node version managers.
+ The best way to install and manage `node.js` is by using node version managers.

- For Linux and MacOS, use the terminal window.
+ For Linux and macOS, use the terminal window.

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

	## Install node.js
	Best way to install and manage `node.js` is making use of node version managers. We recommend using `fnm`, which will be described in more detail later.
	Follow these steps to install the `node.js` packages in Windows, Linux and MacOS.
	1. For Windows:
	1. first install `node.js` from their website at https://nodejs.org
	1. When installing, don't click the option to install the `necessary tools`. These are not needed in our case.
	2. then install [fnm](https://github.com/Schniz/fnm). Please read all the steps in this section first.
	1. All the commands listed on this page will need to be run in a Windows terminal session in the `talawa-admin` directory.
	2. Install `fnm` using the `winget` option listed on the page.
	3. Setup `fnm` to automatically set the version of `node.js` to the version required for the repository using these steps:
	1. First, refer to the `fnm` web page's section on `Shell Setup` recommendations.
	2. Open a `Windows PowerShell` terminal window
	3. Run the recommended `Windows PowerShell` command to open `notepad`.
	4. Paste the recommended string into `notepad`
	5. Save the document.
	6. Exit `notepad`
	7. Exit PowerShell
	8. This will ensure that you are always using the correct version of `node.js`
	2. For Linux and MacOS, use the terminal window.
	## Install node.js
	The best way to install and manage `node.js` is by using node version managers. We recommend using `fnm`, which will be described in more detail later.
	Follow these steps to install the `node.js` packages in Windows, Linux and macOS.
	1. For Windows:
	1. first install `node.js` from their website at https://nodejs.org
	1. When installing, don't click the option to install the `necessary tools`. These are not needed in our case.
	2. then install [fnm](https://github.com/Schniz/fnm). Please read all the steps in this section first.
	1. All the commands listed on this page will need to be run in a Windows terminal session in the `talawa-admin` directory.
	2. Install `fnm` using the `winget` option listed on the page.
	3. Setup `fnm` to automatically set the version of `node.js` to the version required for the repository using these steps:
	1. First, refer to the `fnm` web page's section on `Shell Setup` recommendations.
	2. Open a `Windows PowerShell` terminal window
	3. Run the recommended `Windows PowerShell` command to open `notepad`.
	4. Paste the recommended string into `notepad`
	5. Save the document.
	6. Exit `notepad`
	7. Exit PowerShell
	8. This will ensure that you are always using the correct version of `node.js`
	2. For Linux and macOS, use the terminal window.

Tools

LanguageTool

[grammar] ~98-~98: 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] ~112-~112: Possible typo: you repeated a word
Context: ... 5. Save the document. 6. Exit notepad 7. Exit PowerShell 8. This will ens...

(ENGLISH_WORD_REPEAT_RULE)

---

[grammar] ~115-~115: 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)

Markdownlint

101-101: null
Bare URL used

(MD034, no-bare-urls)

[coderabbitai]

Fix typographical and grammatical issues.

There are several typographical and grammatical issues in the testing section.

Apply this diff to fix the issues:

- You can lint your code files using this command:
+ You can lint your code files using the following command:

- We run a pre-commit hook which automatically runs code quality checks each time you make a commit and also fixes some of the issues.
+ We run a pre-commit hook that automatically runs code quality checks each time you make a commit and also fixes some of the issues.

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

	# Testing
	It is important to test our code. If you are a contributor, please follow these steps.
	## Running tests
	You can run the tests for `talawa-admin` using this command:
	```
	npm run test
	```
	## Debugging tests
	You can see the output of failing tests in broswer by running `jest-preview` package before running your tests
	```
	npm run jest-preview
	npm run test
	```
	You don't need to re-run the `npm run jest-preview` command each time, simply run the `npm run test` command if the Jest Preview server is already running in the background, it'll automatically detect any failing tests and show the preview at `http://localhost:3336` as shown in this screenshot -
	
	## Linting code files
	You can lint your code files using this command:
	```
	npm run lint:fix
	```
	## Husky for Git Hooks
	We are using the package `Husky` to run git hooks that run according to different git workflows.
	#### pre-commit hook
	We run a pre-commit hook which automatically runs code quality checks each time you make a commit and also fixes some of the issues. This way you don't have to run them manually each time.
	If you don't want these pre-commit checks running on each commit, you can manually opt out of it using the `--no-verify` flag with your commit message as shown:-
	git commit -m "commit message" --no-verify
	#### post-merge hook
	We are also running a post-merge(post-pull) hook which will automatically run "npm install" only if there is any change made to pakage.json file so that the developer has all the required dependencies when pulling files from remote.
	If you don't want this hook to run, you can manually opt out of this using the `no verify` flag while using the merge command(git pull):
	git pull --no-verify
	# Testing
	It is important to test our code. If you are a contributor, please follow these steps.
	## Running tests
	You can run the tests for `talawa-admin` using this command:
	```
	npm run test
	```
	## Debugging tests
	You can see the output of failing tests in broswer by running `jest-preview` package before running your tests
	```
	npm run jest-preview
	npm run test
	```
	You don't need to re-run the `npm run jest-preview` command each time, simply run the `npm run test` command if the Jest Preview server is already running in the background, it'll automatically detect any failing tests and show the preview at `http://localhost:3336` as shown in this screenshot -
	
	## Linting code files
	You can lint your code files using the following command:
	```
	npm run lint:fix
	```
	## Husky for Git Hooks
	We are using the package `Husky` to run git hooks that run according to different git workflows.
	#### pre-commit hook
	We run a pre-commit hook that automatically runs code quality checks each time you make a commit and also fixes some of the issues. This way you don't have to run them manually each time.
	If you don't want these pre-commit checks running on each commit, you can manually opt out of it using the `--no-verify` flag with your commit message as shown:-
	git commit -m "commit message" --no-verify
	#### post-merge hook
	We are also running a post-merge(post-pull) hook which will automatically run "npm install" only if there is any change made to pakage.json file so that the developer has all the required dependencies when pulling files from remote.
	If you don't want this hook to run, you can manually opt out of this using the `no verify` flag while using the merge command(git pull):
	git pull --no-verify

Tools

LanguageTool

[grammar] ~286-~286: 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)

Markdownlint

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

(MD001, heading-increment)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD046, code-block-style)

---

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

(MD046, code-block-style)

[coderabbitai]

Fix typographical and grammatical issues.

There are several typographical and grammatical issues in the configuration section.

Apply this diff to fix the issues:

- All the options in "setup" can be done manually as well and here's how to do it.
+ All the options in "setup" can be done manually as well, and here's how to do it.

- It is not a part of the repo and you will have to create it.
+ It is not a part of the repo, and you will have to create it.

- Set the `ALLOW_LOGS` to "YES" if you want warnings , info and error messages in your console or leave it blank if you dont need them or want to keep the console clean
+ Set the `ALLOW_LOGS` to "YES" if you want warnings, info, and error messages in your console, or leave it blank if you don't need them or want to keep the console clean.

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

	# Configuration
	It's important to configure Talawa-Admin. Here's how to do it.
	You can use our interactive setup script for the configuration. Use the following command for the same.
	```
	npm run setup
	```
	All the options in "setup" can be done manually as well and here's how to do it. - [Creating .env file](#creating-env-file)
	## Creating .env file
	A file named .env is required in the root directory of talawa-admin for storing environment variables used at runtime. It is not a part of the repo and you will have to create it. For a sample of `.env` file there is a file named `.env.example` in the root directory. Create a new `.env` file by copying the contents of the `.env.example` into `.env` file. Use this command:
	```
	cp .env.example .env
	```
	This `.env` file must be populated with the following environment variables for `talawa-admin` to work:
	| Variable | Description |
	| ---------------------------- | ------------------------------------------------- |
	| PORT | Custom port for Talawa-Admin development purposes |
	| REACT_APP_TALAWA_URL | URL endpoint for talawa-api graphql service |
	| REACT_APP_USE_RECAPTCHA | Whether you want to use reCAPTCHA or not |
	| REACT_APP_RECAPTCHA_SITE_KEY | Site key for authentication using reCAPTCHA |
	Follow the instructions from the sections [Setting up PORT in .env file](#setting-up-port-in-env-file), [Setting up REACT_APP_TALAWA_URL in .env file](#setting-up-REACT_APP_TALAWA_URL-in-env-file), [Setting up REACT_APP_RECAPTCHA_SITE_KEY in .env file](#setting-up-REACT_APP_RECAPTCHA_SITE_KEY-in-env-file) and [Setting up Compiletime and Runtime logs](#setting-up-compiletime-and-runtime-logs) to set up these environment variables.
	## Setting up PORT in .env file
	Add a custom port number for Talawa-Admin development purposes to the variable named `PORT` in the `.env` file.
	## Setting up REACT_APP_TALAWA_URL in .env file
	Add the endpoint for accessing talawa-api graphql service to the variable named `REACT_APP_TALAWA_URL` in the `.env` file.
	```
	REACT_APP_TALAWA_URL="http://API-IP-ADRESS:4000/graphql/"
	```
	If you are a software developer working on your local system, then the URL would be:
	```
	REACT_APP_TALAWA_URL="http://localhost:4000/graphql/"
	```
	If you are trying to access Talawa Admin from a remote host with the API URL containing "localhost", You will have to change the API URL to
	```
	REACT_APP_TALAWA_URL="http://YOUR-REMOTE-ADDRESS:4000/graphql/"
	```
	For additional details, please refer the `How to Access the Talawa-API URL` section in the INSTALLATION.md file found in the [Talawa-API repo](https://github.com/PalisadoesFoundation/talawa-api).
	## Setting up REACT_APP_RECAPTCHA_SITE_KEY in .env file
	You may not want to setup reCAPTCHA since the project will still work. Moreover, it is recommended to not set it up in development environment.
	Just skip to the [Post Configuration Steps](#post-configuration-steps) if you don't want to set it up. Else, read the following steps.
	If you want to setup Google reCAPTCHA now, you may refer to the `RECAPTCHA` section in the INSTALLATION.md file found in [Talawa-API repo](https://github.com/PalisadoesFoundation/talawa-api).
	`Talawa-admin` needs the `reCAPTCHA site key` for the `reCAPTCHA` service you set up during `talawa-api` installation as shown in this screenshot:
	
	Copy/paste this `reCAPTCHA site key` to the variable named `REACT_APP_RECAPTCHA_SITE_KEY` in `.env` file.
	```
	REACT_APP_RECAPTCHA_SITE_KEY="this_is_the_recaptcha_key"
	```
	## Setting up Compiletime and Runtime logs
	Set the `ALLOW_LOGS` to "YES" if you want warnings , info and error messages in your console or leave it blank if you dont need them or want to keep the console clean
	# Configuration
	It's important to configure Talawa-Admin. Here's how to do it.
	You can use our interactive setup script for the configuration. Use the following command for the same.
	```
	npm run setup
	```
	All the options in "setup" can be done manually as well, and here's how to do it. - [Creating .env file](#creating-env-file)
	## Creating .env file
	A file named .env is required in the root directory of talawa-admin for storing environment variables used at runtime. It is not a part of the repo, and you will have to create it. For a sample of `.env` file there is a file named `.env.example` in the root directory. Create a new `.env` file by copying the contents of the `.env.example` into `.env` file. Use this command:
	```
	cp .env.example .env
	```
	This `.env` file must be populated with the following environment variables for `talawa-admin` to work:
	| Variable | Description |
	| ---------------------------- | ------------------------------------------------- |
	| PORT | Custom port for Talawa-Admin development purposes |
	| REACT_APP_TALAWA_URL | URL endpoint for talawa-api graphql service |
	| REACT_APP_USE_RECAPTCHA | Whether you want to use reCAPTCHA or not |
	| REACT_APP_RECAPTCHA_SITE_KEY | Site key for authentication using reCAPTCHA |
	Follow the instructions from the sections [Setting up PORT in .env file](#setting-up-port-in-env-file), [Setting up REACT_APP_TALAWA_URL in .env file](#setting-up-REACT_APP_TALAWA_URL-in-env-file), [Setting up REACT_APP_RECAPTCHA_SITE_KEY in .env file](#setting-up-REACT_APP_RECAPTCHA_SITE_KEY-in-env-file) and [Setting up Compiletime and Runtime logs](#setting-up-compiletime-and-runtime-logs) to set up these environment variables.
	## Setting up PORT in .env file
	Add a custom port number for Talawa-Admin development purposes to the variable named `PORT` in the `.env` file.
	## Setting up REACT_APP_TALAWA_URL in .env file
	Add the endpoint for accessing talawa-api graphql service to the variable named `REACT_APP_TALAWA_URL` in the `.env` file.
	```
	REACT_APP_TALAWA_URL="http://API-IP-ADRESS:4000/graphql/"
	```
	If you are a software developer working on your local system, then the URL would be:
	```
	REACT_APP_TALAWA_URL="http://localhost:4000/graphql/"
	```
	If you are trying to access Talawa Admin from a remote host with the API URL containing "localhost", You will have to change the API URL to
	```
	REACT_APP_TALAWA_URL="http://YOUR-REMOTE-ADDRESS:4000/graphql/"
	```
	For additional details, please refer the `How to Access the Talawa-API URL` section in the INSTALLATION.md file found in the [Talawa-API repo](https://github.com/PalisadoesFoundation/talawa-api).
	## Setting up REACT_APP_RECAPTCHA_SITE_KEY in .env file
	You may not want to setup reCAPTCHA since the project will still work. Moreover, it is recommended to not set it up in development environment.
	Just skip to the [Post Configuration Steps](#post-configuration-steps) if you don't want to set it up. Else, read the following steps.
	If you want to setup Google reCAPTCHA now, you may refer to the `RECAPTCHA` section in the INSTALLATION.md file found in [Talawa-API repo](https://github.com/PalisadoesFoundation/talawa-api).
	`Talawa-admin` needs the `reCAPTCHA site key` for the `reCAPTCHA` service you set up during `talawa-api` installation as shown in this screenshot:
	
	Copy/paste this `reCAPTCHA site key` to the variable named `REACT_APP_RECAPTCHA_SITE_KEY` in `.env` file.
	```
	REACT_APP_RECAPTCHA_SITE_KEY="this_is_the_recaptcha_key"
	```
	## Setting up Compiletime and Runtime logs
	Set the `ALLOW_LOGS` to "YES" if you want warnings, info, and error messages in your console, or leave it blank if you don't need them or want to keep the console clean.

Tools

LanguageTool

[uncategorized] ~158-~158: 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] ~203-~203: 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] ~207-~207: 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] ~221-~221: 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)

Markdownlint

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

---

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