Skip to content

Conversation

@OpsEclipse
Copy link
Collaborator

Notion ticket link

Implement Report Conflict Feature

Implementation description

  • Added a reusable Dialogue template built on MUI Dialog (components/common/Dialogue.tsx)
  • Implemented the 2-dialog report conflict flow (confirm + success) in the review info stage (components/review/stages/reviewInfoStage.tsx)
  • Added reportReviewConflict GraphQL mutation in graphql/queries.ts
  • Added ReviewPageAPIClient to call the mutation (APIClients/ReviewPageAPIClient.ts)
  • Wired “Yes, report” to execute the mutation and show success/error UI

Steps to test

  1. nvm use 18
  2. npm run lint:tsc
  3. npm run build
  4. Navigate to /review?reviewId=<id>
  5. Click Conflict and verify the confirm dialog opens
  6. Click Cancel and verify it closes
  7. Click Yes, report and verify the mutation is called and the success dialog opens

What should reviewers focus on?

  • Dialogue template styling vs Figma
  • Modal state transitions (disabled while reporting, success dialog, error copy)
  • GraphQL variable types / reviewerId extraction

Pin Node version to match supported builds
Improve error reporting and validate response shape
Create a shared modal wrapper based on MUI Dialog
Add reportReviewConflict mutation and client wrapper
Show confirm and success dialogs and call the report mutation
Relocate ProtectedApplication into components and update imports
Tighten types and routing for review tables and stages
@mxc-maggiechen mxc-maggiechen changed the title Sparsh/intf26 conflict dialog [INTW26] Conflict Dialog Feb 10, 2026
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