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

feat(j-s): Allow defenders to filter cases by court date #17232

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

unakb
Copy link
Member

@unakb unakb commented Dec 13, 2024

Verjandi geti raðað eftir fyrirtöku á málalista eins og önnur hlutverk geta gert

What

Allow defenders to filter case list by court date

Why

It's convenient

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

    • Added sorting functionality for the court date in the Defender Cases Table.
    • Enhanced data retrieval logic to include court date information.
  • Bug Fixes

    • Updated header rendering for the hearing arrangement date to improve clarity and usability.

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

coderabbitai bot commented Dec 13, 2024

Walkthrough

The changes in this pull request focus on the DefenderCasesTable component within the judicial system application. A new condition is added to the getColumnValue function to handle the 'courtDate' column, improving data retrieval. Additionally, the header for 'courtDate' is modified to include a SortButton, enabling sorting functionality based on the court date. This update integrates sorting capabilities while maintaining the overall structure of the table.

Changes

File Change Summary
apps/judicial-system/web/src/routes/Defender/Cases/components/DefenderCasesTable.tsx - Modified getColumnValue to handle 'courtDate'.
- Updated header to include SortButton for 'courtDate'.

Possibly related PRs

Suggested labels

automerge

Suggested reviewers

  • oddsson

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 generate docstrings to generate docstrings for this PR. (Experiment)
  • @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.

@datadog-island-is
Copy link

Datadog Report

Branch report: j-s/defender-filter-court-date
Commit report: f8a9465
Test service: judicial-system-web

✅ 0 Failed, 332 Passed, 0 Skipped, 55.03s Total Time
🔻 Test Sessions change in coverage: 1 decreased (-0.02%)

🔻 Code Coverage Decreases vs Default Branch (1)

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 (1)
apps/judicial-system/web/src/routes/Defender/Cases/components/DefenderCasesTable.tsx (1)

Line range hint 1-1: Add documentation and tests for the court date sorting feature

While the implementation looks good, please consider:

  1. Adding JSDoc comments to document the sorting behavior for court dates
  2. Adding unit tests to verify:
    • Sorting of court dates including null/undefined values
    • Integration with the existing table functionality

Would you like me to help generate the test cases for this feature?

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 231b35f and f009f43.

📒 Files selected for processing (1)
  • apps/judicial-system/web/src/routes/Defender/Cases/components/DefenderCasesTable.tsx (2 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
apps/judicial-system/web/src/routes/Defender/Cases/components/DefenderCasesTable.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."
🔇 Additional comments (1)
apps/judicial-system/web/src/routes/Defender/Cases/components/DefenderCasesTable.tsx (1)

135-141: Verify sorting behavior for null court dates

The implementation follows the existing pattern, but there are two considerations:

  1. The title uses "hearingArrangementDate" which might be confusing for users expecting "Court Date".
  2. The sorting implementation needs to handle cases where courtDate is null/undefined.

Let's verify the sorting implementation:

Comment on lines +60 to +62
if (column === 'courtDate') {
return entry.courtDate
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Consider improving the courtDate handling logic

The current implementation has a few potential issues:

  1. The raw courtDate is returned without any formatting, which might be inconsistent with other date displays in the table.
  2. The fallback to entry.created seems incorrect for columns other than 'courtDate' and 'defendants'.

Consider applying this improvement:

    if (column === 'courtDate') {
-     return entry.courtDate
+     return entry.courtDate ?? null
    }
-   return entry.created
+   return entry[column] ?? null

Committable suggestion skipped: line range outside the PR's diff.

Copy link

codecov bot commented Dec 13, 2024

Codecov Report

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

Project coverage is 35.74%. Comparing base (c13fd91) to head (f009f43).
Report is 2 commits behind head on main.

Files with missing lines Patch % Lines
...s/Defender/Cases/components/DefenderCasesTable.tsx 0.00% 3 Missing ⚠️
Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main   #17232      +/-   ##
==========================================
- Coverage   35.74%   35.74%   -0.01%     
==========================================
  Files        6937     6937              
  Lines      148167   148170       +3     
  Branches    42250    42251       +1     
==========================================
  Hits        52969    52969              
- Misses      95198    95201       +3     
Flag Coverage Δ
judicial-system-web 27.88% <0.00%> (-0.01%) ⬇️

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

Files with missing lines Coverage Δ
...s/Defender/Cases/components/DefenderCasesTable.tsx 0.00% <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 c13fd91...f009f43. Read the comment docs.

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