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

fix: deleted posts still visible after removal (#3602) #3695

Open
wants to merge 8 commits into
base: develop-postgres
Choose a base branch
from

Conversation

AryanSwaroop
Copy link

@AryanSwaroop AryanSwaroop commented Feb 17, 2025

What kind of change does this PR introduce?

Ensures Deleted Posts Are No Longer Visible in posts section of user portal.

Issue Number:

#3602

Snapshots/Videos:

Video_250215115245.mp4

If relevant, did you update the documentation?

No

Summary

A issue like this can cause confusion for any individual using talawa services as if post is not deleted then they might delete some other post in confusion.

Does this PR introduce a breaking change?

There is not any breaking change just a simple awaiting till data is updated.

Checklist

CodeRabbit AI Review

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

Test Coverage

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

Other information

Have you read the contributing guide?

Yes

Summary by CodeRabbit

  • Bug Fixes
    • Refined the post deletion workflow to wait for confirmation of successful removal before refreshing the post list and displaying success notifications. This ensures that any delays or errors are handled gracefully, providing clear, immediate feedback and a smoother, more confident experience when managing your posts.

Copy link
Contributor

coderabbitai bot commented Feb 17, 2025

Walkthrough

This pull request updates the asynchronous post deletion functionality in the UserPortal. The handleDeletePost function in the PostCard component now returns a Promise<void> and awaits the deletion process before proceeding. In addition, the post deletion tests have been enhanced to use a mock function for fetching posts and waitFor to reliably check that UI updates (dropdown, delete button, and success toast) occur as expected.

Changes

File Change Summary
src/components/.../PostCard.tsx Updated handleDeletePost to be asynchronous by returning Promise<void>, awaiting deletePost, conditionally calling fetchPosts when event data exists, and displaying a success toast.
src/components/.../PostCard.spec.tsx Enhanced tests by introducing fetchPostsMock and replacing generic wait calls with waitFor to ensure UI elements (dropdown, delete button, and success toast) are properly verified after deletion.

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant PC as PostCard Component
    participant D as deletePost Service
    participant T as Toast Service

    U->>PC: Clicks delete action
    PC->>D: await deletePost()
    D-->>PC: Returns event data
    PC->>PC: Check if event data exists
    alt Event data present
        PC->>PC: Call fetchPosts()
        PC->>T: Display success toast
    else No event data
        PC-->>PC: End process
    end
Loading

Possibly related PRs

Suggested reviewers

  • palisadoes

Poem

I'm a bunny coder, hopping through the code,
Async deletion makes my little heart explode.
Posts vanish with a skip and an await so neat,
Toasts and tests now cheer as all cases meet.
Leaping forward in style with every line I tote!
Happy trails and carrots in every commit note!


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between eead194 and 43123dd.

📒 Files selected for processing (1)
  • src/components/UserPortal/PostCard/PostCard.spec.tsx (3 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/components/UserPortal/PostCard/PostCard.spec.tsx
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Test Application

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

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[bot]
coderabbitai bot previously approved these changes Feb 17, 2025
@Cioppolo14
Copy link
Contributor

@AryanSwaroop Please fix the failed tests.

@AryanSwaroop
Copy link
Author

@Cioppolo14 that test failure is not related to this issue ! I can solve it, by raising another, @palisadoes merged my PR yesterday.
This error is for src/screens/UserPortal/Volunteer/Actions/Actions.spec.tsx failing !

@palisadoes
Copy link
Contributor

Please fix the test in this PR

@AryanSwaroop
Copy link
Author

On it then!

Copy link

codecov bot commented Feb 21, 2025

Codecov Report

Attention: Patch coverage is 80.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 86.08%. Comparing base (b83973a) to head (87c0c3c).

Files with missing lines Patch % Lines
src/components/UserPortal/PostCard/PostCard.tsx 80.00% 0 Missing and 1 partial ⚠️
Additional details and impacted files
@@                Coverage Diff                @@
##           develop-postgres    #3695   +/-   ##
=================================================
  Coverage             86.08%   86.08%           
=================================================
  Files                   371      371           
  Lines                  9138     9139    +1     
  Branches               1925     1926    +1     
=================================================
+ Hits                   7866     7867    +1     
  Misses                  906      906           
  Partials                366      366           

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

coderabbitai[bot]
coderabbitai bot previously approved these changes Feb 21, 2025
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.

3 participants