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(j-s): Display confirmation modal before completing case #17112

Merged
merged 4 commits into from
Dec 5, 2024

Conversation

unakb
Copy link
Member

@unakb unakb commented Dec 3, 2024

Samþykktar módall til að ljúka máli

What

Display confirmation modal before judge completes an indictment case

Why

So they have time to change their mind if they realize they forgot something

Checklist:

  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • Formatting passes locally with my changes
  • I have rebased against main before asking for a review

Summary by CodeRabbit

  • New Features

    • Introduced a confirmation modal for case completion, enhancing user interaction.
    • Updated modal titles and button texts for clarity and usability.
  • Bug Fixes

    • Improved the flow of case transition by modifying button click handling, ensuring a smoother user experience.
  • Documentation

    • Updated strings for internationalization to reflect the new modal functionality.

@unakb unakb requested a review from a team as a code owner December 3, 2024 13:42
Copy link
Contributor

coderabbitai bot commented Dec 3, 2024

Walkthrough

The changes in this pull request primarily involve updates to the internationalization strings and the handling of user interactions related to case completion in a judicial system application. The Summary.strings.ts file has been modified to replace old message entries with new ones that better prompt users for confirmation before completing a case. Additionally, the Summary.tsx file has undergone changes in the method for handling button clicks, shifting the control flow to prioritize user confirmation through a modal before proceeding with case transitions.

Changes

File Change Summary
apps/judicial-system/web/src/routes/Court/Indictments/Summary/Summary.strings.ts Removed completedCaseModalTitle and completedCaseModalBody; added completeCaseModalTitle, completeCaseModalBody, completeCaseModalPrimaryButton, and completeCaseModalSecondaryButton.
apps/judicial-system/web/src/routes/Court/Indictments/Summary/Summary.tsx Renamed handleNextButtonClick to handleModalPrimaryButtonClick; updated modal handling and button click behavior to reflect new strings and interaction flow.

Possibly related PRs

  • feat(j-s): Indictment summary page #14695: The changes in Summary.tsx are related to the handling of case completion, which aligns with the updates made in Summary.strings.ts regarding the confirmation modal for completing cases.
  • feat(j-s): Reviewer completes indictment review #14762: This PR involves changes to the Summary.tsx file, which also deals with case transitions and user interactions, similar to the modifications in the main PR that affect the confirmation modal.
  • feat(j-s): Indictment decision tag on summary page #15378: The updates in Summary.strings.ts for the new ruling decision tag are directly related to the changes in the main PR, which also modifies strings in the same file.
  • fix(j-s): Generated PDFs #16625: The modifications in Overview.tsx regarding the visibility of generated PDFs relate to the overall handling of case information, which is a broader context of the changes in the main PR that also deals with case completion and user prompts.
  • feat(j-s): Deliver Confirmed Indictment Ruling to Court #17104: The changes in CaseService for delivering confirmed rulings are relevant as they pertain to the overall workflow of case handling, which includes the completion and confirmation processes highlighted in the main PR.

Suggested labels

automerge, high priority

Suggested reviewers

  • unakb

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 235d2e2 and ae58ba3.

📒 Files selected for processing (1)
  • apps/judicial-system/web/src/routes/Court/Indictments/Summary/Summary.strings.ts (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • apps/judicial-system/web/src/routes/Court/Indictments/Summary/Summary.strings.ts

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

codecov bot commented Dec 3, 2024

Codecov Report

Attention: Patch coverage is 0% with 5 lines in your changes missing coverage. Please review.

Project coverage is 35.72%. Comparing base (ab80585) to head (658d087).
Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
...b/src/routes/Court/Indictments/Summary/Summary.tsx 0.00% 5 Missing ⚠️
Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main   #17112      +/-   ##
==========================================
- Coverage   35.74%   35.72%   -0.03%     
==========================================
  Files        6925     6917       -8     
  Lines      147647   147212     -435     
  Branches    42050    41873     -177     
==========================================
- Hits        52779    52586     -193     
+ Misses      94868    94626     -242     
Flag Coverage Δ
judicial-system-web 27.92% <0.00%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
...outes/Court/Indictments/Summary/Summary.strings.ts 0.00% <ø> (ø)
...b/src/routes/Court/Indictments/Summary/Summary.tsx 0.00% <0.00%> (ø)

... and 110 files with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ab80585...658d087. Read the comment docs.

@datadog-island-is
Copy link

datadog-island-is bot commented Dec 3, 2024

Datadog Report

Branch report: j-s/indictment-complete-modal
Commit report: cbe5f54
Test service: judicial-system-web

✅ 0 Failed, 332 Passed, 0 Skipped, 1m 17.85s Total Time
➡️ Test Sessions change in coverage: 1 no change

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: 1

🧹 Outside diff range and nitpick comments (3)
apps/judicial-system/web/src/routes/Court/Indictments/Summary/Summary.strings.ts (1)

31-53: Fix typo in modal body text

There's a typo in the Icelandic text: málsinns should be málsins (double 'n' removed).

-    defaultMessage: 'Niðurstaða málsinns verður send ákæranda og verjanda.',
+    defaultMessage: 'Niðurstaða málsins verður send ákæranda og verjanda.',
apps/judicial-system/web/src/routes/Court/Indictments/Summary/Summary.tsx (2)

Line range hint 55-66: Add error handling for navigation failures

The navigation after successful case transition should handle potential routing errors.

   if (!transitionSuccess) {
     return
   }

-    router.push(`${constants.INDICTMENTS_COMPLETED_ROUTE}/${workingCase.id}`)
+    try {
+      await router.push(`${constants.INDICTMENTS_COMPLETED_ROUTE}/${workingCase.id}`)
+    } catch (error) {
+      // Handle navigation error, possibly show an error message to the user
+      console.error('Navigation failed:', error)
+    }

Line range hint 55-178: Add tests for the confirmation modal workflow

The PR objectives mention that tests haven't been added. Please add unit tests to verify:

  1. Modal display on button click
  2. Successful case transition flow
  3. Error handling scenarios
  4. Navigation after completion

Would you like me to help generate the test cases?

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between dc014ba and 235d2e2.

📒 Files selected for processing (2)
  • apps/judicial-system/web/src/routes/Court/Indictments/Summary/Summary.strings.ts (1 hunks)
  • apps/judicial-system/web/src/routes/Court/Indictments/Summary/Summary.tsx (3 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
apps/judicial-system/web/src/routes/Court/Indictments/Summary/Summary.tsx (1)

Pattern apps/**/*: "Confirm that the code adheres to the following:

  • NextJS best practices, including file structure, API routes, and static generation methods.
  • Efficient state management and server-side rendering techniques.
  • Optimal use of TypeScript for component and utility type safety."
apps/judicial-system/web/src/routes/Court/Indictments/Summary/Summary.strings.ts (1)

Pattern apps/**/*: "Confirm that the code adheres to the following:

  • NextJS best practices, including file structure, API routes, and static generation methods.
  • Efficient state management and server-side rendering techniques.
  • Optimal use of TypeScript for component and utility type safety."
📓 Learnings (1)
apps/judicial-system/web/src/routes/Court/Indictments/Summary/Summary.tsx (1)
Learnt from: unakb
PR: island-is/island.is#15378
File: apps/judicial-system/web/src/routes/Court/Indictments/Summary/Summary.tsx:86-100
Timestamp: 2024-11-12T15:15:11.835Z
Learning: User unakb prefers explicit case handling in switch statements for key functionalities like `getRulingDecisionTagColor` to ensure clarity and avoid assumptions that a case was overlooked.
🔇 Additional comments (1)
apps/judicial-system/web/src/routes/Court/Indictments/Summary/Summary.tsx (1)

161-161: LGTM!

The modal trigger implementation is clear and follows React best practices.

@oddsson oddsson added the automerge Merge this PR as soon as all checks pass label Dec 5, 2024
@kodiakhq kodiakhq bot merged commit 500eef8 into main Dec 5, 2024
34 checks passed
@kodiakhq kodiakhq bot deleted the j-s/indictment-complete-modal branch December 5, 2024 22:51
thorhildurt pushed a commit that referenced this pull request Dec 11, 2024
* fix(j-s): Display confirmation modal before completing case

* Update apps/judicial-system/web/src/routes/Court/Indictments/Summary/Summary.strings.ts

---------

Co-authored-by: Ívar Oddsson <[email protected]>
Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge Merge this PR as soon as all checks pass
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants