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): Add "acknowledged" to case and subpoena #15860

Merged
merged 6 commits into from
Sep 4, 2024

Conversation

unakb
Copy link
Member

@unakb unakb commented Sep 3, 2024

Mock birt fyrir mínar síður

What

Add acknowledged boolean to case and subpoena responses. Just returns false as is, we need to return info from RLS when we've connected that to RVG.

Why

So we can return them to Mínar Síður when ready

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

@unakb unakb requested a review from a team as a code owner September 3, 2024 08:48
Copy link
Contributor

coderabbitai bot commented Sep 3, 2024

Walkthrough

The changes introduce a new optional property, acknowledged, of type Boolean to both the IndictmentCaseData and SubpoenaData classes. This property is included in the API schema and initialized to false in the corresponding response classes. The modifications allow for tracking the acknowledgment status of cases and subpoenas, facilitating future data handling and processing.

Changes

Files Change Summary
apps/judicial-system/digital-mailbox-api/src/app/modules/cases/models/case.response.ts, apps/judicial-system/digital-mailbox-api/src/app/modules/cases/models/subpoena.response.ts Introduced an optional acknowledged property of type Boolean in both IndictmentCaseData and SubpoenaData classes. Initialized to false in response classes.

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

codecov bot commented Sep 3, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 36.93%. Comparing base (7b6a182) to head (d86e320).
Report is 1 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main   #15860   +/-   ##
=======================================
  Coverage   36.93%   36.93%           
=======================================
  Files        6681     6681           
  Lines      136464   136456    -8     
  Branches    38749    38743    -6     
=======================================
  Hits        50401    50401           
+ Misses      86063    86055    -8     
Flag Coverage Δ
api 3.39% <ø> (ø)
application-system-api 41.74% <ø> (ø)
application-template-api-modules 23.65% <ø> (-0.02%) ⬇️
application-templates-accident-notification 19.83% <ø> (ø)
application-ui-shell 21.17% <ø> (ø)

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

see 1 file 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 7b6a182...d86e320. 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: 2

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 232e85f and a82c671.

Files selected for processing (2)
  • apps/judicial-system/digital-mailbox-api/src/app/modules/cases/models/case.response.ts (2 hunks)
  • apps/judicial-system/digital-mailbox-api/src/app/modules/cases/models/subpoena.response.ts (2 hunks)
Additional context used
Path-based instructions (2)
apps/judicial-system/digital-mailbox-api/src/app/modules/cases/models/case.response.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/digital-mailbox-api/src/app/modules/cases/models/subpoena.response.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 (2)
apps/judicial-system/digital-mailbox-api/src/app/modules/cases/models/case.response.ts (1)

14-15: LGTM!

The new optional acknowledged property is added correctly to the IndictmentCaseData class with appropriate type annotation and API schema decoration.

apps/judicial-system/digital-mailbox-api/src/app/modules/cases/models/subpoena.response.ts (1)

28-29: LGTM!

The new optional acknowledged property is correctly defined in the SubpoenaData class.

@datadog-island-is
Copy link

datadog-island-is bot commented Sep 3, 2024

Datadog Report

All test runs 27f4b73 🔗

5 Total Test Services: 0 Failed, 5 Passed
➡️ Test Sessions change in coverage: 10 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.94s 1 no change Link
application-system-api 0 0 0 111 2 3m 16.27s 1 no change Link
application-template-api-modules 0 0 0 109 0 1m 44.2s 1 no change Link
application-templates-accident-notification 0 0 0 98 0 18.06s 1 no change Link
application-ui-shell 0 0 0 74 0 33.25s 1 no change Link

@gudjong gudjong added the automerge Merge this PR as soon as all checks pass label Sep 3, 2024
@kodiakhq kodiakhq bot merged commit 0fa0872 into main Sep 4, 2024
39 checks passed
@kodiakhq kodiakhq bot deleted the j-s/return-acknowledged branch September 4, 2024 11:45
jonnigs pushed a commit that referenced this pull request Sep 12, 2024
* feat(j-s): Added acknowledged to case and subpoena response

* fix(j-s): Add mock to response

* Update subpoena.response.ts

---------

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