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

Merged
merged 4 commits into from
Dec 19, 2024

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-island-is bot commented Dec 13, 2024

Datadog Report

All test runs de8c8a5 🔗

6 Total Test Services: 0 Failed, 6 Passed
➡️ Test Sessions change in coverage: 16 no change

Test Services
Service Name Failed Known Flaky New Flaky Passed Skipped Total Time Code Coverage Change Test Service View
api 0 0 0 4 0 2.72s 1 no change Link
application-system-api 0 0 0 46 0 2m 8.03s 1 no change Link
application-template-api-modules 0 0 0 118 0 2m 5.81s 1 no change Link
application-ui-shell 0 0 0 74 0 32.55s 1 no change Link
judicial-system-web 0 0 0 332 0 55.15s 1 no change Link
web 0 0 0 84 0 24.32s 1 no change Link

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:

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.66%. Comparing base (6167d4f) to head (95d861e).
Report is 1 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.68%   35.66%   -0.03%     
==========================================
  Files        6922     6948      +26     
  Lines      148524   148534      +10     
  Branches    42419    42424       +5     
==========================================
- Hits        53008    52969      -39     
- Misses      95516    95565      +49     
Flag Coverage Δ
api 3.33% <ø> (ø)
application-system-api 38.73% <ø> (-0.01%) ⬇️
application-template-api-modules 27.69% <ø> (ø)
application-ui-shell 22.31% <ø> (ø)
judicial-system-web 27.77% <0.00%> (-0.01%) ⬇️
web 2.40% <ø> (ø)

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%> (ø)

... and 73 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 6167d4f...95d861e. Read the comment docs.

Copy link
Member

@thorhildurt thorhildurt left a comment

Choose a reason for hiding this comment

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

Just one nit, otherwise looks good 👌

@unakb unakb requested a review from oddsson December 17, 2024 15:14
@oddsson oddsson removed their request for review December 17, 2024 20:25
@gudjong gudjong added the automerge Merge this PR as soon as all checks pass label Dec 19, 2024
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.

4 participants