Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve Code Coverage #3528

Open
wants to merge 1 commit into
base: develop-postgres
Choose a base branch
from

Conversation

SukhvirKooner
Copy link

@SukhvirKooner SukhvirKooner commented Feb 2, 2025

What kind of change does this PR introduce?
Adding Tests

Issue Number:

Fixes #3047

Snapshots/Videos:
Screenshot 2025-02-03 at 12 33 51 AM

If relevant, did you update the documentation?

Summary

  • This PR adds comprehensive unit tests for the YearlyEventCalender component to improve test coverage and ensure robust behavior.
  • The Test don't simulate user interactions that set selectedDate equal to the rendered date. That's why /* istanbul ignore next */ is added to line 229—to prevent unnecessary coverage drops for production-only behavior.
  • /* istanbul ignore next */ was removed from line 143 because The tests cover those lines

Does this PR introduce a breaking change?
No

Checklist

CodeRabbit AI Review

  • I have reviewed and addressed all critical issues flagged by CodeRabbit AI
  • I have implemented or provided justification for each non-critical suggestion
  • I have documented my reasoning in the PR comments where CodeRabbit AI suggestions were not implemented

Test Coverage

  • I have written tests for all new changes/features
  • I have verified that test coverage meets or exceeds 95%
  • I have run the test suite locally and all tests pass

Other information

Have you read the contributing guide?

Summary by CodeRabbit

  • Tests
    • Enhanced test coverage for the yearly calendar to ensure events display accurately based on user roles and various interaction scenarios.
  • Chores
    • Updated internal test configurations to improve quality assurance and reliability of event filtering and calendar rendering.

Copy link
Contributor

coderabbitai bot commented Feb 2, 2025

Walkthrough

This pull request adds a comprehensive test suite for the YearlyEventCalender component. It introduces two new utility functions—filterData to filter event data based on user roles and organizational membership, and renderWithRouter to provide routing context in tests. In addition, it modifies the component code to include /* istanbul ignore next */ comments in specific conditions within rendering and filtering logic. The changes enhance automated testing for various edge cases without altering core functionality.

Changes

File Change Summary
src/components/EventCalendar/YearlyEventCalender.spec.tsx Added a comprehensive test suite, including tests for event filtering based on user roles (USER, ADMIN, SUPERADMIN), creation of filterData for event permission logic, and a renderWithRouter helper for routing context.
src/components/EventCalendar/YearlyEventCalender.tsx Inserted /* istanbul ignore next */ comments in the renderMonthDays function and within the filtering logic, and adjusted control flow formatting without modifying functionality.

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant C as YearlyEventCalender
    participant F as filterData
    participant R as Router Context

    U->>C: Render component with event data & user role
    C->>F: Invoke filtering logic based on role and organization
    F-->>C: Return filtered event list
    C->>R: Wrap component in router context
    C->>U: Display calendar with filtered events
Loading

Assessment against linked issues

Objective Addressed Explanation
Improve Code Coverage in src/components/EventCalender/YearlyEventCalender.tsx (#3047) Istanbul ignore comments remain, preventing full test coverage.

Possibly related issues

Possibly related PRs

Suggested reviewers

  • palisadoes

Poem

I'm a rabbit hopping through lines of code,
Skipping bugs on my merry little road.
Filtering events with a twitch of my ear,
Testing each case, making imperfections clear.
With a hop and a skip, the changes unfold—
A joyful rabbit tale in syntax told!
🐰💻


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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

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

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

CodeRabbit Commands (Invoked using PR comments)

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

Other keywords and placeholders

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

Documentation and Community

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

Copy link

github-actions bot commented Feb 2, 2025

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

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🔭 Outside diff range comments (1)
src/components/EventCalendar/YearlyEventCalender.tsx (1)

229-233: Critical: Remove the coverage ignore and add tests for date selection

The /* istanbul ignore next */ in src/components/EventCalendar/YearlyEventCalender.tsx is bypassing tests for core functionality, which is contributing to pipeline failures. Instead of ignoring this logic, please remove the disable statement and add tests to cover the date comparison functionality. Also, review similar instances across the codebase to ensure their behavior is properly tested.

🔗 Analysis chain

Remove code coverage disable statement and add tests.

The /* istanbul ignore next */ comment is causing pipeline failures. Instead of ignoring the code coverage:

  1. Remove the coverage disable statement
  2. Add tests for the date selection functionality

Run the following script to check for similar coverage disable statements:

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for istanbul ignore comments in the codebase
rg -l "istanbul ignore" .

Length of output: 1122

🧰 Tools
🪛 GitHub Actions: PR Workflow

[error] File contains code coverage disable statement. Please remove it and add the appropriate tests.

🧹 Nitpick comments (6)
src/components/EventCalendar/YearlyEventCalender.spec.tsx (4)

15-66: Consider replacing any with proper TypeScript types.

The function logic is correct, but it uses any type which reduces type safety. Consider defining proper interfaces for the event data and using them instead.

Apply this diff to improve type safety:

-  eventData: any[],
+  eventData: InterfaceEventListCardProps[],
🧰 Tools
🪛 ESLint

[error] 16-16: Unexpected any. Specify a different type.

(@typescript-eslint/no-explicit-any)


[error] 20-20: Unexpected any. Specify a different type.

(@typescript-eslint/no-explicit-any)


[error] 20-21: Delete

(prettier/prettier)


[error] 24-24: Unexpected any. Specify a different type.

(@typescript-eslint/no-explicit-any)


[error] 28-30: Replace ⏎······(admin)·=>·admin._id·===·userId⏎···· with (admin)·=>·admin._id·===·userId

(prettier/prettier)


[error] 42-42: Delete ·

(prettier/prettier)


[error] 50-50: Delete ······

(prettier/prettier)


[error] 53-53: Replace any)·=>·attendee._id·===·userId with ·any)·=>·attendee._id·===·userId,

(prettier/prettier)


[error] 53-53: Unexpected any. Specify a different type.

(@typescript-eslint/no-explicit-any)


[error] 55-55: Delete ······

(prettier/prettier)


[error] 63-63: Replace e with (e)

(prettier/prettier)


[error] 64-64: Replace (id·=>·filteredEvents.find(e with ((id)·=>·filteredEvents.find((e)

(prettier/prettier)

🪛 GitHub Actions: PR Workflow

[warning] Code style issues found. Run Prettier with --write to fix.


68-76: Add return type annotation for better type safety.

The function is missing a return type annotation which would improve type safety and documentation.

Apply this diff to add the return type:

-const renderWithRouter = (ui: React.ReactElement) => {
+const renderWithRouter = (ui: React.ReactElement): RenderResult => {
🧰 Tools
🪛 ESLint

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

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


[error] 71-73: Replace ⏎········{ui}⏎······ with {ui}

(prettier/prettier)


[error] 74-74: Insert ,

(prettier/prettier)

🪛 GitHub Actions: PR Workflow

[warning] Code style issues found. Run Prettier with --write to fix.


136-166: Consider extracting common test setup into helper functions.

The test cases for filtering private events and handling admin roles have duplicated setup code. Consider extracting the common setup into helper functions to improve maintainability.

Example helper function:

const createMockEvent = (isPublic: boolean, attendees: string[] = []): Partial<InterfaceEventListCardProps> => ({
  ...mockEventData[0],
  isPublic,
  attendees: attendees.map(id => ({ _id: id })),
  startDate: new Date().toISOString(),
  endDate: new Date().toISOString()
});

Also applies to: 375-395

🧰 Tools
🪛 ESLint

[error] 140-140: Insert ,

(prettier/prettier)


[error] 142-142: Delete ··

(prettier/prettier)


[error] 148-148: Delete ·

(prettier/prettier)


[error] 150-150: Insert ,

(prettier/prettier)


[error] 152-152: Delete ··

(prettier/prettier)


[error] 156-156: Delete ····

(prettier/prettier)


[error] 160-160: Forbidden non-null assertion.

(@typescript-eslint/no-non-null-assertion)


[error] 162-162: Delete ····

(prettier/prettier)

🪛 GitHub Actions: PR Workflow

[warning] Code style issues found. Run Prettier with --write to fix.


220-233: Enhance test assertions with more descriptive messages.

The assertions could be more descriptive to better explain what's being tested and why the test might fail.

Apply this diff to improve the assertions:

-expect(todayCell.length).toBeGreaterThan(0);
+expect(todayCell.length).toBeGreaterThan(0, 'Calendar should render at least one day cell');

Also applies to: 252-254

🧰 Tools
🪛 ESLint

[error] 222-222: Delete ·

(prettier/prettier)


[error] 228-228: Insert ,

(prettier/prettier)

🪛 GitHub Actions: PR Workflow

[warning] Code style issues found. Run Prettier with --write to fix.

src/components/EventCalendar/YearlyEventCalender.tsx (2)

134-168: Consider moving filterData to a separate utility file.

The filterData function is a pure utility function that could be reused across components. Consider moving it to a separate file under utils/ directory.

Example structure:

// utils/eventFilters.ts
export const filterEventsByRole = (
  eventData: InterfaceEventListCardProps[],
  orgData?: InterfaceIOrgList,
  userRole?: string,
  userId?: string,
): InterfaceEventListCardProps[] => {
  // ... existing implementation
};
🧰 Tools
🪛 GitHub Actions: PR Workflow

[error] File contains code coverage disable statement. Please remove it and add the appropriate tests.


223-274: Simplify nested logic in renderMonthDays.

The event rendering logic has deep nesting which makes it harder to understand and maintain. Consider extracting the event rendering logic into separate functions.

Example refactor:

const getDateClassName = (date: Date, monthInx: number): string => {
  return [
    date.toLocaleDateString() === today.toLocaleDateString() ? styles.day__today : '',
    date.getMonth() !== monthInx ? styles.day__outside : '',
    selectedDate?.getTime() === date.getTime() ? styles.day__selected : '',
    styles.day__yearly,
  ].join(' ');
};

const renderEvent = (event: InterfaceEventListCardProps) => {
  const attendees = event.attendees?.map(attendee => ({ _id: attendee._id })) || [];
  return (
    <EventListCard
      {...event}
      refetchEvents={refetchEvents}
      userRole={userRole}
      registrants={attendees}
    />
  );
};
🧰 Tools
🪛 GitHub Actions: PR Workflow

[error] File contains code coverage disable statement. Please remove it and add the appropriate tests.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1183dfc and c9396ce.

📒 Files selected for processing (2)
  • src/components/EventCalendar/YearlyEventCalender.spec.tsx (1 hunks)
  • src/components/EventCalendar/YearlyEventCalender.tsx (2 hunks)
🧰 Additional context used
🪛 ESLint
src/components/EventCalendar/YearlyEventCalender.spec.tsx

[error] 2-2: Replace ·render,·fireEvent,·act,·screen,·waitFor,·within· with ⏎··render,⏎··fireEvent,⏎··act,⏎··screen,⏎··waitFor,⏎··within,⏎

(prettier/prettier)


[error] 2-2: 'within' is defined but never used.

(@typescript-eslint/no-unused-vars)


[error] 16-16: Unexpected any. Specify a different type.

(@typescript-eslint/no-explicit-any)


[error] 20-20: Unexpected any. Specify a different type.

(@typescript-eslint/no-explicit-any)


[error] 20-21: Delete

(prettier/prettier)


[error] 24-24: Unexpected any. Specify a different type.

(@typescript-eslint/no-explicit-any)


[error] 28-30: Replace ⏎······(admin)·=>·admin._id·===·userId⏎···· with (admin)·=>·admin._id·===·userId

(prettier/prettier)


[error] 42-42: Delete ·

(prettier/prettier)


[error] 50-50: Delete ······

(prettier/prettier)


[error] 53-53: Replace any)·=>·attendee._id·===·userId with ·any)·=>·attendee._id·===·userId,

(prettier/prettier)


[error] 53-53: Unexpected any. Specify a different type.

(@typescript-eslint/no-explicit-any)


[error] 55-55: Delete ······

(prettier/prettier)


[error] 63-63: Replace e with (e)

(prettier/prettier)


[error] 64-64: Replace (id·=>·filteredEvents.find(e with ((id)·=>·filteredEvents.find((e)

(prettier/prettier)


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

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


[error] 71-73: Replace ⏎········{ui}⏎······ with {ui}

(prettier/prettier)


[error] 74-74: Insert ,

(prettier/prettier)


[error] 81-81: Delete ··

(prettier/prettier)


[error] 102-102: Insert ,

(prettier/prettier)


[error] 103-103: Insert ,

(prettier/prettier)


[error] 124-124: Insert ,

(prettier/prettier)


[error] 125-125: Insert ,

(prettier/prettier)


[error] 126-126: Insert ,

(prettier/prettier)


[error] 130-130: Insert ,

(prettier/prettier)


[error] 140-140: Insert ,

(prettier/prettier)


[error] 142-142: Delete ··

(prettier/prettier)


[error] 148-148: Delete ·

(prettier/prettier)


[error] 150-150: Insert ,

(prettier/prettier)


[error] 152-152: Delete ··

(prettier/prettier)


[error] 156-156: Delete ····

(prettier/prettier)


[error] 160-160: Forbidden non-null assertion.

(@typescript-eslint/no-non-null-assertion)


[error] 162-162: Delete ····

(prettier/prettier)


[error] 167-167: Delete ··

(prettier/prettier)


[error] 170-173: Replace ⏎········eventData={mockEventData}⏎········refetchEvents={mockRefetchEvents}⏎······/> with eventData={mockEventData}·refetchEvents={mockRefetchEvents}·/>,

(prettier/prettier)


[error] 177-177: Replace getByText(new·Date().getFullYear().toString()) with ⏎········getByText(new·Date().getFullYear().toString()),⏎······

(prettier/prettier)


[error] 179-179: Delete ····

(prettier/prettier)


[error] 183-183: Replace '._calendar__weekdays_658d08' with ⏎······'._calendar__weekdays_658d08',⏎····

(prettier/prettier)


[error] 186-186: Replace header with (header)

(prettier/prettier)


[error] 197-200: Replace ⏎········eventData={mockEventData}⏎········refetchEvents={mockRefetchEvents}⏎······/> with eventData={mockEventData}·refetchEvents={mockRefetchEvents}·/>,

(prettier/prettier)


[error] 222-222: Delete ·

(prettier/prettier)


[error] 228-228: Insert ,

(prettier/prettier)


[error] 240-240: Insert ,

(prettier/prettier)


[error] 243-243: Delete ·

(prettier/prettier)


[error] 249-249: Insert ,

(prettier/prettier)


[error] 261-261: Insert ,

(prettier/prettier)


[error] 265-265: Delete ·

(prettier/prettier)


[error] 271-271: Insert ,

(prettier/prettier)


[error] 283-283: Insert ,

(prettier/prettier)


[error] 287-290: Replace ⏎········eventData={[mockEvent]}⏎········refetchEvents={mockRefetchEvents}⏎······/> with eventData={[mockEvent]}·refetchEvents={mockRefetchEvents}·/>,

(prettier/prettier)


[error] 299-299: Forbidden non-null assertion.

(@typescript-eslint/no-non-null-assertion)


[error] 303-303: Replace '._expand_event_list_658d08' with ⏎········'._expand_event_list_658d08',⏎······

(prettier/prettier)


[error] 310-313: Replace ⏎········eventData={[]}⏎········refetchEvents={mockRefetchEvents}⏎······/> with eventData={[]}·refetchEvents={mockRefetchEvents}·/>,

(prettier/prettier)


[error] 330-330: Insert ,

(prettier/prettier)


[error] 332-332: Delete ··

(prettier/prettier)


[error] 334-337: Replace ⏎········eventData={[mockEvent]}⏎········refetchEvents={mockRefetchEvents}⏎······/> with eventData={[mockEvent]}·refetchEvents={mockRefetchEvents}·/>,

(prettier/prettier)


[error] 339-339: Delete ··

(prettier/prettier)


[error] 341-341: Delete ··

(prettier/prettier)


[error] 347-347: Insert ,

(prettier/prettier)


[error] 348-348: Insert ,

(prettier/prettier)


[error] 350-350: Delete ··

(prettier/prettier)


[error] 354-354: Delete ·

(prettier/prettier)


[error] 359-359: Insert ,

(prettier/prettier)


[error] 360-360: Delete ··

(prettier/prettier)


[error] 361-361: Delete ··

(prettier/prettier)


[error] 363-363: Delete ····

(prettier/prettier)


[error] 366-366: Delete ······

(prettier/prettier)


[error] 380-380: Insert ,

(prettier/prettier)


[error] 384-384: Delete ·

(prettier/prettier)


[error] 390-390: Insert ,

(prettier/prettier)


[error] 402-402: Insert ,

(prettier/prettier)


[error] 403-403: Insert ,

(prettier/prettier)


[error] 407-407: Delete ·

(prettier/prettier)


[error] 410-410: Insert ,

(prettier/prettier)


[error] 414-414: Delete ····

(prettier/prettier)


[error] 421-421: Replace '._expand_event_list_658d08' with ⏎······'._expand_event_list_658d08',⏎····

(prettier/prettier)


[error] 427-430: Replace ⏎········eventData={mockEventData}⏎········refetchEvents={mockRefetchEvents}⏎······/> with eventData={mockEventData}·refetchEvents={mockRefetchEvents}·/>,

(prettier/prettier)


[error] 446-451: Replace ⏎······<Calendar·⏎········eventData={[]}⏎········refetchEvents={mockRefetchEvents}⏎······/>⏎···· with <Calendar·eventData={[]}·refetchEvents={mockRefetchEvents}·/>

(prettier/prettier)


[error] 455-455: Delete ··

(prettier/prettier)


[error] 470-470: Insert ,

(prettier/prettier)


[error] 475-478: Replace ⏎········{·_id:·'user1'·},⏎········{·_id:·'user2'·}⏎······ with {·_id:·'user1'·},·{·_id:·'user2'·}

(prettier/prettier)


[error] 482-482: Insert ,

(prettier/prettier)


[error] 483-483: Insert ,

(prettier/prettier)


[error] 487-487: Delete ·

(prettier/prettier)


[error] 492-492: Insert ,

(prettier/prettier)


[error] 496-496: Delete ····

(prettier/prettier)


[error] 508-509: Delete

(prettier/prettier)


[error] 513-513: Insert ,

(prettier/prettier)


[error] 517-520: Replace ⏎········eventData={[mockEvent]}⏎········refetchEvents={mockRefetchEvents}⏎······/> with eventData={[mockEvent]}·refetchEvents={mockRefetchEvents}·/>,

(prettier/prettier)


[error] 529-529: Forbidden non-null assertion.

(@typescript-eslint/no-non-null-assertion)


[error] 532-532: Replace '._expand_event_list_658d08' with ⏎········'._expand_event_list_658d08',⏎······

(prettier/prettier)


[error] 538-538: Forbidden non-null assertion.

(@typescript-eslint/no-non-null-assertion)


[error] 544-545: Delete

(prettier/prettier)


[error] 559-559: Delete ·

(prettier/prettier)


[error] 562-562: Insert ,

(prettier/prettier)


[error] 569-569: Forbidden non-null assertion.

(@typescript-eslint/no-non-null-assertion)


[error] 581-581: Insert ,

(prettier/prettier)


[error] 586-586: Insert ,

(prettier/prettier)


[error] 591-591: Insert ,

(prettier/prettier)


[error] 592-592: Insert ,

(prettier/prettier)


[error] 602-602: Replace events with ⏎······events,⏎····

(prettier/prettier)


[error] 613-613: Insert ,

(prettier/prettier)


[error] 616-616: Replace e with (e)

(prettier/prettier)


[error] 626-626: Insert ,

(prettier/prettier)


[error] 630-631: Delete

(prettier/prettier)


[error] 634-634: Replace e with (e)

(prettier/prettier)


[error] 635-635: Replace id with (id)

(prettier/prettier)


[error] 636-636: Replace id with (id)

(prettier/prettier)


[error] 642-643: Replace ⏎····const·modifiedEvents·=·events.map(e with ····const·modifiedEvents·=·events.map((e)

(prettier/prettier)


[error] 650-650: Replace e with (e)

(prettier/prettier)

src/components/EventCalendar/YearlyEventCalender.tsx

[error] 220-220: Insert ;

(prettier/prettier)

🪛 GitHub Actions: PR Workflow
src/components/EventCalendar/YearlyEventCalender.spec.tsx

[warning] Code style issues found. Run Prettier with --write to fix.

src/components/EventCalendar/YearlyEventCalender.tsx

[error] File contains code coverage disable statement. Please remove it and add the appropriate tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant