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 same-day discharge date selection in DateInputV2 component #9014

Merged

Conversation

JavidSumra
Copy link
Contributor

@JavidSumra JavidSumra commented Nov 6, 2024

Proposed Changes

@ohcnetwork/care-fe-code-reviewers

Merge Checklist

  • Add specs that demonstrate bug / test the new feature.
  • Update product documentation.
  • Ensure that UI text is kept in I18n files.
  • Prep screenshot or demo video for changelog entry, and attach it to issue.
  • Request for Peer Reviews.
  • Completion of QA.

Summary by CodeRabbit

  • New Features
    • Enhanced date selection logic to allow selecting a date that matches both minimum and maximum constraints when they are the same.

@JavidSumra JavidSumra requested a review from a team as a code owner November 6, 2024 09:13
Copy link
Contributor

coderabbitai bot commented Nov 6, 2024

Warning

Rate limit exceeded

@github-actions[bot] has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 5 minutes and 45 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between b6fa2da and efc8592.

Walkthrough

The changes in DateInputV2.tsx introduce a new conditional check in the isDateWithinConstraints function. This check allows the selection of a date that is equal to both the minimum and maximum constraints when they are the same. This modification aims to improve the date selection logic without altering the overall structure or flow of the component.

Changes

File Change Summary
src/components/Common/DateInputV2.tsx Added a conditional check in isDateWithinConstraints to allow selection of a date equal to both min and max when they are the same.

Assessment against linked issues

Objective Addressed Explanation
The date and time component should allow selecting any date from the admission date up to the current date (#[9011])

🐰 In the garden where time does flow,
A date now chosen, as we all know.
With constraints that once held tight,
Same-day discharges now feel just right!
Hop along, let the dates align,
For every moment, it's truly divine! 🌼


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.

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.

Copy link

netlify bot commented Nov 6, 2024

Deploy Preview for care-ohc failed.

Name Link
🔨 Latest commit efc8592
🔍 Latest deploy log https://app.netlify.com/sites/care-ohc/deploys/672b70934547fd00080d7175

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 (2)
src/components/Common/DateInputV2.tsx (2)

193-202: Consider using dayjs for more robust date comparison.

The current implementation uses granular date component comparisons. Consider using dayjs for more maintainable date equality checks:

-    if (
-      min &&
-      max &&
-      min.getDate() === max.getDate() &&
-      day === min.getDate() &&
-      month === min.getMonth() &&
-      year === min.getFullYear()
-    ) {
-      return true;
-    }
+    if (min && max && dayjs(min).isSame(max, 'day') && dayjs(new Date(year, month, day)).isSame(min, 'day')) {
+      return true;
+    }

This approach:

  • Reduces code complexity
  • Handles edge cases more reliably
  • Aligns with the existing dayjs usage in the component

193-202: Consider documenting the same-day date handling behavior.

The special case handling for same-day dates is a significant behavior that should be documented for future maintainers and users of the component.

Consider:

  1. Adding a JSDoc comment to the isDateWithinConstraints function explaining the same-day date handling
  2. Updating the component's props documentation to clarify that same-day selections are allowed when min and max dates are equal
  3. Adding test cases to verify this behavior
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 3008cc2 and b6fa2da.

📒 Files selected for processing (1)
  • src/components/Common/DateInputV2.tsx (1 hunks)
🔇 Additional comments (1)
src/components/Common/DateInputV2.tsx (1)

193-202: LGTM! Verify the time component handling.

The new condition correctly enables same-day date selection, addressing the core issue.

Let's verify the time component handling:

✅ Verification successful

Time component is properly handled - no issues found

The implementation correctly handles the time component:

  • When allowTime is false, getDayStart() is used which sets hours, minutes, seconds, and milliseconds to 0
  • When allowTime is true, the full date object with time is preserved
  • The same-day validation in isDateWithinConstraints() only checks date components (day, month, year) which is correct since time constraints are handled separately through the getDayStart() function
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for time-related validations in the component
rg -A 5 "allowTime.*isDateWithinConstraints|isDateWithinConstraints.*allowTime" .

Length of output: 83


Script:

#!/bin/bash
# Let's first check the full implementation of isDateWithinConstraints
ast-grep --pattern 'isDateWithinConstraints($$$) {
  $$$
}'

# Also check for any time-related props or state
rg "allowTime|timeFormat|time" src/components/Common/DateInputV2.tsx

Length of output: 728


Script:

#!/bin/bash
# Let's check how getDayStart is implemented since it's used with allowTime
ast-grep --pattern 'getDayStart($$$) {
  $$$
}'

# Also check for any time-related utility functions
rg -A 5 "function.*Date|const.*Date" src/components/Common/DateInputV2.tsx

Length of output: 1939

@nihal467 nihal467 added urgent P1 breaking issue or vital feature labels Nov 6, 2024
@nihal467
Copy link
Member

nihal467 commented Nov 6, 2024

LGTM @rithviknishad can you review the code

Copy link
Member

@rithviknishad rithviknishad left a comment

Choose a reason for hiding this comment

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

LGTM; @shivankacker could you review this

@github-actions github-actions bot added the Deploy-Failed Deplyment is not showing preview label Nov 6, 2024
@rithviknishad rithviknishad removed the Deploy-Failed Deplyment is not showing preview label Nov 6, 2024
@rithviknishad rithviknishad merged commit 0f9cc52 into ohcnetwork:develop Nov 6, 2024
16 of 20 checks passed
Copy link

github-actions bot commented Nov 6, 2024

@JavidSumra Your efforts have helped advance digital healthcare and TeleICU systems. 🚀 Thank you for taking the time out to make CARE better. We hope you continue to innovate and contribute; your impact is immense! 🙌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs review P1 breaking issue or vital feature tested urgent
Projects
None yet
4 participants