Fix: The partial visibility of a checkmark when password field loses focus

[nishika-7]

What kind of change does this PR introduce?

The PR is a bug fix

Issue Number:

Fixes #2692

Did you add tests for your changes?

No

Snapshots/Videos:

**If relevant, did you update the documentation?
Not applicable

Summary

This Pull Request fixes a bug in password validation field. Previously, a password validation checkmark remained partially visible after the password input field lost focus. The update ensures that the password validation field disappears when password input field loses focus.

Does this PR introduce a breaking change?

No

Have you read the contributing guide?

Yes

Summary by CodeRabbit

• New Features

  • Introduced a new configuration file for YAML language settings and auto-review features.
  • Added a comprehensive installation guide for the Talawa Admin application.
  • Implemented localization support with new JSON files for English, French, Hindi, Spanish, and Chinese translations.
  • Added scripts for checking local storage usage and updating table of contents in Markdown files.

• Bug Fixes

  • Enhanced error handling in various scripts and configuration files.

• Documentation

  • Updated README, CONTRIBUTING, and various markdown files to improve clarity and navigation.
  • Added a detailed code style guide and issue report guidelines.

• Chores

  • Removed outdated CI and linting workflows.
  • Updated dependencies and package configurations in package.json.

• Tests

  • Added new test suites for various functionalities, ensuring robust error handling and behavior validation.

[coderabbitai]

Walkthrough

This pull request introduces a comprehensive set of configuration files, workflow updates, and localization resources for the Talawa Admin project. The changes span multiple aspects of the project, including environment setup, linting configurations, GitHub workflows, localization files, and documentation updates. The modifications aim to improve code quality, developer experience, and internationalization support.

Changes

File/Directory	Change Summary
.coderabbit.yaml	New configuration file for YAML language server with review and chat settings
.env.example	Added environment variables for port, API URL, reCAPTCHA, and logging
.eslintignore	Excluded src/components/CheckIn/tagTemplate.ts from linting
.eslintrc.json	Enhanced linting configuration with new plugins, rules, and TypeScript support
.github/workflows/	Introduced multiple workflow files for CI/CD, code quality checks, and issue management
public/locales/	Added localization files for English, French, Hindi, Spanish, and Chinese
config/	Added Babel and Vite configuration files
scripts/	Added various utility scripts for testing, mocking, and Git hooks
README.md, CONTRIBUTING.md, etc.	Updated documentation and guidelines

Assessment against linked issues

Objective	Addressed	Explanation
Password validation checkmark bug [#2692]	❓	No direct changes addressing the specific password validation UI issue were found in this PR

Possibly related PRs

• coderabbit yaml file #1991: Similar .coderabbit.yaml configuration
• Fixes: Translations Are Not Correctly Tested in Our PR Workflow  #2263: Translation file enhancements
• feat: Workflow changes which will label issues automatically as per #2256 #2390: Auto-labeling configuration
• fix failing workflow of TS compilation #2472: TypeScript compilation workflow updates
• Refactor : src/components/CheckIn/CheckInWrapper.test.tsx from Jest to Vitest #2709: Test framework refactoring
• Fix: ReCAPTCHA refresh on submitting Login/SignUp form #2943: ReCAPTCHA refresh improvements

Suggested reviewers

• @palisadoes
• @varshith257

Poem

🐰 A Rabbit's Configuration Ballad 🌈

In lines of YAML and JSON so bright,
Workflows dance with algorithmic might
Locales bloom in languages five
Our code's potential now comes alive!

Configurations, our digital friend
Where quality and creativity blend! 🚀

Tip

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

---

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

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

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

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

CodeRabbit Commands (Invoked using PR comments)

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

Other keywords and placeholders

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

Documentation and Community

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

[github-actions]

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

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

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

Our policies make our code better.

Reviewers

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

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

Reviewing Your Code

Your reviewer(s) will have the following roles:

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

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

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

Other

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

[github-actions]

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

[coderabbitai]

Actionable comments posted: 20

🧹 Nitpick comments (47)

.github/workflows/stale.yml (3)

1-11: Enhance the header documentation for better clarity

The current header refers to a README.md file without specifying its location or including key information directly. Consider adding:

• The exact path to the referenced README.md
• Brief summary of the workflow's purpose
• Key configuration guidelines directly in the header

 ##############################################################################
 ##############################################################################
 #
 # NOTE!
 #
-# Please read the README.md file in this directory that defines what should 
-# be placed in this file
+# This workflow manages stale issues and pull requests automatically.
+# For detailed configuration guidelines, please refer to:
+# .github/workflows/README.md
+#
+# Key points:
+# - Runs daily at midnight
+# - Marks issues/PRs as stale after 10 days of inactivity
+# - Closes stale items after 180 days
 #
 ##############################################################################
 ##############################################################################

🧰 Tools

🪛 yamllint (1.35.1)

[error] 6-6: trailing spaces

(trailing-spaces)

---

18-21: Remove trailing spaces

The permissions configuration is correct, but there are trailing spaces that should be removed.

 permissions:
   issues: write
-  pull-requests: write  
-  
+  pull-requests: write

🧰 Tools

🪛 yamllint (1.35.1)

[error] 20-20: trailing spaces

(trailing-spaces)

---

[error] 21-21: trailing spaces

(trailing-spaces)

---

29-43: Consider enhancing the stale configuration

The current configuration is solid but could be improved:

1. The stale labels could be more descriptive
2. Consider adding more exempt labels for common scenarios

       stale-issue-message: 'This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.'
       stale-pr-message: 'This pull request did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please verify it has no conflicts with the develop branch and rebase if needed. Mention it now if you need help or give permission to other people to finish your work.'
       close-issue-message: 'This issue did not get any activity in the past 180 days and thus has been closed. Please check if the newest release or develop branch has it fixed. Please, create a new issue if the issue is not fixed.'
       close-pr-message: 'This pull request did not get any activity in the past 180 days and thus has been closed.'
-      stale-issue-label: 'no-issue-activity'
-      stale-pr-label: 'no-pr-activity'
+      stale-issue-label: 'stale-needs-response'
+      stale-pr-label: 'stale-needs-update'
       days-before-stale: 10
       days-before-close: 180
       remove-stale-when-updated: true
       exempt-all-milestones: true
-      exempt-pr-labels: 'wip'
-      exempt-issue-labels: 'wip'
+      exempt-pr-labels: 'wip,blocked,waiting-for-review'
+      exempt-issue-labels: 'wip,blocked,need-investigation'
       operations-per-run: 30

setup.ts (3)

45-48: Inconsistent use of asynchronous file reading
The code uses fs.readFileSync in some places while using fs.readFile with a callback in others. Mixing synchronous and asynchronous file operations can introduce potential confusion or race conditions if extended further. Standardize on a single approach (preferably asynchronous) for clarity and consistency.

---

111-117: Add error handling for file read
The callback function signature suggests a possible err, but it’s not handled. Ensure that you handle any readFile errors to prevent silent failures.

---

180-182: Consider reloading environment variables
After modifying .env, reloading the variables with dotenv.config() might prevent discrepancies if the script continues to rely on process.env. This ensures the new changes are live within the same execution context.

Would you like me to propose an updated approach to reload .env?

.husky/post-merge (1)

4-4: Add support for alternative package managers
This script defaults to npm install. If your team uses Yarn or pnpm, consider detecting which package manager is in use or making it configurable to avoid unexpected dependency synchronization issues.

.husky/pre-commit (1)

4-10: Avoid wholesale git add .
After running format, lint, and type checks, git add . may inadvertently add files that the user had not intended to include in this commit. Limiting staged changes to lint-fixed files and updated docs can help maintain more atomic commits.

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

11-12: Remove trailing whitespace
Static analysis indicates trailing whitespace or unnecessary newlines in lines 11-12. Remove them to maintain code cleanliness and adhere to linting standards.

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

🧰 Tools

🪛 eslint

[error] 11-12: Delete ··⏎

(prettier/prettier)

config/vite.config.ts (1)

26-28: Port mismatch in comment
The comment still says "this sets a default port to 3000" whereas the code sets it to 4321. Consider updating the comment to reflect the correct port or reading the port from an environment variable to avoid confusion.

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

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

5-11: Centralize file-skip configuration.
It might be helpful to store the skipped file paths in a single JSON config or environment variable, so future contributors can more easily manage or update them. This fosters maintainability by decoupling the list from the script.

---

48-66: Consider adding tests for the validation script.
The script is pivotal to enforcing TSDoc usage. Automated tests or real-world integration tests (e.g., within a CI environment) would help prevent regressions, especially when more complex rules or additional skip files are introduced.

Would you like assistance in drafting a small test suite for this script?

jest.config.js (2)

33-34: Minor formatting alignment with Prettier.
Static analysis hints suggest removing or inserting commas/spaces. Run Prettier locally to auto-fix these minor style issues.

-    '^(?!.*\\.(js|jsx|ts|tsx|css|json)$)': 'jest-preview/transforms/file', 
+    '^(?!.*\\.(js|jsx|ts|tsx|css|json)$)': 'jest-preview/transforms/file',

🧰 Tools

🪛 eslint

[error] 33-33: Delete ·

(prettier/prettier)

---

[error] 34-34: Insert ,

(prettier/prettier)

---

60-65: Coverage thresholds are set leniently.
Consider incrementally increasing these thresholds to encourage better test coverage over time.

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

89-89: Adhere to Prettier’s trailing comma requirement.
Static analysis suggests adding a trailing comma for consistency and cleaner diffs.

-  console.info(
-    '\x1b[34m%s\x1b[0m',
-    '\nInfo: Consider using custom hook functions.'
-  );
+  console.info(
+    '\x1b[34m%s\x1b[0m',
+    '\nInfo: Consider using custom hook functions.',
+  );

And similarly for line 92 with any multiline function calls.

Also applies to: 92-92

🧰 Tools

🪛 eslint

[error] 89-89: Insert ,

(prettier/prettier)

.github/workflows/eslint_disable_check.py (3)

29-39: Consider extracting the regex pattern as a constant for reusability.
Separating the regex pattern into a module-level constant can enhance readability and make it easier to maintain or modify the pattern in the future.

- def has_eslint_disable(file_path):
-     eslint_disable_pattern = re.compile(r'//\s*eslint-disable(?:-next-line|-line)?', re.IGNORECASE)
+ ESLINT_DISABLE_PATTERN = re.compile(r'//\s*eslint-disable(?:-next-line|-line)?', re.IGNORECASE)

+ def has_eslint_disable(file_path):
      try:
          with open(file_path, 'r', encoding='utf-8') as file:
              content = file.read()
              return bool(ESLINT_DISABLE_PATTERN.search(content))
      except Exception as e:
          print(f"Error reading file {file_path}: {e}")
          return False

---

61-61: Rename the unused loop variable to _dirs.
Static analysis indicates that the variable dirs is unused in this loop. Renaming it to _dirs is more Pythonic and signals that it's intentionally ignored.

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

🧰 Tools

🪛 Ruff (0.8.2)

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

Rename unused dirs to _dirs

(B007)

---

113-122: Enhance user feedback for zero ESLint-disable usage.
Currently, when no eslint-disable statements are found, the script prints a success message. Consider extending the message to show how many files were checked or to note that the check is complete for clarity.

.github/workflows/compare_translations.py (2)

64-73: Clarify function docstring parameters.
The docstring mentions default_file and other_file in separate lines. Consider formatting them consistently or combining them into a single bullet for better readability.

---

135-135: Raise chained exception for better debugging.
Use raise ... from e to preserve original traceback context.

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

🧰 Tools

🪛 Ruff (0.8.2)

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

(B904)

.github/workflows/countline.py (4)

35-55: Potentially support TypeScript or JavaScript analysis.
If this repository has TypeScript or JavaScript files in lib or test, consider enhancing _valid_filename to check if .ts or .js files might be relevant. Right now, the function only checks for invalid segments like .test. or .spec., but not whether .ts or .js are acceptable.

---

146-195: Allow user override for directories of interest.
Currently, you hardcode lib, src, and test paths. Consider adding support for a CLI argument specifying which directories to check for lines of code, making the script more flexible.

---

256-264: Skip commented lines more robustly.
Only skipping lines that start with # or / might miss other comment forms (e.g., <!-- --> in HTML/JSX). If needed, you could provide an optional extended check for multi-line comments or additional comment syntaxes.

---

278-290: Suggest linking to relevant style or design guidelines for line limits.
Mentioning a link or reference to a coding style guide or codebase-wide best practices regarding line limits might provide additional context for contributors.

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

2-10: Standardize punctuation and message formatting

The messages have inconsistent punctuation:

• Some use exclamation marks while others don't
• Inconsistent capitalization (e.g., "Authorised" vs "not found")
• Template variables are used differently ("{{msg}}" vs "{{entity}}")

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

35-36: Format URL as proper Markdown link

The bare URL should be formatted as a proper Markdown link for better readability and to comply with Markdown best practices.

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

🧰 Tools

🪛 Markdownlint (0.37.0)

36-36: null
Bare URL used

(MD034, no-bare-urls)

---

33-34: Use proper heading syntax

Use proper Markdown heading syntax instead of bold text for section headers.

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

🧰 Tools

🪛 Markdownlint (0.37.0)

33-33: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

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

14-20: Consider limiting workflow triggers

The workflow currently runs on all branches for both pull requests and pushes. This might lead to unnecessary runs and consume GitHub Actions minutes.

Consider limiting the workflow to specific branches:

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

🧰 Tools

🪛 yamllint (1.35.1)

[error] 17-17: trailing spaces

(trailing-spaces)

---

[error] 20-20: trailing spaces

(trailing-spaces)

.github/workflows/README.md (1)

1-47: LGTM with minor fixes needed

The workflow guidelines are well-structured and comprehensive. However, there are a couple of minor issues to address:

1. Line 24: Remove the repeated word "to"
2. Line 35: Use "e.g." instead of "eg." as it's the correct abbreviation format

-      1. Place all actions related to to this in the `pull-request-target.yml` file.
+      1. Place all actions related to this in the `pull-request-target.yml` file.
-1. Jobs only work correctly if they have a dedicated file (eg. `CodeQL`)
+1. Jobs only work correctly if they have a dedicated file (e.g. `CodeQL`)

🧰 Tools

🪛 LanguageTool

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

(ENGLISH_WORD_REPEAT_RULE)

---

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

(E_G)

.github/workflows/issue.yml (1)

6-6: Remove trailing spaces

There are trailing spaces at the end of this line.

-# be placed in this file 
+# be placed in this file

🧰 Tools

🪛 yamllint (1.35.1)

[error] 6-6: trailing spaces

(trailing-spaces)

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

7-7: Remove trailing space in translation string.

The translation for "noResultsFoundFor" has a trailing space that should be removed.

-  "noResultsFoundFor": "No se aplicaron filtros ",
+  "noResultsFoundFor": "No se aplicaron filtros"

ISSUE_GUIDELINES.md (2)

29-29: Fix sentence structure.

The sentence has grammatical issues and appears to be a combination of two incomplete thoughts.

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

---

44-44: Capitalize "Slack" as it's a proper noun.

The word "slack" should be capitalized when referring to the communication platform.

-   2. Ask our contributors to assign it to you in `#talawa` slack channel.
+   2. Ask our contributors to assign it to you in `#talawa` Slack channel.
-1. Join our `#talawa-github` slack channel for automatic issue and pull request updates.
+1. Join our `#talawa-github` Slack channel for automatic issue and pull request updates.
-1. Discuss issues in our various slack channels when necessary
+1. Discuss issues in our various Slack channels when necessary

Also applies to: 53-53, 57-57

🧰 Tools

🪛 LanguageTool

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

(ON_SKYPE)

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

41-41: Fix inconsistent word spacing in Hindi translation.

The word "पासवर्ड" (password) has inconsistent spacing.

-  "enterPassword": "पास वर्ड दर्ज करें",
+  "enterPassword": "पासवर्ड दर्ज करें",

README.md (2)

53-53: Fix markdown heading formatting

Remove extra spaces after the hash symbol in the heading.

-#  Videos
+# Videos

🧰 Tools

🪛 Markdownlint (0.37.0)

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

(MD019, no-multiple-space-atx)

---

56-56: Add hyphen in compound adjective

The term "open source" should be hyphenated when used as a compound adjective before "contributors".

-new open source contributors
+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)

.eslintrc.json (2)

70-76: Consider relaxing explicit function return type requirement

The current configuration requires explicit return types for all functions, which might be overly strict and reduce code readability in cases where TypeScript's type inference is sufficient.

Consider allowing implicit return types for simple functions:

    "@typescript-eslint/explicit-function-return-type": [
      2,
      {
        "allowExpressions": true,
-       "allowTypedFunctionExpressions": true
+       "allowTypedFunctionExpressions": true,
+       "allowDirectConstAssertionInArrowFunctions": true,
+       "allowConciseArrowFunctionExpressionsStartingWithVoid": true
      }
    ],

---

81-85: Consider relaxing interface naming convention

The current naming convention requires interfaces to start with either "Interface" or "TestInterface", which might lead to verbose and redundant naming.

Consider allowing PascalCase without mandatory prefixes:

      {
        "selector": "interface",
-       "format": ["PascalCase"],
-       "prefix": ["Interface", "TestInterface"]
+       "format": ["PascalCase"]
      },

PR_GUIDELINES.md (1)

31-34: Code examples need language specifiers

The fenced code blocks should specify their language for proper syntax highlighting.

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

Also applies to: 59-62

🧰 Tools

🪛 Markdownlint (0.37.0)

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

(MD040, fenced-code-language)

CODE_STYLE.md (1)

58-89: Code examples need language specifiers

The fenced code blocks should specify their language for proper syntax highlighting.

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

Also applies to: 173-183

🧰 Tools

🪛 Markdownlint (0.37.0)

73-73: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

75-75: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

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)

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

225-226: Consider adjusting the code coverage threshold

The minimum coverage threshold of 95% is quite high for a UI project, especially one focused on bug fixes. This might discourage contributors from submitting small but important fixes.

Consider lowering the threshold to a more reasonable value (e.g., 80%) for UI components, while maintaining higher coverage requirements for critical business logic.

CONTRIBUTING.md (1)

95-107: Enhance test coverage documentation

The test coverage documentation is well structured but could be more specific about UI component testing.

Consider adding a section about testing UI components, particularly for visual regression testing which would be relevant for the password validation checkmark issue this PR addresses.

🧰 Tools

🪛 Markdownlint (0.37.0)

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

(MD040, fenced-code-language)

INSTALLATION.md (1)

246-247: Clarify logging configuration

The logging configuration explanation is ambiguous and could lead to confusion.

Apply this diff to improve clarity:

-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` environment variable:
+- Set to "YES" to enable console logging (warnings, info, and error messages)
+- Leave blank or set to any other value to disable console logging
+
+This setting is useful for debugging but can be disabled to keep the console clean.

🧰 Tools

🪛 LanguageTool

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

(MD_PRP_QUESTION_MARK)

schema.graphql (1)

1114-1117: Enhance subscription security

The subscription operations lack authentication and authorization checks. This could lead to unauthorized access to real-time data.

Consider:

1. Adding the @auth directive to subscription fields
2. Implementing subscription-specific authorization logic
3. Adding rate limiting for subscriptions

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

27-28: Fix markdown formatting for URL

The bare URL should be properly formatted as a markdown link for better readability and maintainability.

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

🧰 Tools

🪛 Markdownlint (0.37.0)

28-28: null
Bare URL used

(MD034, no-bare-urls)

---

25-26: Use proper markdown heading

Using bold text instead of a proper heading affects document structure and accessibility.

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

🧰 Tools

🪛 Markdownlint (0.37.0)

25-25: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

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

1-16: Consider defining or removing the TSDoc tag "@pdfme" to avoid lint errors.
Though this file is JavaScript, certain lint rules or TSDoc syntax can trigger false positives. You may suppress or fix the tag if truly needed.

🧰 Tools

🪛 eslint

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

(tsdoc/syntax)

---

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

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

---

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

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

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b465221 and 621cc0e.

⛔ Files ignored due to path filters (75)

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

📒 Files selected for processing (82)

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

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

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

💤 Files with no reviewable changes (13)

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

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

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

🧰 Additional context used

📓 Learnings (1)

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

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

🪛 eslint

scripts/custom-test-env.js

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

(tsdoc/syntax)

---

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

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

---

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

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

scripts/githooks/update-toc.js

[error] 11-12: Delete ··⏎

(prettier/prettier)

jest.config.js

[error] 33-33: Delete ·

(prettier/prettier)

---

[error] 34-34: Insert ,

(prettier/prettier)

scripts/githooks/check-localstorage-usage.js

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

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

---

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

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

---

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

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

---

[error] 89-89: Insert ,

(prettier/prettier)

---

[error] 92-92: Insert ,

(prettier/prettier)

🪛 yamllint (1.35.1)

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

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 13-13: trailing spaces

(trailing-spaces)

---

[error] 15-15: trailing spaces

(trailing-spaces)

---

[error] 27-27: trailing spaces

(trailing-spaces)

---

[error] 28-28: trailing spaces

(trailing-spaces)

---

[error] 29-29: trailing spaces

(trailing-spaces)

---

[error] 31-31: trailing spaces

(trailing-spaces)

---

[error] 33-33: trailing spaces

(trailing-spaces)

---

[error] 34-34: trailing spaces

(trailing-spaces)

---

[error] 36-36: trailing spaces

(trailing-spaces)

---

[error] 41-41: trailing spaces

(trailing-spaces)

---

[error] 46-46: trailing spaces

(trailing-spaces)

---

[error] 71-71: trailing spaces

(trailing-spaces)

.github/workflows/stale.yml

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 20-20: trailing spaces

(trailing-spaces)

---

[error] 21-21: trailing spaces

(trailing-spaces)

.github/workflows/issue.yml

[error] 6-6: trailing spaces

(trailing-spaces)

---

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

(indentation)

---

[warning] 66-66: too many blank lines

(1 > 0) (empty-lines)

.github/workflows/codeql-codescan.yml

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 17-17: trailing spaces

(trailing-spaces)

---

[error] 20-20: trailing spaces

(trailing-spaces)

---

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

(indentation)

---

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

(indentation)

.github/workflows/push.yml

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 17-17: trailing spaces

(trailing-spaces)

---

[error] 18-18: trailing spaces

(trailing-spaces)

---

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

(indentation)

---

[error] 21-21: trailing spaces

(trailing-spaces)

---

[error] 50-50: trailing spaces

(trailing-spaces)

---

[warning] 62-62: too many blank lines

(1 > 0) (empty-lines)

.github/workflows/pull-request.yml

[error] 49-49: trailing spaces

(trailing-spaces)

---

[error] 60-60: trailing spaces

(trailing-spaces)

---

[error] 63-63: trailing spaces

(trailing-spaces)

---

[error] 92-92: trailing spaces

(trailing-spaces)

---

[error] 126-126: trailing spaces

(trailing-spaces)

---

[error] 129-129: trailing spaces

(trailing-spaces)

---

[error] 150-150: trailing spaces

(trailing-spaces)

---

[error] 157-157: trailing spaces

(trailing-spaces)

---

[error] 197-197: trailing spaces

(trailing-spaces)

---

[error] 201-201: trailing spaces

(trailing-spaces)

---

[error] 204-204: trailing spaces

(trailing-spaces)

---

[error] 205-205: trailing spaces

(trailing-spaces)

---

[error] 213-213: trailing spaces

(trailing-spaces)

---

[error] 243-243: trailing spaces

(trailing-spaces)

---

[error] 249-249: trailing spaces

(trailing-spaces)

---

[error] 251-251: trailing spaces

(trailing-spaces)

🪛 Markdownlint (0.37.0)

README.md

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

(MD019, no-multiple-space-atx)

CONTRIBUTING.md

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

158-158: null
No empty links

(MD042, no-empty-links)

---

159-159: null
No empty links

(MD042, no-empty-links)

---

161-161: null
No empty links

(MD042, no-empty-links)

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)

PR_GUIDELINES.md

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

.github/ISSUE_TEMPLATE/bug-report.md

36-36: null
Bare URL used

(MD034, no-bare-urls)

---

33-33: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

DOCUMENTATION.md

25-25: null
Bare URL used

(MD034, no-bare-urls)

INSTALLATION.md

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

(MD001, heading-increment)

---

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

(MD007, ul-indent)

---

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

(MD007, ul-indent)

---

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

(MD014, commands-show-output)

---

105-105: null
Bare URL used

(MD034, no-bare-urls)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

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

(MD046, code-block-style)

---

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

(MD046, code-block-style)

---

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

(MD051, link-fragments)

---

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

(MD051, link-fragments)

.github/ISSUE_TEMPLATE/feature-request.md

28-28: null
Bare URL used

(MD034, no-bare-urls)

---

25-25: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

🪛 LanguageTool

README.md

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

CONTRIBUTING.md

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

(INSERT_PLEASE)

---

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

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

(THE_SUPERLATIVE)

---

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

(UNLIKELY_OPENING_PUNCTUATION)

---

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

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

(IF_THERE_COMMA)

---

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

(RB_LY_COMMA)

---

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

(FIRST_SERVED)

---

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

(ON_SKYPE)

---

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

(EN_WORDINESS_PREMIUM_LAST_BUT_NOT_THE_LEAST)

---

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

(MISSING_TO_BETWEEN_BE_AND_VB)

---

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

(ON_SKYPE)

---

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

(EN_A_VS_AN)

---

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

(DURING_THAT_TIME_COMMA)

---

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

(MAC_OS)

---

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

(BE_VBP_IN)

---

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

(ON_SKYPE)

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)

PR_GUIDELINES.md

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

(UNLIKELY_OPENING_PUNCTUATION)

---

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

(IN_ORDER_TO_PREMIUM)

---

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

(SPLIT_INFINITIVE)

---

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

(EN_WEAK_ADJECTIVE)

---

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

(SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)

---

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

(FIX_RESOLVE)

---

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

(SOONER_OR_LATER)

---

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

(COMMA_COMPOUND_SENTENCE)

---

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

(MAKE_CHANGES)

.github/workflows/README.md

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

(ENGLISH_WORD_REPEAT_RULE)

---

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

(E_G)

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)

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)

INSTALLATION.md

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

(ENGLISH_WORD_REPEAT_RULE)

---

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

(DURING_THAT_TIME_COMMA)

---

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[uncategorized] ~61-~61: Possible missing comma found.
Context: ...` knowledge is required for open source contribution so make sure you're comfortable with it...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[uncategorized] ~64-~64: Possible missing comma found.
Context: ...ithub. ## Setting up this repository First you need a local copy of talawa-admin`...

(AI_HYDRA_LEO_MISSING_COMMA)

---

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

(NOUN_VERB_CONFUSION)

---

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

(MAC_OS)

---

[uncategorized] ~69-~69: Possible missing article found.
Context: ...to do this is to right-click and choose appropriate option based on your OS. 3. **For Our O...

(AI_HYDRA_LEO_MISSING_THE)

---

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

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

(MAC_OS)

---

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

(ENGLISH_WORD_REPEAT_RULE)

---

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

(MAC_OS)

---

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

(NOUN_VERB_CONFUSION)

---

[uncategorized] ~130-~130: Possible missing comma found.
Context: ...stall TypeScript, you can use the npm command which comes with node.js: ```bash np...

(AI_HYDRA_LEO_MISSING_COMMA)

---

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

(AI_HYDRA_LEO_MISSING_COMMA)

---

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

(COMMA_COMPOUND_SENTENCE)

---

[uncategorized] ~162-~162: Possible missing comma found.
Context: ...ve to create it. For a sample of .env file there is a file named .env.example in...

(AI_HYDRA_LEO_MISSING_COMMA)

---

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

(NOUN_VERB_CONFUSION)

---

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

(NOUN_VERB_CONFUSION)

---

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

(AI_HYDRA_LEO_MISSING_COMMA)

---

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

(MD_PRP_QUESTION_MARK)

---

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

(BY_DEFAULT_COMMA)

---

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

(AI_HYDRA_LEO_MISSING_COMMA)

---

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

(PRP_MD_NN)

CODE_OF_CONDUCT.md

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

(ENGLISH_WORD_REPEAT_RULE)

🪛 actionlint (1.7.4)

.github/workflows/stale.yml

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

(action)

.github/workflows/issue.yml

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

(action)

.github/workflows/codeql-codescan.yml

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

(action)

---

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

(action)

---

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

(action)

.github/workflows/pull-request.yml

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

(expression)

---

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

(shellcheck)

---

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

(expression)

🪛 Ruff (0.8.2)

.github/workflows/compare_translations.py

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

(B904)

.github/workflows/eslint_disable_check.py

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

Rename unused dirs to _dirs

(B007)

🔇 Additional comments (29)

.gitignore (4)

3-5: LGTM: Package manager lock files exclusion

Good practice to ignore lock files when using npm as the primary package manager.

---

13-14: LGTM: Test coverage reports exclusion

Correctly excludes coverage reports and codecov artifacts.

---

21-21: LGTM: Environment file exclusion

Good security practice to ignore .env files containing sensitive configuration.

---

31-37: LGTM: Editor and debug files exclusion

Appropriate exclusion of editor-specific files and debug logs.

.github/workflows/stale.yml (1)

12-17: LGTM! Well-configured workflow trigger

The workflow name is descriptive and the schedule is appropriately set to run daily at midnight using standard cron syntax.

setup.ts (2)

13-19: Handle missing .env.example gracefully
Currently, if .env.example doesn't exist or fails to read for any reason, the script may proceed without properly handling the error. Consider wrapping file operations in try/catch blocks or verifying file existence before reading to provide a more robust error handling strategy.

---

72-76: Validate potential invalid URLs
When prompting and validating the endpoint, only checkConnection(url.origin) is performed. Consider additional checks (e.g., catching malformed URLs, verifying path segments, or adding robust error messages) to refine user feedback and prevent misconfiguration.

config/vite.config.ts (1)

13-23: Verify environment variable usage
Using EnvironmentPlugin('all') may include extra variables that aren't strictly needed, leading to a large and potentially sensitive environment payload. Verify which variables need exposure and limit them accordingly for security and clarity.

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

1-2: Imports look good and are aligned with modern ECMAScript standards.

---

14-35: Robust recursive directory traversal.
The approach handles errors without breaking the flow and excludes non-.tsx files properly. This should work reliably for typical directory structures.

jest.config.js (3)

1-10: Overall Jest configuration looks solid.
Including whatwg-fetch as a setup file is a helpful choice for browser-like testing scenarios.

---

11-19: Good choice of transforms for diverse file types.
Your Babel Jest transform covers JS/TS code, and dedicated transformations for CSS and other file types help maintain test consistency.

---

66-71: Efficiently ignoring irrelevant test paths.
This keeps the CI pipeline clean by filtering out build and public assets. Looks good.

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

10-10: Ignore missing function return type ESLint warnings for JavaScript.
The rule @typescript-eslint/explicit-function-return-type isn't applicable to .js files in this project. You can safely disable or override this rule for .js files if it keeps raising false positives.

Also applies to: 20-20, 43-43

🧰 Tools

🪛 eslint

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

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

.github/workflows/talawa_admin_md_mdx_format_adjuster.py (3)

19-44: Escaping special MDX characters.
The regex approach properly checks for unescaped <, >, {, and }. This is a straightforward solution to reduce formatting errors when transitioning from Markdown to MDX.

---

45-65: Selective file re-write.
Writing back changes only when necessary avoids unnecessary file modifications and keeps the git history cleaner.

---

66-96: Command-line interface for directory processing.
Using argparse for collecting a --directory argument is a neat, minimal approach that clearly communicates the script’s intended usage. Nicely done.

.coderabbit.yaml (2)

5-10: Confirm that enabling all review features aligns with your project needs.
You have multiple advanced features enabled (poem, high_level_summary, etc.). Ensure these auto-generated items align with your workflow requirements.

---

11-16: Validate that the listed base branches are correct.
The config includes two base branches: develop and main. Double-check that these are indeed the branches used in this repository and align with your typical PR workflow.

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

1-44: Verify PR objective alignment

The changes in this PR appear to be unrelated to the stated objective of "fixing partial visibility of checkmark when password field loses focus". The files being modified are for localization, templates, and workflows, but none appear to address the UI issue mentioned in the PR description.

Please clarify if:

1. These changes are intended to be part of this PR
2. The missing UI-related changes will be added in a separate commit
3. The PR description needs to be updated to reflect these changes instead

🧰 Tools

🪛 actionlint (1.7.4)

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

(action)

---

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

(action)

---

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

(action)

🪛 yamllint (1.35.1)

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 17-17: trailing spaces

(trailing-spaces)

---

[error] 20-20: trailing spaces

(trailing-spaces)

---

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

(indentation)

---

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

(indentation)

.github/workflows/issue.yml (1)

1-1: ⚠️ Major discrepancy between PR objective and actual changes

The PR description states it fixes "The partial visibility of a checkmark when password field loses focus" (Issue #2692). However, the changes in this PR appear completely unrelated to this objective:

1. .github/workflows/README.md: New workflow documentation
2. public/locales/zh/common.json: Chinese translations
3. .github/workflows/issue.yml: Issue management workflow updates

Please clarify this discrepancy. Are these the correct files for fixing the password validation UI bug?

package.json (3)

2-3: Verify the major version bump

The version has been increased from 0.1.0 to 3.0.0, which is a major version bump. Please ensure this aligns with your versioning strategy and that all breaking changes are documented.

---

73-89: Verify the new scripts configuration

New scripts have been added for linting, formatting, and testing. While these are good additions:

1. Ensure the new scripts don't break existing CI/CD pipelines
2. Verify that the new vite configuration works with the existing setup

---

160-162: Verify Node.js version requirement

The engine field requires Node.js >=20.x. Ensure all development and deployment environments meet this requirement.

schema.graphql (1)

1-3: Review auth directive implementation

The @auth directive is defined but lacks implementation details for the authorization logic. This could lead to security vulnerabilities if not properly implemented.

Consider implementing a proper authorization mechanism that:

1. Validates user permissions
2. Handles token verification
3. Implements role-based access control

CODE_OF_CONDUCT.md (1)

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

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

🧰 Tools

🪛 LanguageTool

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

(ENGLISH_WORD_REPEAT_RULE)

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

1-5: Mock function appears correct and concise.
This Jest mock correctly abstracts away the actual avatar generation, returning a controlled mock data URI. Great job ensuring a simple, testable approach.

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

1-22: Implementation looks robust.
This mock function sensibly validates inputs and returns a controlled, pseudo PDF data array. Good clarity and strong error handling.

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

1-47: Well-structured test suite.
These tests thoroughly cover normal and error conditions, enforcing correct behavior of the mocked generate function.

[coderabbitai]

⚠️ Potential issue

Update actions/stale action version for compatibility

The current version might have compatibility issues with the GitHub Actions runner.

     steps:
-    - uses: actions/stale@v8
+    - uses: actions/stale@v9

📝 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

	jobs:
	stale:
	runs-on: ubuntu-latest
	steps:
	- uses: actions/stale@v8
	jobs:
	stale:
	runs-on: ubuntu-latest
	steps:
	- uses: actions/stale@v9

🧰 Tools

🪛 actionlint (1.7.4)

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

(action)

[coderabbitai]

🛠️ Refactor suggestion

Consider returning collected errors instead of exiting.
Globally exiting from the function can limit testing or reusability. You might consider returning the errors instead, letting the caller decide whether to exit or handle them differently.

[coderabbitai]

⚠️ Potential issue

Fix incorrect icon size specification

The size "16x16" for logo192.png appears incorrect as the filename implies it should be "192x192".

-      "sizes": "16x16"
+      "sizes": "192x192"

📝 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

	"sizes": "16x16"
	"sizes": "192x192"

[coderabbitai]

⚠️ Potential issue

❌ PR changes do not address the stated objective

The current changes (localization files and manifest updates) do not address the PR's objective of fixing the "partial visibility of checkmark when password field loses focus" issue. Additionally, some changes introduce potential issues (incorrect icon size in manifest).

To properly fix the password validation UI issue:

1. Focus on the relevant UI components and styles
2. Include changes to the password field validation logic
3. Update the checkmark visibility handling
4. Add tests to verify the fix

Would you like assistance in identifying the correct files to modify?

[coderabbitai]

⚠️ Potential issue

Translate English messages to Spanish

The following messages need to be translated to Spanish to maintain consistency:

• "Talawa-API service is unavailable!..."
• "Not found"
• "An unknown error occurred..."
• "Sorry! you are not Authorised!"
• "Error sending mail"
• "Email not registered"
• "Oops! The Page you requested was not found!"

Would you like me to help with the Spanish translations for these messages?

[coderabbitai]

⚠️ Potential issue

Secure the branch comparison script

The script uses untrusted input directly in the inline script. This could be a security risk.

Apply this diff to use environment variables instead:

-        if: ${{ github.event.pull_request.base.ref == github.event.pull_request.head.ref }}
+        env:
+          BASE_REF: ${{ github.event.pull_request.base.ref }}
+          HEAD_REF: ${{ github.event.pull_request.head.ref }}
         run: |
-          echo "Source Branch ${{ github.event.pull_request.head.ref }}"
-          echo "Target Branch ${{ github.event.pull_request.base.ref }}"
+          echo "Source Branch $HEAD_REF"
+          echo "Target Branch $BASE_REF"
+          if [ "$BASE_REF" = "$HEAD_REF" ]; then
           echo "Error: Source and Target Branches are the same. Please ensure they are different."
           exit 1
+          fi

📝 Committable suggestion

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

Suggested change

	run: |
	echo "Source Branch ${{ github.event.pull_request.head.ref }}"
	echo "Target Branch ${{ github.event.pull_request.base.ref }}"
	echo "Error: Source and Target Branches are the same. Please ensure they are different."
	exit 1
	env:
	BASE_REF: ${{ github.event.pull_request.base.ref }}
	HEAD_REF: ${{ github.event.pull_request.head.ref }}
	run: |
	echo "Source Branch $HEAD_REF"
	echo "Target Branch $BASE_REF"
	if [ "$BASE_REF" = "$HEAD_REF" ]; then
	echo "Error: Source and Target Branches are the same. Please ensure they are different."
	exit 1
	fi

🧰 Tools

🪛 actionlint (1.7.4)

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

(expression)

[coderabbitai]

⚠️ Potential issue

Remove duplicate enum definition

The AdvertisementType enum is defined twice in the schema. This duplication could lead to confusion and maintenance issues.

Remove one of the duplicate definitions:

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

Also applies to: 67-71

[coderabbitai]

⚠️ Potential issue

Remove duplicate type definition

The UserPhone type is defined twice in the schema. This duplication should be removed to maintain schema consistency.

Remove one of the duplicate definitions:

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

Also applies to: 1348-1352

[coderabbitai]

⚠️ Potential issue

Remove duplicate type definition

The OrganizationCustomField type is defined twice in the schema. This duplication could cause confusion and schema validation errors.

Remove the duplicate type definition:

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

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

[coderabbitai]

🛠️ Refactor suggestion

Inconsistent mutation parameter style

The createAdvertisement mutation uses individual parameters instead of an input type, unlike other similar mutations. This inconsistency makes the API harder to maintain and use.

Refactor to use the existing CreateAdvertisementInput type:

-  createAdvertisement(
-    endDate: Date!
-    link: String!
-    name: String!
-    orgId: ID!
-    startDate: Date!
-    type: String!
-  ): Advertisement!
+  createAdvertisement(input: CreateAdvertisementInput!): CreateAdvertisementPayload!

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

[palisadoes]

This PR has too many submitted files that are out of scope of the original issue.

Please ensure the following:

1. Fetch the latest upstream/develop-postgres files
2. Create a new local branch based on the latest upstream/develop-postgres branch.
   1. Your new local branch must not have the same name
3. Make your PR modifications based on this new local branch
4. Submit your PRs against our develop-postgres branch.

Please ask the slack channels for assistance.

Closing