fixed Event and Holiday Calendar View

[gurramkarthiknetha]

This feature displays an interactive calendar view for tracking events and holidays. The calendar highlights holidays and user/organization-created events for the selected month, with color-coded markers for easy identification

What kind of change does this PR introduce?
This PR introduces a new feature for displaying an interactive event calendar with a list of holidays and user/organization-created events.

Issue Number:

Fixes #1887

Did you add tests for your changes?
Yes, unit tests have been added to ensure the functionality works as expected.

Snapshots/Videos:
Snapshots and a short demonstration video showcasing the feature have been attached for better understanding.

If relevant, did you update the documentation?
Yes, the relevant sections in the Talawa-Docs have been updated to include details about the new feature.
Summary

This feature addresses the need for a more user-friendly and comprehensive event calendar.

Problem: The existing calendar lacked the ability to display a list of holidays and events in an organized manner.
Solution:
A list of holidays and events is now displayed below the calendar.
Color-coding has been implemented to distinguish between holidays and events for improved usability.
The UI aligns with the Figma design shared by the team.

Does this PR introduce a breaking change?

No, this PR does not introduce any breaking changes.

Other information

The Figma design used for this implementation can be found here.
This PR follows the project’s contribution guidelines and is submitted against the develop branch, as recommended.

Have you read the contributing guide?

Yes

Summary by CodeRabbit

Summary by CodeRabbit

• New Features

  • Introduced a new configuration file for automated dependency updates.
  • Added support for multiple languages with comprehensive localization files for English, French, Hindi, Spanish, and Chinese.
  • Implemented a setup script for easier environment configuration, including reCAPTCHA support and API URL validation.
  • Enhanced the GraphQL schema with new types and directives for better data management and security.

• Bug Fixes

  • Improved error handling for localization and API interactions.
  • Fixed issues related to localStorage usage detection in the codebase.

• Chores

  • Updated the README and documentation files for better user guidance.
  • Refined the CI/CD workflows for more efficient testing and deployment.
  • Modified GitHub issue and pull request templates for improved clarity and contributor guidance.
  • Updated project dependencies for enhanced performance and functionality.

[coderabbitai]

Walkthrough

This pull request introduces significant updates across multiple files, including new configuration files, scripts, and localization resources. Key changes include the addition of a .coderabbit.yaml file for YAML language server settings, a .env.example file for environment variable configurations, and various localization JSON files for multiple languages. Additionally, updates to GitHub workflows and templates enhance the project's structure and usability. The modifications aim to improve the configuration, testing, and documentation processes within the Talawa project.

Changes

File Path	Change Summary
.coderabbit.yaml	New configuration file for YAML language server settings.
.env.example	New template for environment variables including PORT, REACT_APP_TALAWA_URL, and others.
.eslintignore	Excluded src/components/CheckIn/tagTemplate.ts from linting.
.eslintrc.json	Updated ESLint configuration with new plugins, rules, and environment settings.
.github/ISSUE_TEMPLATE/bug-report.md	Modified formatting, added a section for internship candidates.
.github/ISSUE_TEMPLATE/feature-request.md	Updated metadata and added a section for internship candidates.
.github/dependabot.yaml	New configuration file for Dependabot to automate dependency updates.
.github/pull_request_template.md	Enhanced guidance for contributors regarding branching strategy and additional fields.
.github/workflows/README.md	New README file outlining guidelines for managing workflow files.
.github/workflows/codeql-codescan.yml	New workflow for automating CodeQL analysis.
.github/workflows/pull-request.yml	New comprehensive workflow for managing pull requests with multiple jobs for quality checks.
README.md	Updated structure and content, including new sections for community engagement and documentation.
package.json	Major updates to project name, version, and dependencies; added scripts for Vite and linting.
public/locales/en/common.json	New localization file for English UI elements.
public/locales/fr/common.json	New localization file for French UI elements.
public/locales/hi/common.json	New localization file for Hindi UI elements.
public/locales/sp/common.json	New localization file for Spanish UI elements.
public/locales/zh/common.json	New localization file for Chinese UI elements.
scripts/githooks/check-localstorage-usage.js	New script to check for localStorage usage in the codebase.
scripts/githooks/update-toc.js	New script to update the table of contents in Markdown files.
setup.ts	New setup script for initializing environment variables and configuration.

Assessment against linked issues

Objective	Addressed	Explanation
Add a list of holidays and events below the event calendar (#1887)	❌	The changes do not implement the requested calendar features.

Possibly related PRs

• coderabbit yaml file #1991: Introduces a .coderabbit.yaml configuration file for YAML language server settings.
• develop branch - coderabbit yaml file #1997: Adds another .coderabbit.yaml file with similar functionalities.
• Fixes: Translations Are Not Correctly Tested in Our PR Workflow  #2263: Modifies the compare_translations.py script, potentially relevant to review processes.
• feat: Workflow changes which will label issues automatically as per #2256 #2390: Introduces a JSON5 configuration for automatic labeling in GitHub workflows.
• added docker check to workflow #2414: Adds a Docker check to the workflow, potentially related to configuration settings.
• Added GitHub PR Workflow Check: Talawa Admin app starts (No Docker) #2452: Adds a workflow check for the Talawa Admin app to start without Docker.
• Updated pr template with checklist #2454: Updates the pull request template to include a checklist for CodeRabbit AI review.
• Updated pr template for develop-postgress branch #2458: Updates the pull request template for the develop-postgres branch.
• fix failing workflow of TS compilation #2472: Fixes failing workflows related to TypeScript compilation.
• reverting workflow changes #2498: Reverts workflow changes that may relate to overall workflow processes.

Suggested labels

ignore-sensitive-files-pr

Suggested reviewers

• pranshugupta54
• varshith257
• palisadoes

Poem

🐇 In the land of code where changes bloom,
A YAML file brings light to the room.
With translations for all, in languages wide,
The Talawa Admin takes a joyful stride.
So let’s hop along, with scripts that cheer,
For a brighter future, the changes are here! 🌼

---

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

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

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

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

CodeRabbit Commands (Invoked using PR comments)

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

Other keywords and placeholders

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

Documentation and Community

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

[github-actions]

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

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

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

Our policies make our code better.

Reviewers

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

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

Reviewing Your Code

Your reviewer(s) will have the following roles:

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

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

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

Other

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

[coderabbitai]

Actionable comments posted: 43

🧹 Outside diff range and nitpick comments (53)

.github/workflows/compare_translations.py (1)

155-155: Safely remove 'en' from languages list

Attempting to remove 'en' from the languages list without checking if it exists may raise a ValueError. To prevent this, check for its presence before removing.

Apply this diff to handle the potential error:

- languages.remove("en")  # Exclude default language directory
+ if "en" in languages:
+     languages.remove("en")  # Exclude default language directory

.github/workflows/countline.py (2)

255-255: Consider using 'utf-8' encoding for reading files

Currently, files are opened with 'latin-1' encoding. Unless there's a specific need for 'latin-1', using 'utf-8' is standard and supports a broader range of characters, which might prevent decoding errors.

Apply this diff to change the encoding:

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

---

267-267: Remove outdated or misleading comment

The comment suggests that a value is changed to 1 when the line rule is violated, but no such operation occurs in the code. This could confuse readers.

Apply this diff to remove the misleading comment:

- # If the line rule is voilated then the value is changed to 1

.husky/post-merge (1)

4-4: Add newline at the end of the file

It's good practice to include a newline at the end of files to adhere to POSIX standards and avoid potential issues with tools that expect this.

Apply this diff to add a newline:

 git diff HEAD^ HEAD --exit-code -- ./package.json || npm install
+

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

4-7: Fix JSDoc tag syntax

The @pdfme reference should be properly formatted as a package name.

- * A custom environment to set the TextEncoder and TextDecoder variables, that is required by @pdfme during testing.
+ * A custom environment to set the TextEncoder and TextDecoder variables, that is required by the `pdfme` package during testing.

🧰 Tools

🪛 eslint

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

(tsdoc/syntax)

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

10-13: Remove commented debug code and enhance error messages

The error handling is good, but we should:

1. Remove the commented console.log
2. Make error messages more specific about which input was empty

 if (template.schemas.length === 0 || inputs.length === 0) {
-    // console.log('pdf error: length : ', template, inputs, inputs.length);
-    throw new Error('Template or inputs cannot be empty.');
+    throw new Error(
+      `Validation failed: ${template.schemas.length === 0 ? 'template schemas' : 'inputs'} cannot be empty.`
+    );
 }

---

17-20: Consider using deterministic mock data

The current implementation uses random content which might make tests non-deterministic. Consider using a more predictable pattern for mock data generation.

-  const contentSize = Math.min(template.schemas.length, inputs.length) * 10;
-  const mockContent = Array.from({ length: contentSize }, () =>
-    Math.floor(Math.random() * 256),
-  );
+  const contentSize = Math.min(template.schemas.length, inputs.length) * 10;
+  const mockContent = Array.from({ length: contentSize }, (_, i) => i % 256);

.github/pull_request_template.md (1)

51-53: Enhance contributing guide section

The contributing guide section should be more prominent and specific.

-**Have you read the [contributing guide](https://github.com/PalisadoesFoundation/talawa-admin/blob/master/CONTRIBUTING.md)?**
-
-<!--Yes or No-->
+**Contributing Guidelines Checklist**
+
+Please confirm that you have:
+- [ ] Read the [contributing guide](https://github.com/PalisadoesFoundation/talawa-admin/blob/main/CONTRIBUTING.md)
+- [ ] Followed the coding style guidelines
+- [ ] Tested your changes locally

.github/workflows/push.yml (1)

42-48: Optimize cache key strategy

The current cache key strategy could be improved by:

1. Including package.json in the hash to detect dependency changes
2. Simplifying restore-keys to reduce fallback chains

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

jest.config.js (1)

48-51: Decide on watch plugins configuration

Either remove or uncomment the watch plugins configuration. Commented code should not be committed.

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

.github/workflows/talawa_admin_md_mdx_format_adjuster.py (1)

89-93: Add logging for processed files

Consider adding logging to track which files are being processed and any changes made.

+    import logging
+    logging.basicConfig(level=logging.INFO)
+
     # Process each Markdown file in the directory
     for root, _, files in os.walk(args.directory):
         for file in files:
             if file.lower().endswith(".md"):
+                logging.info("Processing file: %s", os.path.join(root, file))
                 process_file(os.path.join(root, file))

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

6-71: Fix YAML formatting issues

Multiple lines contain trailing spaces which should be removed for better YAML formatting.

Consider using a YAML formatter to clean up trailing spaces and ensure consistent formatting throughout the file.

🧰 Tools

🪛 yamllint (1.35.1)

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 13-13: trailing spaces

(trailing-spaces)

---

[error] 15-15: trailing spaces

(trailing-spaces)

---

[error] 27-27: trailing spaces

(trailing-spaces)

---

[error] 28-28: trailing spaces

(trailing-spaces)

---

[error] 29-29: trailing spaces

(trailing-spaces)

---

[error] 31-31: trailing spaces

(trailing-spaces)

---

[error] 33-33: trailing spaces

(trailing-spaces)

---

[error] 34-34: trailing spaces

(trailing-spaces)

---

[error] 36-36: trailing spaces

(trailing-spaces)

---

[error] 41-41: trailing spaces

(trailing-spaces)

---

[error] 46-46: trailing spaces

(trailing-spaces)

---

[error] 71-71: trailing spaces

(trailing-spaces)

.github/workflows/eslint_disable_check.py (3)

29-47: Consider enhancing the regex pattern for better accuracy.

The current pattern might miss some edge cases. Consider using a more precise pattern that accounts for possible whitespace and comment variations.

-    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)?(?:\s.*)?(?:\*/)?', re.IGNORECASE)

---

61-61: Rename unused loop variable.

The loop control variable dirs is not used in the loop body.

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

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

Rename unused dirs to _dirs

(B007)

---

91-122: Consider adding logging for better debugging.

While the error handling is good, adding logging would help with debugging and monitoring.

+import logging
+
+logging.basicConfig(
+    level=logging.INFO,
+    format='%(asctime)s - %(levelname)s - %(message)s'
+)

 def main():
     args = arg_parser_resolver()
 
     if not os.path.exists(args.directory):
-        print(f"Error: The specified directory '{args.directory}' does not exist.")
+        logging.error(f"The specified directory '{args.directory}' does not exist.")
         sys.exit(1)
 
     eslint_found = check_eslint(args.directory)
 
     if eslint_found:
-        print("ESLint-disable check failed. Exiting with error.")
+        logging.error("ESLint-disable check failed. Exiting with error.")
         sys.exit(1)
 
-    print("ESLint-disable check completed successfully.")
+    logging.info("ESLint-disable check completed successfully.")

.eslintrc.json (1)

57-69: Consider the impact of strict TypeScript rules.

While strict TypeScript rules improve code quality, some rules might be too restrictive for development velocity:

• no-explicit-any: Might be too strict for areas dealing with external APIs
• no-non-null-assertion: Could make code more verbose in cases where null is impossible

Consider allowing these with explicit documentation requirements instead of outright banning them.

PR_GUIDELINES.md (2)

31-34: Add language specifiers to code blocks.

Code blocks should specify the language for proper syntax highlighting.

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

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

Also applies to: 39-42

🧰 Tools

🪛 Markdownlint (0.35.0)

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

(MD040, fenced-code-language)

---

56-56: Improve sentence structure in the quality statement.

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

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

🧰 Tools

🪛 LanguageTool

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

(EN_WEAK_ADJECTIVE)

---

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

(SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)

CODE_OF_CONDUCT.md (1)

11-11: Fix duplicate word in navigation links

The navigation links contain a duplicate word "Enforcement". Consider combining these sections or using more specific names to differentiate them.

- - [Enforcement](#enforcement)
- - [Enforcement Guidelines](#enforcement-guidelines)
+ - [Enforcement Policy](#enforcement)
+ - [Enforcement Guidelines](#enforcement-guidelines)

🧰 Tools

🪛 LanguageTool

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

(ENGLISH_WORD_REPEAT_RULE)

CODE_STYLE.md (3)

127-138: Fix list indentation in directory structure

The directory structure section has inconsistent list indentation levels.

Consider updating the indentation to follow a consistent pattern:

`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
  - `components` - All Sass files for components
  - `content` - All Sass files for content
  - `forms` - All Sass files for forms
  - `_talawa.scss` - Partial Sass file for Talawa
  - `_utilities.scss` - Partial Sass file for utilities
  - `_variables.scss` - Partial Sass file for variables
  - `app.scss` - Main Sass file for the app

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

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)

---

58-69: Add language specifications to code blocks

Code blocks are missing language specifications, which affects syntax highlighting.

Add appropriate language specifications to code blocks:

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

- ```
+ ```typescript
import { Row, Col, Container } from 'react-bootstrap';

Also applies to: 173-183

🧰 Tools

🪛 Markdownlint (0.35.0)

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

(MD040, fenced-code-language)

---

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

(MD040, fenced-code-language)

---

71-71: Clarify Bootstrap component usage directive

The statement about component usage is too restrictive and might not cover all valid use cases.

Consider rewording to:

- All components should be either imported from React-Bootstrap library or Material UI library, components should not be written using plain Bootstrap classes and attributes without leveraging the React-Bootstrap library.
+ Prefer using React-Bootstrap or Material UI components when available. Plain Bootstrap classes can be used for styling, but component functionality should leverage React-specific libraries when possible.

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

14-17: Consider limiting the workflow trigger to specific branches.

The current configuration triggers the workflow on pull requests to any branch ('**'). Consider limiting it to only the main development branches to avoid unnecessary workflow runs.

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

CONTRIBUTING.md (2)

73-73: Fix grammatical and formatting issues.

There are several grammatical issues that should be addressed:

• "First Come First Serve" should be "First Come, First Served"
• "slack" should be capitalized as "Slack"
• Add missing commas in compound sentences

🧰 Tools

🪛 LanguageTool

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

(IF_THERE_COMMA)

---

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

(RB_LY_COMMA)

---

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

(FIRST_SERVED)

---

104-107: Add language identifiers to code blocks.

Code blocks should specify their language for proper syntax highlighting.

- ```
+ ```bash
npm install
npm run test --watchAll=false --coverage

Also applies to: 128-132, 139-145

🧰 Tools

🪛 Markdownlint (0.35.0)

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

(MD040, fenced-code-language)

INSTALLATION.md (2)

68-68: Maintain consistent OS naming.

Replace "MacOS" with "macOS" for consistency with Apple's branding.

Also applies to: 102-102, 119-119

🧰 Tools

🪛 LanguageTool

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

---

246-246: Improve clarity in environment variable description.

The description of the ALLOW_LOGS variable needs better punctuation and 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` to "YES" if you want warnings, info, and error messages in your console. Leave it blank if you don't need them or want 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)

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

35-36: Format URL using proper markdown syntax

The bare URL should be formatted using proper markdown link syntax for better readability and consistency.

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

🧰 Tools

🪛 Markdownlint (0.35.0)

36-36: null
Bare URL used

(MD034, no-bare-urls)

---

33-34: Use proper markdown heading syntax

Convert the bold text to a proper markdown heading for better document structure.

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

🧰 Tools

🪛 Markdownlint (0.35.0)

33-33: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

DOCUMENTATION.md (3)

24-25: Fix grammar and formatting in Docusaurus launch instructions

There are grammar issues and a bare URL in the launch instructions.

-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. Launch Docusaurus on your system according to the `talawa-docs` documentation. 
+    - A local version of `docs.talawa.io` will automatically launch in your browser at `http://localhost:3000`

🧰 Tools

🪛 Markdownlint (0.35.0)

25-25: null
Bare URL used

(MD034, no-bare-urls)

🪛 LanguageTool

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

(MD_BASEFORM)

---

26-27: Improve Markdown terminology and formatting

Use proper capitalization for Markdown and improve formatting clarity.

-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. Add/modify the Markdown documents to the `docs/` directory of the `talawa-docs` repository
+1. If adding a file, you will need to edit `sidebars.js` to update the [docs.talawa.io](https://docs.talawa.io/) navigation menus

🧰 Tools

🪛 LanguageTool

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

(MARKDOWN_NNP)

---

31-32: Improve final instruction formatting and clarity

The final instruction could be more professionally formatted and clearer.

-## Other information
-***PLEASE*** do not add markdown files in this repository. Add them to `talawa-docs`!
+## Important Note
+Do not add Markdown files to this repository. All documentation files should be added to the `talawa-docs` repository.

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

.github/workflows/README.md (5)

7-7: Enhance the guidance for workflow changes.

Consider expanding this section to explain how contributors can get advice (e.g., through discussions, issues) and what the review process entails.

-Any changes to files in this directory are flagged when pull requests are run. Make changes only on the advice of a contributor.
+Any changes to files in this directory are flagged during pull request checks. Before making changes:
+1. Open a discussion or issue to get guidance from maintainers
+2. Ensure your changes align with the project's CI/CD strategy
+3. Make changes only after receiving explicit approval from a contributor

---

13-15: Fix grammatical issues for better readability.

Add a comma after "Whenever possible" for proper punctuation.

-Whenever possible you must ensure that:
+Whenever possible, you must ensure that:

🧰 Tools

🪛 LanguageTool

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

(AI_HYDRA_LEO_MISSING_COMMA)

---

24-24: Remove duplicate word "to".

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

🧰 Tools

🪛 LanguageTool

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

(ENGLISH_WORD_REPEAT_RULE)

---

35-35: Fix abbreviation format.

Use the correct format for the Latin abbreviation "e.g." (exempli gratia).

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

🧰 Tools

🪛 LanguageTool

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

(E_G)

---

41-47: Enhance code quality requirements documentation.

Consider adding more context about the code quality tools and their configuration.

 1. All scripts in this directory must be written in python3 for consistency.
 1. The python3 scripts must follow the following coding standards. Run these commands against your scripts before submitting PRs that modify or create python3 scripts in this directory.
     1. Pycodestyle
     1. Pydocstyle
     1. Pylint
     1. Flake8
-1. All scripts must run a main() function.
+1. All scripts must run a main() function.
+1. Configuration files for these tools can be found in the repository root:
+    - `.pylintrc` for Pylint configuration
+    - `setup.cfg` for Pycodestyle, Pydocstyle, and Flake8 settings
+1. Minimum required code quality scores:
+    - Pylint: 9.0/10
+    - Coverage: 80%

public/manifest.json (1)

16-16: Maintain consistent asset organization

While logo512.png has been moved to the images/ directory, logo192.png remains in the root. Consider moving all image assets to the images/ directory for consistent organization.

Apply these changes:

1. Move logo192.png to the images/ directory
2. Update the manifest:

-      "src": "logo192.png",
+      "src": "images/logo192.png",

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

2-2: Fix formatting in French error message

Remove the extra period and space in talawaApiUnavailable:

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

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

5-5: Fix capitalization in error message

The word "Authorised" is inconsistently capitalized and uses British spelling. Consider using American spelling for consistency with other messages.

-  "notAuthorised": "Sorry! you are not Authorised!",
+  "notAuthorised": "Sorry! You are not authorized!"

---

10-10: Fix spelling error in error message

The word "occured" is misspelled. It should be "occurred".

-  "errorLoading": "Error occured while loading {{entity}} data"
+  "errorLoading": "Error occurred while loading {{entity}} data"

---

1-11: Ensure consistent punctuation across error messages

Some messages end with exclamation marks while others don't. Consider standardizing the punctuation:

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

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

14-20: Consider limiting the workflow trigger scope

The workflow currently runs on all branches ('**'). Consider limiting it to specific branches (e.g., main, develop) to optimize CI resources.

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/stale.yml (2)

31-34: Consider customizing stale messages for Event Calendar context

Since this PR is part of the Event and Holiday Calendar View feature, consider customizing the stale messages to be more specific to calendar-related issues and PRs.

- 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-issue-message: 'This calendar-related issue has been inactive for 10 days and will be closed in 180 days without updates. Please verify if the issue persists in the latest develop branch, particularly checking the new calendar view implementation.'

---

41-42: Consider additional exempt labels

The configuration only exempts 'wip' labeled items. Consider adding more exempt labels specific to the calendar feature development.

- exempt-pr-labels: 'wip'
- exempt-issue-labels: 'wip'
+ exempt-pr-labels: 'wip,calendar-feature,needs-review'
+ exempt-issue-labels: 'wip,calendar-feature,pending-design'

.github/workflows/issue.yml (1)

12-16: Consider handling additional issue events

The workflow currently only triggers on newly opened issues. Consider including other relevant issue events like 'reopened' or 'labeled' to ensure comprehensive issue management.

 on:
   issues:
-      types: ['opened']
+      types: ['opened', 'reopened', 'labeled']

🧰 Tools

🪛 yamllint (1.35.1)

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

(indentation)

.gitignore (3)

34-37: Consider editor configuration files.

The addition of editor-specific ignore patterns (.idea, .vscode, *.swp) seems unrelated to the calendar feature. Consider:

1. Keeping shared editor configs in version control for consistent development experience
2. Using global gitignore for personal editor files

---

Line range hint 1-37: Overall changes seem unrelated to PR objectives.

The modifications to .gitignore appear to be unrelated to the stated PR objectives of implementing an Event and Holiday Calendar View. Consider:

1. Splitting these changes into a separate PR focused on project configuration
2. Keeping only changes directly related to the calendar feature in this PR

---

Environment patterns in .gitignore are justified but documentation is missing

The multiple environment patterns in .gitignore are necessary as the codebase actively uses environment variables for configuration:

• Port configuration
• Talawa API URL
• reCAPTCHA settings
• WebSocket URL

However, there's no .env.example file to document these required variables. Please:

1. Create an .env.example file documenting these required variables:
   • PORT
   • REACT_APP_TALAWA_URL
   • REACT_APP_RECAPTCHA_SITE_KEY
   • REACT_APP_USE_RECAPTCHA
   • REACT_APP_BACKEND_WEBSOCKET_URL

🔗 Analysis chain

Line range hint 21-25: Review environment file patterns.

The addition of multiple environment file patterns seems overly broad and unrelated to the calendar feature. Consider:

1. Using only necessary environment patterns
2. Documenting required environment variables in .env.example

Let's verify the environment setup:

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if .env.example exists and contains calendar-related vars
if [ -f ".env.example" ]; then
    echo "Checking .env.example for calendar-related variables:"
    rg -i 'calendar|event|holiday' .env.example
fi

Length of output: 188

---

Script:

#!/bin/bash
# Let's check for any environment variable usage in the codebase
echo "Searching for environment variable usage:"
rg "process\.env\." -A 2

echo -e "\nChecking for dotenv related setup:"
rg "require\(['\"]dotenv['\"]" -A 2
rg "import.*dotenv" -A 2

echo -e "\nChecking package.json for dotenv dependency:"
if [ -f "package.json" ]; then
    cat package.json | grep -A 5 -B 5 "dotenv"
fi

Length of output: 3110

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

10-18: Add TypeScript return type for better type safety.

The function should explicitly declare its return type for better type safety and code clarity.

-const containsSkipComment = (file) => {
+const containsSkipComment = (file: string): boolean => {

🧰 Tools

🪛 eslint

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

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

---

87-93: Fix template literal formatting.

Add missing commas in template literals as per the project's formatting guidelines.

   console.info(
     '\x1b[34m%s\x1b[0m',
-    '\nInfo: Consider using custom hook functions.'
+    '\nInfo: Consider using custom hook functions.',
   );
   console.info(
-    'Please use the getItem, setItem, and removeItem functions provided by the custom hook useLocalStorage.\n'
+    'Please use the getItem, setItem, and removeItem functions provided by the custom hook useLocalStorage.\n',
   );

🧰 Tools

🪛 eslint

[error] 89-89: Insert ,

(prettier/prettier)

---

[error] 92-92: Insert ,

(prettier/prettier)

---

1-96: Consider adding unit tests for the script.

While the script is well-structured, adding unit tests would help ensure its reliability, especially for:

• Different file patterns and content scenarios
• Command-line argument handling
• Skip comment detection
• Various localStorage usage patterns

Would you like me to help create a test suite for this script?

🧰 Tools

🪛 eslint

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

schema.graphql (1)

858-875: Correct formatting of the PageInfo type description

The PageInfo type description between lines 858-875 has inconsistent indentation and misplaced triple quotes, which might cause parsing issues.

Adjust the formatting to align descriptions properly:

-"""
 Information about pagination in a connection.
 """
 type PageInfo {
-  currPageNo: Int
-
-  """
-  When paginating forwards, are there more items?
-  """
-  hasNextPage: Boolean!
-
-  """
-  When paginating backwards, are there more items?
-  """
-  hasPreviousPage: Boolean!
-  nextPageNo: Int
-  prevPageNo: Int
-  totalPages: Int
-}
+"""
+Information about pagination in a connection.
+"""
+type PageInfo {
+  currPageNo: Int
+
+  """
+  When paginating forwards, are there more items?
+  """
+  hasNextPage: Boolean!
+
+  """
+  When paginating backwards, are there more items?
+  """
+  hasPreviousPage: Boolean!
+  nextPageNo: Int
+  prevPageNo: Int
+  totalPages: Int
+}

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 9b5bd3e and 9442bb2.

⛔ 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
• ISSUE_TEMPLATE.md
• Docker_Container/.dockerignore
• .github/workflows/ci.yml
• .github/workflows/linter.yml
• Docker_Container/dockerfile
• Docker_Container/docker-compose.yml
• Docker_Container/README.md
• public/index.html
• .github/workflows/codeql-analysis.yml
• PULL_REQUEST_TEMPLATE.md
• PR-guidelines.md
• .github/workflows/npm-publish.yml

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

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

👮 Files not reviewed due to content moderation or server errors (3)

• public/locales/zh/common.json
• public/locales/en/translation.json
• public/locales/fr/translation.json

🧰 Additional context used

🪛 LanguageTool

CODE_OF_CONDUCT.md

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

(ENGLISH_WORD_REPEAT_RULE)

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)

---

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

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)

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

INSTALLATION.md

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

(ENGLISH_WORD_REPEAT_RULE)

---

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

(DURING_THAT_TIME_COMMA)

---

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

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

(NOUN_VERB_CONFUSION)

---

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

(MAC_OS)

---

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

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

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

(MAC_OS)

---

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

(ENGLISH_WORD_REPEAT_RULE)

---

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

(MAC_OS)

---

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

(NOUN_VERB_CONFUSION)

---

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

(COMMA_COMPOUND_SENTENCE)

---

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

(NOUN_VERB_CONFUSION)

---

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

(NOUN_VERB_CONFUSION)

---

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

(MD_PRP_QUESTION_MARK)

---

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

(BY_DEFAULT_COMMA)

---

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

(PRP_MD_NN)

.github/workflows/README.md

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

(AI_HYDRA_LEO_MISSING_COMMA)

---

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

(ENGLISH_WORD_REPEAT_RULE)

---

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

(E_G)

DOCUMENTATION.md

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

(MD_BASEFORM)

---

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

(MARKDOWN_NNP)

---

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

(AI_EN_LECTOR_REPLACEMENT_PREPOSITION)

🪛 eslint

scripts/custom-test-env.js

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

(tsdoc/syntax)

---

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

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

---

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

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

scripts/githooks/update-toc.js

[error] 11-12: Delete ··⏎

(prettier/prettier)

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)

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

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)

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/bug-report.md

36-36: null
Bare URL used

(MD034, no-bare-urls)

---

33-33: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

.github/ISSUE_TEMPLATE/feature-request.md

28-28: null
Bare URL used

(MD034, no-bare-urls)

---

25-25: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

DOCUMENTATION.md

25-25: null
Bare URL used

(MD034, no-bare-urls)

🪛 actionlint (1.7.4)

.github/workflows/codeql-codescan.yml

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

(action)

---

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

(action)

---

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

(action)

.github/workflows/stale.yml

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

(action)

.github/workflows/issue.yml

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

(action)

.github/workflows/pull-request.yml

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

(expression)

---

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

(shellcheck)

---

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

(expression)

🪛 yamllint (1.35.1)

.github/workflows/codeql-codescan.yml

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 17-17: trailing spaces

(trailing-spaces)

---

[error] 20-20: trailing spaces

(trailing-spaces)

---

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

(indentation)

---

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

(indentation)

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

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 13-13: trailing spaces

(trailing-spaces)

---

[error] 15-15: trailing spaces

(trailing-spaces)

---

[error] 27-27: trailing spaces

(trailing-spaces)

---

[error] 28-28: trailing spaces

(trailing-spaces)

---

[error] 29-29: trailing spaces

(trailing-spaces)

---

[error] 31-31: trailing spaces

(trailing-spaces)

---

[error] 33-33: trailing spaces

(trailing-spaces)

---

[error] 34-34: trailing spaces

(trailing-spaces)

---

[error] 36-36: trailing spaces

(trailing-spaces)

---

[error] 41-41: trailing spaces

(trailing-spaces)

---

[error] 46-46: trailing spaces

(trailing-spaces)

---

[error] 71-71: trailing spaces

(trailing-spaces)

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

🪛 Ruff (0.8.0)

.github/workflows/eslint_disable_check.py

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

Rename unused dirs to _dirs

(B007)

.github/workflows/compare_translations.py

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

(B904)

🔇 Additional comments (14)

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

14-14: Review security implications of pull_request_target

The pull_request_target event runs workflows with repository secrets on PRs from forks. This could potentially expose sensitive information if not properly configured.

✅ Verification successful

Let me gather more information about the workflow configuration to better assess the security implications.

---

The pull_request_target usage is secure in this workflow

The current workflow configuration is safe because:

• It only uses GITHUB_TOKEN which has limited scope and is automatically rotated
• The workflow only performs non-sensitive operations:
  • Adding PR review policy comment using thollander/actions-comment-pull-request
  • Sending greeting message using actions/first-interaction
• No repository checkout is performed
• No code execution or access to sensitive secrets is present

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for potential security risks in workflow permissions
rg -l 'pull_request_target' .github/workflows/ | while read -r file; do
  echo "Analyzing $file for sensitive operations:"
  rg -A 5 'secrets\.|checkout|npm|pip|actions/setup' "$file"
done

Length of output: 798

---

Script:

#!/bin/bash
# Check the complete workflow configuration
cat .github/workflows/pull-request-target.yml

Length of output: 3641

.github/workflows/eslint_disable_check.py (1)

1-28: LGTM! Well-structured script header and imports.

The documentation clearly explains the script's purpose and compliance with Python coding standards.

package.json (1)

73-89: Verify script configurations

The scripts section includes new configurations for Vite and TypeScript. Ensure that:

1. The Vite config path is correct
2. The test environment setup is compatible with the new configuration
3. The setup script is properly documented

✅ Verification successful

All script configurations are properly set up and documented

The verification confirms that all required configuration files are present and properly configured:

• The Vite config at config/vite.config.ts is well-structured with correct plugins and server settings
• The custom test environment at scripts/custom-test-env.js properly extends Jest's JSDOM environment with required polyfills
• The setup script at setup.ts is comprehensive and well-documented, handling environment configuration, API endpoints, and development settings

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Verify the existence and content of config files
echo "Checking Vite config..."
cat config/vite.config.ts || echo "Vite config not found"
echo "Checking test environment setup..."
cat scripts/custom-test-env.js || echo "Test environment setup not found"
echo "Checking setup script..."
cat setup.ts || echo "Setup script not found"

Length of output: 7574

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

85-136: LGTM! Well-structured sensitive file checks.

The implementation provides comprehensive protection for sensitive files with appropriate conditional execution and clear error messaging.

🧰 Tools

🪛 yamllint (1.35.1)

[error] 92-92: trailing spaces

(trailing-spaces)

---

[error] 126-126: trailing spaces

(trailing-spaces)

---

[error] 129-129: trailing spaces

(trailing-spaces)

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

27-28: Format URL using proper markdown syntax

The bare URL should be formatted using proper markdown link syntax for better readability and consistency.

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

🧰 Tools

🪛 Markdownlint (0.35.0)

28-28: null
Bare URL used

(MD034, no-bare-urls)

---

25-26: Use proper markdown heading syntax

Convert the bold text to a proper markdown heading for better document structure.

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

🧰 Tools

🪛 Markdownlint (0.35.0)

25-25: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

.github/workflows/README.md (1)

1-47: Well-structured workflow guidelines document.

The document provides clear and comprehensive guidelines for managing GitHub workflows. The structure is logical, and the content effectively covers all necessary aspects of workflow management.

🧰 Tools

🪛 LanguageTool

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

(AI_HYDRA_LEO_MISSING_COMMA)

---

[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/stale.yml (1)

37-39: Review stale timeframes

The current configuration marks items as stale after 10 days and closes them after 180 days. Consider if these timeframes align with the team's development cycle, especially for calendar feature development.

✅ Verification successful

Current stale timeframes are well-configured

The stale configuration appears appropriate and well-thought-out for the following reasons:

• The 10-day stale marking serves as an initial reminder for attention, with clear messages for both issues and PRs
• The 180-day grace period before closing provides ample time for response
• Important safeguards are in place:
  • WIP items are exempt via exempt-pr-labels and exempt-issue-labels
  • All milestoned items are exempt via exempt-all-milestones
  • Stale status is removed upon updates via remove-stale-when-updated
  • Rate-limited to 30 operations per run to prevent overwhelming notifications

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check typical issue/PR resolution times to validate timeframes
gh api graphql -f query='
{
  repository(owner: "YourOrg", name: "YourRepo") {
    issues(last: 100, states: CLOSED) {
      nodes {
        closedAt
        createdAt
      }
    }
  }
}' | jq '.data.repository.issues.nodes[] | (.closedAt | fromdate) - (.createdAt | fromdate)'

Length of output: 410

---

Script:

#!/bin/bash
# Let's check the repository's activity patterns and stale configuration history
# First, check if there are other workflow files with stale configurations
fd -e yml -e yaml . .github/workflows/ --exec grep -l "days-before"

# Then look for any discussions or documentation about stale settings
fd -e md . -E node_modules --exec grep -l -i "stale"

# Finally, check the stale workflow file's history
git log -p -- .github/workflows/stale.yml | head -n 50

Length of output: 148

---

Script:

#!/bin/bash
# Let's examine the stale.yml file content to understand the full configuration context
cat .github/workflows/stale.yml

# Also check for any recent issues or PRs that might have been marked as stale
rg -l "stale" .github/ISSUE_TEMPLATE/ .github/PULL_REQUEST_TEMPLATE/ 2>/dev/null || true

Length of output: 2036

.github/workflows/issue.yml (3)

58-65: Update first-interaction action and verify documentation links

1. Consider updating to the latest version of the first-interaction action.
2. Let's verify that the referenced documentation links are valid.

-      - uses: actions/first-interaction@v1
+      - uses: actions/[email protected]

✅ Verification successful

Documentation links are valid, consider updating action version

Both CONTRIBUTING.md and ISSUE_GUIDELINES.md files exist in the repository, confirming that the welcome message links are valid. The suggestion to update actions/first-interaction to v1.3.0 would be a good improvement for maintenance.

• CONTRIBUTING.md ✓
• ISSUE_GUIDELINES.md ✓

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if the referenced documentation files exist
echo "Checking CONTRIBUTING.md..."
fd -t f "CONTRIBUTING.md"
echo "Checking ISSUE_GUIDELINES.md..."
fd -t f "ISSUE_GUIDELINES.md"

Length of output: 229

---

21-25: Verify the auto-label.json5 file exists

The workflow uses sparse checkout to fetch the auto-label configuration file. Let's verify its existence and structure.

✅ Verification successful

The auto-label.json5 file exists and is properly structured

The sparse-checkout configuration is correctly set up, and the auto-label.json5 file exists with a valid JSON5 structure containing label synonyms and default labels configuration.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if the auto-label.json5 file exists and is valid JSON5
fd -t f "auto-label.json5" .github/workflows

Length of output: 79

---

Script:

#!/bin/bash
# Let's check the content of the auto-label.json5 file to verify its structure
cat .github/workflows/auto-label.json5

Length of output: 262

---

1-11: Verify the referenced README.md file exists

The header comments reference a README.md file that defines what should be placed in this workflow file. Let's verify its existence and location.

✅ Verification successful

The referenced README.md exists and provides clear guidelines

The README.md file exists at the correct location (.github/workflows/README.md) and contains comprehensive guidelines for workflow files. The file specifically mentions that issue-related actions should be placed in the issues.yml file, which aligns with the current file's purpose.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for README.md files in the .github/workflows directory
fd -t f "README.md" .github/workflows

Length of output: 65

---

Script:

#!/bin/bash
# Let's check the content of the README.md to verify if it contains guidelines for the workflow file
cat .github/workflows/README.md

Length of output: 2105

🧰 Tools

🪛 yamllint (1.35.1)

[error] 6-6: trailing spaces

(trailing-spaces)

.gitignore (2)

13-14: Verify the coverage directory pattern change.

The pattern change from -/coverage to coverage/ and addition of codecov seems unrelated to the calendar feature. Please ensure this doesn't affect existing CI/CD pipelines.

Let's check the CI configuration:

✅ Verification successful

Let me check the content of these CI files to see how they use the coverage directory.

---

The coverage directory pattern change is safe and aligned with CI/CD usage

The change from -/coverage to coverage/ and addition of codecov in .gitignore is actually correct and matches how the CI pipeline uses these paths. The CI workflows generate coverage reports at ./coverage/lcov.info and use Codecov for coverage reporting, which justifies both ignore patterns. This change appears to be a cleanup to better match the actual usage in the CI pipeline.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if coverage is referenced in CI configs
rg -l 'coverage' .github/workflows/

Length of output: 97

---

Script:

#!/bin/bash
# Check how coverage is used in CI configs
rg -A 5 -B 5 'coverage' .github/workflows/pull-request.yml .github/workflows/push.yml

Length of output: 3827

---

31-32: Verify debug log configuration.

The addition of debug.log to the Express setup section seems unrelated to the calendar feature. Please confirm if this is part of the intended changes.

Let's check the debug log usage:

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

1-9: LGTM! Clean and effective script setup.

The script initialization with necessary imports and command-line argument handling is well-structured.

[coderabbitai]

⚠️ Potential issue

Fix file skipping logic in findTsxFiles

The use of path.relative(dir, filePath) may not correctly skip files in subdirectories because it includes the subdirectory path in the result. This can cause filenames like index.tsx in subdirectories to not be skipped as intended. Consider using path.basename(filePath) to compare just the filename, ensuring that files are skipped regardless of their directory.

Apply this diff to fix the comparison:

- !filesToSkip.includes(path.relative(dir, filePath))
+ !filesToSkip.includes(path.basename(filePath))

📝 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

	filePath.endsWith('.tsx') &&
	!filePath.endsWith('.test.tsx') &&
	!filesToSkip.includes(path.relative(dir, filePath))
	) {
	results.push(filePath);
	filePath.endsWith('.tsx') &&
	!filePath.endsWith('.test.tsx') &&
	!filesToSkip.includes(path.basename(filePath))
	) {
	results.push(filePath);

[coderabbitai]

🛠️ Refactor suggestion

Handle errors and use consistent file operations

In several places, fs.readFile is used with a callback, but the err parameter is not checked. If an error occurs while reading the .env file, the subsequent operations may cause exceptions. Additionally, mixing asynchronous fs.readFile with synchronous fs.writeFileSync can lead to inconsistent behavior.

Refactor to use synchronous methods consistently and handle errors properly. Apply this diff to fix the issue at one occurrence and replicate it for the others:

- fs.readFile('.env', 'utf8', (err, data) => {
-   const result = data.replace(`PORT=${port}`, `PORT=${customPort}`);
-   fs.writeFileSync('.env', result, 'utf8');
- });
+ try {
+   const data = fs.readFileSync('.env', 'utf8');
+   const result = data.replace(`PORT=${port}`, `PORT=${customPort}`);
+   fs.writeFileSync('.env', result, 'utf8');
+ } catch (err) {
+   console.error(`Error reading or writing .env file: ${err.message}`);
+   process.exit(1);
+ }

Repeat similar changes at lines 111-117, 153-159, and 174-177 to ensure consistent error handling and file operation methods throughout the script.

Also applies to: 111-117, 153-159, 174-177

[coderabbitai]

🛠️ Refactor suggestion

Use exception chaining with raise ... from e

When re-raising an exception inside an except block, it's recommended to use exception chaining to preserve the original traceback. This provides better context and helps in debugging.

Apply this diff to include the original exception:

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

📝 Committable suggestion

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

Suggested change

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

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)

[coderabbitai]

🛠️ Refactor suggestion

Enhance pre-commit hook reliability and consistency

Several improvements could make this pre-commit hook more robust:

1. The commented-out lint:fix command seems inconsistent with the active lint-staged command
2. Missing error handling could allow commits to proceed even if commands fail
3. Running all these commands on every commit might impact performance

Consider this improved implementation:

- npm run format:fix
- # npm run lint:fix
- npm run lint-staged
- npm run typecheck
- npm run update:toc
+ set -e  # Exit on error
+ echo "Running pre-commit checks..."
+ 
+ # Run lighter checks first
+ npm run lint-staged || exit 1
+ 
+ # Run heavier checks
+ npm run typecheck || exit 1
+ npm run update:toc || exit 1

📝 Committable suggestion

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

Suggested change

	npm run format:fix
	# npm run lint:fix
	npm run lint-staged
	npm run typecheck
	npm run update:toc
	git add .
	set -e # Exit on error
	echo "Running pre-commit checks..."
	# Run lighter checks first
	npm run lint-staged || exit 1
	# Run heavier checks
	npm run typecheck || exit 1
	npm run update:toc || exit 1
	git add .

[coderabbitai]

⚠️ Potential issue

Add error handling for file operations

The file reading operations should include error handling to gracefully handle cases where files are inaccessible or the directory cannot be read.

Consider this safer implementation:

- const markdownFiles = fs
-   .readdirSync('./')
-   .filter((file) => file.endsWith('.md'));
+ let markdownFiles = [];
+ try {
+   markdownFiles = fs
+     .readdirSync('./')
+     .filter((file) => file.endsWith('.md'));
+ } catch (error) {
+   console.error('Error reading directory:', error);
+   process.exit(1);
+ }

📝 Committable suggestion

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

Suggested change

	const markdownFiles = fs
	.readdirSync('./')
	.filter((file) => file.endsWith('.md'));
	let markdownFiles = [];
	try {
	markdownFiles = fs
	.readdirSync('./')
	.filter((file) => file.endsWith('.md'));
	} catch (error) {
	console.error('Error reading directory:', error);
	process.exit(1);
	}

[coderabbitai]

⚠️ Potential issue

Remove duplicate definition of EmploymentStatus enum

The enum EmploymentStatus is duplicated at lines 265-269 and lines 1242-1246, which is invalid.

Please remove one of the definitions. For example, delete the second one at lines 1242-1246:

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

Also applies to: 1242-1246

[coderabbitai]

⚠️ Potential issue

Remove duplicate definition of Gender enum

Gender enum is defined twice at lines 438-442 and lines 1248-1252.

Delete one of the duplicate definitions to prevent schema errors. Remove the second definition at lines 1248-1252:

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

Also applies to: 1248-1252

[coderabbitai]

⚠️ Potential issue

Remove duplicate definition of MaritalStatus enum

The enum MaritalStatus appears twice in the schema at lines 491-498 and lines 1254-1261.

To fix this, remove the duplicated enum. Delete the version at lines 1254-1261:

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

Also applies to: 1254-1261

[coderabbitai]

⚠️ Potential issue

Remove duplicate definition of AddressInput input type

The AddressInput type is defined twice, at lines 43-52 and lines 1212-1221, causing redundancy.

Eliminate one of the definitions to ensure schema validity. For example, remove the second one at lines 1212-1221:

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

Also applies to: 1212-1221

[coderabbitai]

⚠️ Potential issue

Remove duplicate definition of UserPhone type

The type UserPhone is declared twice at lines 1348-1352 and lines 1407-1411.

Remove the duplicate to prevent conflicts. Delete the second definition at lines 1407-1411:

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

Also applies to: 1407-1411

[palisadoes]

This PR has too many submitted files.

Please ensure the following:

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

Closing