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): Cancelled Unassigned Indictment #15910

Merged
merged 2 commits into from
Sep 9, 2024

Conversation

gudjong
Copy link
Member

@gudjong gudjong commented Sep 5, 2024

Cancelled Unassigned Indictment

Ákæra afturkölluð áður en hún er móttekin - dettur í "bíður úthlutunar" hjá dómstól þegar dómurinn hefur lokað málinu.

What

  • Displays a cancelled indictment that has not been assigned to a judge in the correct court case list.

Why

  • Verified bug.

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 filtering logic for cases awaiting assignment to include only those with states of 'Submitted' or 'Received.' This enhances the accuracy of case display for users.

@gudjong gudjong requested a review from a team as a code owner September 5, 2024 18:01
Copy link
Contributor

coderabbitai bot commented Sep 5, 2024

Walkthrough

The change involves modifying the filtering logic in the Cases component of the Cases.tsx file. The criteria for identifying cases awaiting assignment has been updated to include only cases with the states CaseState.SUBMITTED or CaseState.RECEIVED, instead of excluding cases with the state CaseState.WAITING_FOR_CANCELLATION. This adjustment refines the selection process for cases displayed as awaiting assignment.

Changes

Files Change Summary
.../web/src/routes/Shared/Cases/Cases.tsx Updated filtering logic to include cases with states CaseState.SUBMITTED or CaseState.RECEIVED.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant CasesComponent
    participant CaseState

    User->>CasesComponent: Request to view cases
    CasesComponent->>CaseState: Fetch current case states
    CaseState-->>CasesComponent: Return case states
    CasesComponent->>CasesComponent: Filter cases (SUBMITTED, RECEIVED)
    CasesComponent-->>User: Display filtered cases
Loading

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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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
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: 0

Outside diff range, codebase verification and nitpick comments (1)
apps/judicial-system/web/src/routes/Shared/Cases/Cases.tsx (1)

Line range hint 1-300: Adherence to NextJS and TypeScript best practices.

The component makes good use of React hooks for state management and TypeScript for type safety. The modular structure and clear separation of concerns are commendable.

Consider enhancing the error handling by providing more specific user feedback or recovery options in case of failed operations.

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between a4c7324 and e890696.

Files selected for processing (1)
  • apps/judicial-system/web/src/routes/Shared/Cases/Cases.tsx (1 hunks)
Additional context used
Path-based instructions (1)
apps/judicial-system/web/src/routes/Shared/Cases/Cases.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/Shared/Cases/Cases.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-06-27T14:37:07.823Z
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 not posted (1)
apps/judicial-system/web/src/routes/Shared/Cases/Cases.tsx (1)

150-150: Refined filtering logic for cases awaiting assignment.

The updated condition to include only cases in CaseState.SUBMITTED or CaseState.RECEIVED should more accurately reflect the intended case statuses for assignment. This change aligns with the PR's objective to correct the display of cancelled indictments.

Please ensure that this change integrates well with the rest of the system, particularly how cases transition between different states.

@datadog-island-is
Copy link

datadog-island-is bot commented Sep 5, 2024

Datadog Report

Branch report: j-s/fix-unassigned-cancellation
Commit report: 02d53c1
Test service: judicial-system-web

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

Copy link

codecov bot commented Sep 5, 2024

Codecov Report

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

Project coverage is 36.82%. Comparing base (e3254de) to head (526f5f8).
Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
...icial-system/web/src/routes/Shared/Cases/Cases.tsx 0.00% 1 Missing ⚠️
Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main   #15910   +/-   ##
=======================================
  Coverage   36.82%   36.82%           
=======================================
  Files        6692     6692           
  Lines      137100   137100           
  Branches    38975    38975           
=======================================
  Hits        50482    50482           
  Misses      86618    86618           
Flag Coverage Δ
judicial-system-web 28.73% <0.00%> (ø)

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

Files with missing lines Coverage Δ
...icial-system/web/src/routes/Shared/Cases/Cases.tsx 72.72% <0.00%> (ø)

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 e3254de...526f5f8. Read the comment docs.

@oddsson oddsson added the automerge Merge this PR as soon as all checks pass label Sep 9, 2024
@kodiakhq kodiakhq bot merged commit 251a043 into main Sep 9, 2024
30 checks passed
@kodiakhq kodiakhq bot deleted the j-s/fix-unassigned-cancellation branch September 9, 2024 11:01
jonnigs pushed a commit that referenced this pull request Sep 12, 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