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 DateTimeQuestion response update logic from creating duplicates #10369

Merged

Conversation

rithviknishad
Copy link
Member

@rithviknishad rithviknishad commented Feb 3, 2025

Proposed Changes

  • Fix DateTimeQuestion response update logic from creating duplicates

Issue reported by @nihal467

@ohcnetwork/care-fe-code-reviewers

Merge Checklist

  • Add specs that demonstrate bug / test a 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

  • Refactor

    • Revised how the questionnaire processes time inputs. Now, when a new time is selected, it replaces any previously stored value with the current one, ensuring that only the latest entry is maintained. This update streamlines the date/time response handling, resulting in a clearer and more intuitive experience.
  • New Features

    • Enhanced observation value display by formatting values based on their type for improved clarity.
  • User Interface

    • Updated loading message for fetching observations to provide better user feedback.

@rithviknishad rithviknishad requested a review from a team as a code owner February 3, 2025 11:29
@rithviknishad rithviknishad added P1 breaking issue or vital feature needs testing labels Feb 3, 2025
Copy link
Contributor

coderabbitai bot commented Feb 3, 2025

Walkthrough

The changes involve modifications to the DateTimeQuestion component's handleTimeChange function, where the spread operator for questionnaireResponse.values is removed. This results in the update callback now only including the new date-time value. Additionally, in the ObservationsList component, an import statement for the formatValue function is added, and the rendering of observation values is updated to utilize this function. The loading text is also modified for better user feedback. Lastly, the formatValue function in QuestionnaireResponsesList is made public.

Changes

File Change Summary
src/components/.../Questionnaire/QuestionTypes/DateTimeQuestion.tsx Removed the spread operator for questionnaireResponse.values in handleTimeChange, so only the newly generated date-time value (ISO string) is used in the update.
src/components/.../Facility/ConsultationDetails/ObservationsList.tsx Added import for formatValue, updated rendering to use formatValue(item.value.value, item.value_type), and changed loading text from t("loading_more") to t("loading").
src/components/.../Facility/ConsultationDetails/QuestionnaireResponsesList.tsx Changed formatValue function from private to public by adding the export keyword, with no changes to its internal logic.

Suggested labels

needs testing, needs review

Suggested reviewers

  • rithviknishad

Poem

I'm a happy rabbit, hopping by,
Celebrating changes as time goes by.
Old values now take a little rest,
New date-time stands out as the best.
Code carrots crunching in the light—
A fresh update, oh what a delight!
🥕 Hop on and keep your code bright!


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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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 Feb 3, 2025

Deploy Preview for care-ohc ready!

Name Link
🔨 Latest commit 4cd834c
🔍 Latest deploy log https://app.netlify.com/sites/care-ohc/deploys/67a0abc9b223110008978de7
😎 Deploy Preview https://deploy-preview-10369--care-ohc.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link

cloudflare-workers-and-pages bot commented Feb 3, 2025

Deploying care-fe with  Cloudflare Pages  Cloudflare Pages

Latest commit: 4cd834c
Status: ✅  Deploy successful!
Preview URL: https://9a4f415a.care-fe.pages.dev
Branch Preview URL: https://rithviknishad-fix-datetime-q.care-fe.pages.dev

View logs

Copy link

cypress bot commented Feb 3, 2025

CARE    Run #4578

Run Properties:  status check passed Passed #4578  •  git commit 3e829268b8: Fix DateTimeQuestion response update logic from creating duplicates
Project CARE
Branch Review rithviknishad/fix/datetime-question-causing-duplicates
Run status status check passed Passed #4578
Run duration 06m 04s
Commit git commit 3e829268b8: Fix DateTimeQuestion response update logic from creating duplicates
Committer Rithvik Nishad
View all properties for this run ↗︎

Test results
Tests that failed  Failures 0
Tests that were flaky  Flaky 0
Tests that did not run due to a developer annotating a test with .skip  Pending 0
Tests that did not run due to a failure in a mocha hook  Skipped 0
Tests that passed  Passing 10
View all changes introduced in this branch ↗︎

@nihal467
Copy link
Member

nihal467 commented Feb 3, 2025

LGTM

@khavinshankar khavinshankar merged commit e52edd4 into develop Feb 3, 2025
21 of 22 checks passed
@khavinshankar khavinshankar deleted the rithviknishad/fix/datetime-question-causing-duplicates branch February 3, 2025 11:50
Copy link

github-actions bot commented Feb 3, 2025

@rithviknishad 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! 🙌

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

🧹 Nitpick comments (1)
src/components/Facility/ConsultationDetails/QuestionnaireResponsesList.tsx (1)

56-84: LGTM! Good modularization of the formatValue function.

Making the formatValue function public promotes code reuse and ensures consistent value formatting across components. The function's logic handles various value types correctly and safely.

However, consider adding JSDoc documentation to help other developers understand the function's purpose and parameters:

+/**
+ * Formats a value based on its type for display
+ * @param value - The value to format, which can be of various types
+ * @param type - The type of the value (e.g., "dateTime", "choice", "decimal", "integer")
+ * @returns A formatted string representation of the value
+ */
 export function formatValue(
   value: ResponseValueType["value"],
   type: string,
 ): string {
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 3e82926 and 4cd834c.

📒 Files selected for processing (2)
  • src/components/Facility/ConsultationDetails/ObservationsList.tsx (3 hunks)
  • src/components/Facility/ConsultationDetails/QuestionnaireResponsesList.tsx (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: cypress-run (1)
🔇 Additional comments (3)
src/components/Facility/ConsultationDetails/ObservationsList.tsx (3)

10-10: LGTM! Good reuse of the formatValue function.

Importing and reusing the formatValue function from QuestionnaireResponsesList promotes code reuse and ensures consistent value formatting across components.


101-101: LGTM! Value formatting is now consistent.

The change from directly displaying item.value.value to using formatValue(item.value.value, item.value_type) ensures consistent value formatting with QuestionnaireResponsesList.


113-113: Consider using consistent loading text.

The loading text has been changed from "loading_more" to "loading", but this might affect the user's understanding of the pagination state.

Run this script to check loading text consistency across the codebase:

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

Successfully merging this pull request may close these issues.

3 participants