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

chore(j-s): Switch indictment confirmation request #17153

Merged
merged 4 commits into from
Dec 9, 2024

Conversation

oddsson
Copy link
Member

@oddsson oddsson commented Dec 5, 2024

Switch indictment confirmation request

Asana

What

Switch indictment confirmation request so that the deny option is first and accept is second.

Why

We generally place the yes option on the right and the no option on the left

Screenshots / Gifs

Screenshot 2024-12-05 at 21 43 24

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

    • Improved user interface for confirming or denying indictments with updated radio button labels and IDs.
    • Enhanced clarity in the decision-making process for users regarding indictment confirmation.
  • Bug Fixes

    • Corrected the logic for handling indictment confirmation decisions to ensure accurate modal displays based on user selection.

@oddsson oddsson requested a review from a team as a code owner December 5, 2024 21:43
Copy link
Contributor

coderabbitai bot commented Dec 5, 2024

Walkthrough

The changes in this pull request focus on the Overview component in the Overview.tsx file, specifically modifying the handling of the indictment confirmation process. The IDs and labels for the RadioButton components for confirming or denying indictments have been swapped. The state variable indictmentConfirmationDecision is now set based on user selection, affecting the logic in the handleNextButtonClick function to determine the appropriate modal type to display. The updates aim to clarify user interactions regarding indictment decisions.

Changes

File Path Change Summary
apps/judicial-system/web/src/routes/Prosecutor/Indictments/Overview/Overview.tsx Swapped IDs and labels for confirmation and denial RadioButton components; updated state handling for indictmentConfirmationDecision; modified logic in handleNextButtonClick for modal type display based on user selection.

Possibly related PRs

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 954e11c and 5737221.

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

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 5, 2024

Codecov Report

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

Project coverage is 35.65%. Comparing base (02d4080) to head (77be9e0).
Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
...outes/Prosecutor/Indictments/Overview/Overview.tsx 0.00% 2 Missing ⚠️
Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main   #17153      +/-   ##
==========================================
- Coverage   35.73%   35.65%   -0.08%     
==========================================
  Files        6928     6923       -5     
  Lines      147817   147945     +128     
  Branches    42127    42210      +83     
==========================================
- Hits        52818    52747      -71     
- Misses      94999    95198     +199     
Flag Coverage Δ
judicial-system-web 27.89% <0.00%> (ø)

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

Files with missing lines Coverage Δ
...outes/Prosecutor/Indictments/Overview/Overview.tsx 0.00% <0.00%> (ø)

... and 54 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 02d4080...77be9e0. Read the comment docs.

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

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 2421d10 and 954e11c.

📒 Files selected for processing (1)
  • apps/judicial-system/web/src/routes/Prosecutor/Indictments/Overview/Overview.tsx (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
apps/judicial-system/web/src/routes/Prosecutor/Indictments/Overview/Overview.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."
📓 Learnings (1)
apps/judicial-system/web/src/routes/Prosecutor/Indictments/Overview/Overview.tsx (4)
Learnt from: oddsson
PR: island-is/island.is#16731
File: apps/judicial-system/web/src/routes/Shared/IndictmentOverview/IndictmentOverview.tsx:172-186
Timestamp: 2024-11-12T15:15:20.157Z
Learning: In `IndictmentOverview.tsx`, since the defendants data does not change, using `useMemo` to memoize the filtering logic is unnecessary.
Learnt from: gudjong
PR: island-is/island.is#16863
File: apps/judicial-system/web/src/routes/Prosecutor/Indictments/Overview/Overview.tsx:194-200
Timestamp: 2024-11-27T14:34:38.028Z
Learning: In `Overview.tsx`, the `defendant.subpoenas` array never contains null or undefined `subpoena` objects, so additional null checks are not needed.
Learnt from: unakb
PR: island-is/island.is#14712
File: apps/judicial-system/web/src/routes/PublicProsecutor/Indictments/Overview/IndictmentOverview.tsx:0-0
Timestamp: 2024-11-12T15:15:11.835Z
Learning: The judicial system application uses a toaster notification system to handle errors globally.
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/Prosecutor/Indictments/Overview/Overview.tsx (1)

286-290: LGTM! Radio button reordering aligns with UI conventions

The placement of the deny option before the confirm option follows the common UI pattern of positioning negative actions on the left and positive actions on the right, improving user experience through consistent interface patterns.

@datadog-island-is
Copy link

datadog-island-is bot commented Dec 5, 2024

Datadog Report

Branch report: j-s/switch-indictment-confirmation-request
Commit report: 34a52c7
Test service: judicial-system-web

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

@oddsson oddsson added the automerge Merge this PR as soon as all checks pass label Dec 9, 2024
@oddsson oddsson added automerge Merge this PR as soon as all checks pass and removed automerge Merge this PR as soon as all checks pass labels Dec 9, 2024
@kodiakhq kodiakhq bot merged commit 93800d2 into main Dec 9, 2024
34 checks passed
@kodiakhq kodiakhq bot deleted the j-s/switch-indictment-confirmation-request branch December 9, 2024 21:15
thorhildurt pushed a commit that referenced this pull request Dec 11, 2024
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