Skip to content

AMM-1204#57

Merged
helenKaryamsetty merged 1 commit intoPSMRI:developfrom
ravishanigarapu:develop
Mar 17, 2025
Merged

AMM-1204#57
helenKaryamsetty merged 1 commit intoPSMRI:developfrom
ravishanigarapu:develop

Conversation

@ravishanigarapu
Copy link
Copy Markdown
Contributor

@ravishanigarapu ravishanigarapu commented Mar 12, 2025

📋 Description

JIRA ID: AMM-1204

Please provide a summary of the change and the motivation behind it. Include relevant context and details.


✅ Type of Change

  • 🐞 Bug fix (non-breaking change which resolves an issue)
  • New feature (non-breaking change which adds functionality)
  • 🔥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • 🛠 Refactor (change that is neither a fix nor a new feature)
  • ⚙️ Config change (configuration file or build script updates)
  • 📚 Documentation (updates to docs or readme)
  • 🧪 Tests (adding new or updating existing tests)
  • 🎨 UI/UX (changes that affect the user interface)
  • 🚀 Performance (improves performance)
  • 🧹 Chore (miscellaneous changes that don't modify src or test files)

ℹ️ Additional Information

Please describe how the changes were tested, and include any relevant screenshots, logs, or other information that provides additional context.

Summary by CodeRabbit

  • New Features
    • Enhanced call record date formatting to ensure consistent and accurate display of call start and end times. These improvements provide more reliable timestamp information for call records.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Mar 12, 2025

Walkthrough

The changes introduce two new private methods in CallClosureImpl.java for formatting timestamps. The methods, getCallDateStartFormat and getCallDateEndFormat, are used to format callStartDate and callEndDate respectively. In the createEcdCallRecordsInOutboundCalls method, if callStartDate is null, the logic now retrieves a timestamp from either motherRecord.getLmpDate() or childRecord.getDob() and processes it through getCallDateStartFormat. Similarly, the assignment of callEndDate now uses getCallDateEndFormat instead of a direct timestamp assignment.

Changes

File Change Summary
src/.../CallClosureImpl.java - Added private Timestamp getCallDateStartFormat(Timestamp callStartDate)
- Added private Timestamp getCallDateEndFormat(Timestamp callEndDate)
- Updated createEcdCallRecordsInOutboundCalls to utilize these methods

Sequence Diagram(s)

sequenceDiagram
    participant Caller
    participant CallClosureImpl
    participant RecordSource

    Caller->>CallClosureImpl: createEcdCallRecordsInOutboundCalls(data)
    alt callStartDate is null
        CallClosureImpl->>RecordSource: Retrieve LMP/DOB
        RecordSource-->>CallClosureImpl: Timestamp value
        CallClosureImpl->>CallClosureImpl: getCallDateStartFormat(timestamp)
        Note right of CallClosureImpl: Format to start of day
        CallClosureImpl-->>CallClosureImpl: Formatted callStartDate
    else
        CallClosureImpl-->>CallClosureImpl: Use provided callStartDate
    end
    CallClosureImpl->>CallClosureImpl: getCallDateEndFormat(timestamp)
    Note right of CallClosureImpl: Format to end of day
    Caller-->>CallClosureImpl: Returns formatted call details
Loading

Suggested Reviewers

  • devikasuresh20

Poem

I'm a rabbit with a code so neat,
Formatting dates with a rhythmic beat.
New methods hop in, start and end the day,
Making timestamps jump in a clever way.
Hoppy changes spring from every line,
Cheers to progress in our code design!
🐰✨

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • @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.

CodeRabbit Configuration 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.

@sonarqubecloud
Copy link
Copy Markdown

Copy link
Copy Markdown

@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

🧹 Nitpick comments (1)
src/main/java/com/iemr/ecd/service/associate/CallClosureImpl.java (1)

512-522: Consider adding null checks to the formatting methods.

The formatting methods don't currently handle null timestamp inputs. Since these methods are used in various places, adding null checks would improve robustness.

 private Timestamp getCallDateEndFormat(Timestamp callEndDate) {
+    if (callEndDate == null) {
+        return null;
+    }
     SimpleDateFormat format = new SimpleDateFormat("yyyy-MM-dd 23:59:59");
     String time = format.format(callEndDate);
     return Timestamp.valueOf(time);
 }

 private Timestamp getCallDateStartFormat(Timestamp callStartDate) {
+    if (callStartDate == null) {
+        return null;
+    }
     SimpleDateFormat format = new SimpleDateFormat("yyyy-MM-dd 00:00:00");
     String time = format.format(callStartDate);
     return Timestamp.valueOf(time);
 }
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3d6cfbc and 356b7b7.

📒 Files selected for processing (1)
  • src/main/java/com/iemr/ecd/service/associate/CallClosureImpl.java (7 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Analyze (java)
🔇 Additional comments (8)
src/main/java/com/iemr/ecd/service/associate/CallClosureImpl.java (8)

25-25: LGTM: Appropriate imports added for the new functionality.

The added imports for SimpleDateFormat and Date support the new timestamp formatting methods.

Also applies to: 30-30


406-410: LGTM: Improved timestamp handling for mother records.

Good implementation of consistent date formatting. The code now properly formats callStartDate to the start of day when retrieved from motherRecord.getLmpDate(), providing better consistency in date handling.


418-418: LGTM: Enhanced end date formatting.

The implementation now properly formats the call end date to the end of the day (23:59:59) using the new utility method, providing better consistency in date range calculations.

Also applies to: 426-426


435-435: LGTM: Consistent start date formatting for the next iteration.

Good use of the new formatting utility to ensure that the new start date is consistently set to the beginning of the day (00:00:00).

Also applies to: 472-472


443-446: LGTM: Improved timestamp handling for child records.

Good implementation of consistent date formatting for child records. The code now properly formats callStartDate to the start of day when retrieved from childRecord.getDob().


455-455: LGTM: Enhanced end date formatting for child records.

The implementation now correctly formats the child record call end date to the end of the day (23:59:59), ensuring consistency in date range calculations.

Also applies to: 463-463


512-516: LGTM: Well-implemented utility method for end-of-day formatting.

The getCallDateEndFormat method cleanly handles formatting timestamps to the end of the day (23:59:59), which is important for inclusive date range queries.


518-522: LGTM: Well-implemented utility method for start-of-day formatting.

The getCallDateStartFormat method cleanly handles formatting timestamps to the start of the day (00:00:00), which is important for consistent date range queries.

Copy link
Copy Markdown
Member

@helenKaryamsetty helenKaryamsetty left a comment

Choose a reason for hiding this comment

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

looks fine

@helenKaryamsetty helenKaryamsetty merged commit cbeeecc into PSMRI:develop Mar 17, 2025
This was referenced May 26, 2025
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.

2 participants