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

chore(application-system): Stop populating club info which duplicates employer info #16861

Merged
merged 6 commits into from
Nov 14, 2024

Conversation

norda-gunni
Copy link
Member

@norda-gunni norda-gunni commented Nov 14, 2024

...

Attach a link to issue if relevant

What

Remove club from application data

Why

Club is unnecessary because it is duplicated by employer

Screenshots / Gifs

Attach Screenshots / Gifs to help reviewers understand the scope of the pull request

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

    • Updated accident report generation to focus on individual and employer details, removing club-related information.
  • Bug Fixes

    • Eliminated the getClub function to streamline accident notification processing.
  • Chores

    • Adjusted logging level in the getAccidentNotificationStatus method for improved log management.

@norda-gunni norda-gunni requested a review from a team as a code owner November 14, 2024 10:27
Copy link
Contributor

coderabbitai bot commented Nov 14, 2024

Walkthrough

The changes involve the removal of the getClub function from the accident-notification-v2.utils.ts file, which was responsible for retrieving club-related information for sports accidents. Consequently, the applicationToAccidentReport function was updated to eliminate references to getClub, indicating that club information will no longer be included in accident reports. The remaining functions and their logic are unchanged, preserving the operational behavior of the accident report generation process. Additionally, the logging level in the getAccidentNotificationStatus method of the accident-notification.service.ts file was changed from 'log' to 'debug'.

Changes

File Change Summary
libs/application/template-api-modules/src/lib/modules/templates/accident-notification/accident-notification-v2.utils.ts Removed getClub function and its logic; updated applicationToAccidentReport to exclude club information.
libs/api/domains/health-insurance/src/lib/accident-notification.service.ts Changed logging level in getAccidentNotificationStatus from 'log' to 'debug'.

Possibly related PRs

Suggested labels

automerge

Suggested reviewers

  • HjorturJ
  • Toti91

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 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 Nov 14, 2024

Codecov Report

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

Project coverage is 36.45%. Comparing base (17266fc) to head (f10794d).
Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
...insurance/src/lib/accident-notification.service.ts 0.00% 1 Missing ⚠️
Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main   #16861   +/-   ##
=======================================
  Coverage   36.44%   36.45%           
=======================================
  Files        6852     6852           
  Lines      143567   143563    -4     
  Branches    40973    40971    -2     
=======================================
+ Hits        52330    52339    +9     
+ Misses      91237    91224   -13     
Flag Coverage Δ
api 3.34% <ø> (ø)
api-domains-health-insurance 34.33% <0.00%> (ø)
application-system-api 40.99% <ø> (+<0.01%) ⬆️
application-template-api-modules 27.65% <ø> (-0.01%) ⬇️

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

Files with missing lines Coverage Δ
...ent-notification/accident-notification-v2.utils.ts 16.39% <ø> (+0.33%) ⬆️
...insurance/src/lib/accident-notification.service.ts 0.00% <0.00%> (ø)

... and 7 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 17266fc...f10794d. Read the comment docs.

@datadog-island-is
Copy link

datadog-island-is bot commented Nov 14, 2024

Datadog Report

All test runs 9613901 🔗

4 Total Test Services: 0 Failed, 4 Passed
➡️ Test Sessions change in coverage: 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.73s 1 no change Link
api-domains-health-insurance 0 0 0 4 0 14.83s 1 no change Link
application-system-api 0 0 0 112 2 3m 26.87s 1 no change Link
application-template-api-modules 0 0 0 113 0 2m 22.04s 1 no change Link

@norda-gunni norda-gunni added the automerge Merge this PR as soon as all checks pass label Nov 14, 2024
@norda-gunni norda-gunni removed the automerge Merge this PR as soon as all checks pass label Nov 14, 2024
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 and nitpick comments (1)
libs/api/domains/health-insurance/src/lib/accident-notification.service.ts (1)

Line range hint 1-101: Well-structured service implementation!

The service demonstrates excellent TypeScript practices with proper type definitions, dependency injection, and clear separation of concerns. The modular design ensures reusability across different NextJS applications.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between e7abc47 and f10794d.

📒 Files selected for processing (1)
  • libs/api/domains/health-insurance/src/lib/accident-notification.service.ts (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
libs/api/domains/health-insurance/src/lib/accident-notification.service.ts (1)

Pattern libs/**/*: "Confirm that the code adheres to the following:

  • Reusability of components and hooks across different NextJS apps.
  • TypeScript usage for defining props and exporting types.
  • Effective tree-shaking and bundling practices."
🔇 Additional comments (1)
libs/api/domains/health-insurance/src/lib/accident-notification.service.ts (1)

72-72: LGTM! Appropriate logging level adjustment.

Changing to debug level is appropriate for routine status checks, especially after simplifying the data model by removing club information.

Let's verify the logging configuration and usage:

✅ Verification successful

Logging level change is consistent with codebase patterns

The change from 'log' to 'debug' aligns with the existing logging patterns in the health insurance domain:

  • All similar status check operations use debug level
  • The logger configuration is consistently imported and injected across services
  • Other accident-related operations also use debug level for routine status checks
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check logging configuration and usage patterns
# Expected: Consistent debug level usage for similar status checks

# Check logging configuration
rg -A 3 "LOGGER_PROVIDER" "libs/api/domains/health-insurance"

# Check debug level usage patterns
rg "logger\.(debug|log)" "libs/api/domains/health-insurance"

Length of output: 4136

@norda-gunni norda-gunni added the automerge Merge this PR as soon as all checks pass label Nov 14, 2024
@kodiakhq kodiakhq bot merged commit 4acfbd4 into main Nov 14, 2024
23 checks passed
@kodiakhq kodiakhq bot deleted the as-remove-club-from-accudent-report branch November 14, 2024 12:21
jonnigs pushed a commit that referenced this pull request Nov 26, 2024
… employer info (#16861)

* chore(application-system): Stop populating club info which duplicates employer info

* Cleanup

* Correct log method

---------

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