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): Filtering of public prosecution cases #14802

Merged
merged 3 commits into from
May 18, 2024

Conversation

unakb
Copy link
Member

@unakb unakb commented May 15, 2024

Þín yfirlesin mál sem saksóknari RSAK birtast í Afgreidd mál

What

Changed the filter so that public prosecutors can still see cases they were assigned to review even after they've finished reviewing them

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

  • Bug Fixes
    • Simplified the logic for filtering cases, ensuring more accurate and streamlined results for users reviewing indictment cases.

@unakb unakb requested a review from a team as a code owner May 15, 2024 10:07
Copy link
Contributor

coderabbitai bot commented May 15, 2024

Walkthrough

The recent changes streamline the filtering logic for prosecution user cases by removing redundant conditions. Specifically, the indictment_review_decision check has been eliminated, leaving only the indictment_reviewer_id filter. Corresponding updates were made in the backend filter logic and the frontend case filtering, ensuring consistency and simplifying the overall codebase.

Changes

File Path Change Summary
.../cases.filter.ts Simplified the getProsecutionUserCasesQueryFilter function by removing the indictment_review_decision condition.
.../cases.filter.spec.ts Updated the getCasesQueryFilter function to remove the nested Op.and condition involving indictment_reviewer_id and indictment_review_decision.
.../Cases.tsx Modified the case filtering logic to check for c.indictmentReviewer?.id === user?.id && !c.indictmentReviewDecision.

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.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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

Review Details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits Files that changed from the base of the PR and between b3b8102 and c306f1a.
Files selected for processing (3)
  • apps/judicial-system/backend/src/app/modules/case/filters/cases.filter.ts (1 hunks)
  • apps/judicial-system/backend/src/app/modules/case/filters/test/cases.filter.spec.ts (2 hunks)
  • apps/judicial-system/web/src/routes/Shared/Cases/Cases.tsx (1 hunks)
Files not reviewed due to errors (1)
  • apps/judicial-system/web/src/routes/Shared/Cases/Cases.tsx (no review received)
Additional Context Used
Path-based Instructions (3)
apps/judicial-system/backend/src/app/modules/case/filters/cases.filter.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."
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."
apps/judicial-system/backend/src/app/modules/case/filters/test/cases.filter.spec.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."
Additional comments not posted (4)
apps/judicial-system/backend/src/app/modules/case/filters/cases.filter.ts (2)

48-48: Ensure the removal of the indictment_review_decision condition aligns with the intended logic. Verify that cases with non-null indictment_review_decision should still be included in the results.


Line range hint 154-154: Ensure the new filtering condition correctly identifies cases awaiting review by the indictment reviewer. Verify that the logic aligns with the intended behavior of including cases with non-null indictmentReviewDecision.

apps/judicial-system/backend/src/app/modules/case/filters/test/cases.filter.spec.ts (2)

63-63: Ensure the updated test case correctly reflects the new filter condition for indictment_reviewer_id. Verify that the removal of the indictment_review_decision condition is consistent with the updated function logic.


121-121: Ensure the updated test case correctly reflects the new filter condition for indictment_reviewer_id. Verify that the removal of the indictment_review_decision condition is consistent with the updated function logic.

@datadog-island-is
Copy link

datadog-island-is bot commented May 15, 2024

Datadog Report

All test runs df7043c 🔗

3 Total Test Services: 0 Failed, 3 Passed
⬆️ Test Sessions change in coverage: 1 increased (+0.08%), 5 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.97s 1 no change Link
judicial-system-backend 0 0 0 19477 0 16m 13.52s 1 increased (+0.08%) Link
judicial-system-web 0 0 0 312 0 1m 7.66s 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: 0

Review Details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits Files that changed from the base of the PR and between c306f1a and cd99335.
Files selected for processing (1)
  • apps/judicial-system/backend/src/app/modules/case/filters/cases.filter.ts (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • apps/judicial-system/backend/src/app/modules/case/filters/cases.filter.ts

Copy link

codecov bot commented May 15, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 36.95%. Comparing base (42a5b46) to head (bc1cc5a).
Report is 1 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main   #14802      +/-   ##
==========================================
- Coverage   36.97%   36.95%   -0.02%     
==========================================
  Files        6327     6319       -8     
  Lines      129016   128486     -530     
  Branches    36831    36670     -161     
==========================================
- Hits        47698    47483     -215     
+ Misses      81318    81003     -315     
Flag Coverage Δ
judicial-system-web 28.08% <100.00%> (+<0.01%) ⬆️

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

Files Coverage Δ
...ckend/src/app/modules/case/filters/cases.filter.ts 97.95% <ø> (ø)
...icial-system/web/src/routes/Shared/Cases/Cases.tsx 74.22% <100.00%> (+2.50%) ⬆️

... and 68 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 559ac86...bc1cc5a. Read the comment docs.

@gudjong gudjong added the automerge Merge this PR as soon as all checks pass label May 18, 2024
@kodiakhq kodiakhq bot merged commit da3b47f into main May 18, 2024
33 checks passed
@kodiakhq kodiakhq bot deleted the j-s/filter-public-defender branch May 18, 2024 23:46
@coderabbitai coderabbitai bot mentioned this pull request Nov 27, 2024
6 tasks
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.

3 participants