Fix report abuse

[CasperL1218]

Summary

This pull request enhanced the Report Abuse feature for reviews. The new Report Abuse feature provides a more comprehensive process for reporting reviews, and allowing admin to monitor reported reviews to take actions.

Main Requirements Completed:

• Added confirmation modal for reporting
• Added success toast for report submission
• Kept reported reviews visible on apartment page
• Admin section exists for handling reported reviews

Backend Changes Completed:

• Added report functionality to endpoints
• Added report fields to review type
  • Include date, reason, and userId
  • reason field will require future frontend process
• Implemented proper status handling
  • Create REPORTED review status
  • Implemented new report entry creation
• Added validation for report submissions
  • Relevant authorization and identity check for report functionality (admin, review owner, etc.)

Frontend Changes Completed:

• Report process
  • Added report confirmation modal
  • Added report abuse success toast
• Page display
  • Modified review fetching to include reported reviews (so users can see both APPROVED and REPORTED reviews)
  • Updated ApartmentPage, AdminPage, ProfilePage, LandlordPage, and BookmarkPage
• Review owner page (ProfilePage)
  • Prevent reported review owner to edit reviews
  • Prevent review owner to report their own reviews
  • Added reported reviews section to profile page
• Admin Page
  • Reported review section
  • Review dropdown UI enhancement

Review Status Flow Fixed:

• PENDING → APPROVED → can be REPORTED
• Can't report PENDING reviews
• Can't report own reviews
• Reported reviews remain visible to all users

Edge Cases Handled:

• Users can't report their own reviews
• Users can't report pending reviews
• Reported reviews stay visible but can't be edited
• Profile page shows all review statuses correctly

Test Plan

*Reported reviews in profile page: 1. Reported reviews can't be edited/deleted. 2. Can't report self's reviews.

*Only able to report other users' review. REPORTED reviews are still visible.

*Admin page reported review display

*Admin page review section dropdown menu

Test the following flows:

1. Regular user flow:

   • View an approved review
   • Click report abuse button
   • Confirm report in modal
   • See success toast
   • Verify review remains visible

2. Edge cases:

   • Verify can't report own reviews (report button hidden)
   • Verify can't report pending reviews (pending reviews are only available in owner's profile page, where report button is hidden)
   • Verify reported reviews can't be edited
   • Verify reported reviews show up in profile page

Notes

• Using lazy migration for the reports field in review documents
• Reported reviews remain visible to prevent abuse of the report system
• Only admins can take action on reported reviews

Breaking Changes

• Database schema change: Added reports array field to review documents (lazy migration)

Future Plans

• Receive feedbacks
• Implement report-reason functionality

[dti-github-bot]

[diff-counting] Significant lines: 351.

[kea-roy]

PR Review

You implemented the report abuse confirmation modal really well with no flaws, and the toast works correctly as expected. Good work on these parts.

You also adjusted the app.ts really well, I love the security checks and the logic works correctly.

I like the addition of the collapsing arrows and it really helps improve the user experience! One minor change would be to switch the open and close state direction to match the convention across our site, so just flip the rotate CSS.

This is the current state, but it should be the opposite.