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

[organization] updated organization screen #2085

Conversation

Alfredoeb9
Copy link

@Alfredoeb9 Alfredoeb9 commented Jul 12, 2024

What kind of change does this PR introduce?

bugFix, and Unit Test

Issue Number:

Fixes #2058

Did you add tests for your changes?

Yes

Summary

Filtered out events from action items and created unit test to verify only action items are being displayed.

Other information

Have you read the contributing guide?

Yes

Summary by CodeRabbit

  • New Features

    • Introduced detailed action items with information such as assignee, category, notes, dates, completion status, assigner, and creator.
  • Bug Fixes

    • Updated action items display logic to show only items without associated events.
  • Tests

    • Added a test case to ensure proper display of action items, checking for the presence of a specific item.

filtered out events from action items and created unit test to verify only action items are being displayed
Copy link

coderabbitai bot commented Jul 12, 2024

Walkthrough

The changes filter out event-specific action items from the organization-wide action items screen. A new mock action item is added, and a test case ensures only organization action items are displayed.

Changes

File Path Change Summary
src/screens/OrganizationActionItems/OrganizationActionItemMocks.ts Added a new action item with detailed information.
src/screens/OrganizationActionItems/OrganizationActionItems.test.tsx Added a test case to ensure only action items without associated events are displayed.
src/screens/OrganizationActionItems/OrganizationActionItems.tsx Modified the organizationActionItems function to filter action items and pass filtered data to the container.

Assessment against linked issues

Objective (Issue #2058) Addressed Explanation
Event Action Items are Displayed on the Organization Action Item Screen
Event specific action items must not be visible in the Organization (non-event) action items screen
Write tests to verify this behavior

Poem

In the code where tasks align,
Organization's list now refined.
Events no longer crowd the scene,
For clarity, screens kept clean.
Tests ensure all stays true,
A better world for me and you. 🌟🐇


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>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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

CodeRabbit Commands (invoked as PR comments)

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

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

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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

Our Pull Request Approval Process

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

Testing Your Code

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

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

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

Reviewers

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

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

Reviewing Your Code

Your reviewer(s) will have the following roles:

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

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

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

Other

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

Copy link

@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

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 836b534 and 14bda33.

Files selected for processing (3)
  • src/screens/OrganizationActionItems/OrganizationActionItemMocks.ts (1 hunks)
  • src/screens/OrganizationActionItems/OrganizationActionItems.test.tsx (1 hunks)
  • src/screens/OrganizationActionItems/OrganizationActionItems.tsx (2 hunks)
Additional context used
Learnings (2)
Common learnings
Learnt from: Chaitanya1672
PR: PalisadoesFoundation/talawa-admin#2049
File: src/screens/OrganizationActionItems/ActionItemUpdateModal.tsx:112-138
Timestamp: 2024-07-03T07:40:16.065Z
Learning: The `istanbul ignore next` comments in the `ActionItemUpdateModal.tsx` file were added as part of a commit that introduced tests for the `ActionItemUpdateModal` component. Removing these comments and writing tests to cover the previously ignored lines is recommended to ensure code integrity and improve test coverage.
src/screens/OrganizationActionItems/OrganizationActionItems.test.tsx (1)
Learnt from: Chaitanya1672
PR: PalisadoesFoundation/talawa-admin#2049
File: src/screens/OrganizationActionItems/ActionItemUpdateModal.tsx:112-138
Timestamp: 2024-07-03T07:40:16.065Z
Learning: The `istanbul ignore next` comments in the `ActionItemUpdateModal.tsx` file were added as part of a commit that introduced tests for the `ActionItemUpdateModal` component. Removing these comments and writing tests to cover the previously ignored lines is recommended to ensure code integrity and improve test coverage.
Additional comments not posted (4)
src/screens/OrganizationActionItems/OrganizationActionItemMocks.ts (1)

99-127: New action item added to mock data.

The new action item is consistent with the existing structure and aligns with the PR objectives to filter out event action items.

src/screens/OrganizationActionItems/OrganizationActionItems.tsx (2)

200-202: New filter logic added to exclude event action items.

The new filter logic correctly excludes action items associated with events by checking if item.event is null.


372-372: Updated prop passed to ActionItemsContainer.

The updated prop actionItemsData now uses the filtered action items, ensuring only non-event action items are passed.

src/screens/OrganizationActionItems/OrganizationActionItems.test.tsx (1)

598-618: New test case added to verify that only organization action items are displayed.

The new test case checks for the presence of an action item named "John Doe", which is part of the mock data with event set to null. This aligns with the PR objectives.

Copy link

This pull request did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please verify it has no conflicts with the develop branch and rebase if needed. Mention it now if you need help or give permission to other people to finish your work.

@github-actions github-actions bot added the no-pr-activity No pull request activity label Jul 23, 2024
Copy link

codecov bot commented Jul 25, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.92%. Comparing base (836b534) to head (14bda33).
Report is 10 commits behind head on develop.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #2085   +/-   ##
========================================
  Coverage    97.91%   97.92%           
========================================
  Files          231      231           
  Lines         6201     6203    +2     
  Branches      1790     1790           
========================================
+ Hits          6072     6074    +2     
  Misses         118      118           
  Partials        11       11           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@palisadoes palisadoes merged commit a1d5361 into PalisadoesFoundation:develop Jul 25, 2024
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-pr-activity No pull request activity
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants