Add 'Update Details' Button in Community Nurse Log Update Details Page

[kihan2518B]

Proposed Changes

• Fixes Add "Update Details" Button in view details page of community nurse and details log update #9060

@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

• New Features
  • Added an "Update Log" button in the Critical Care Preview component for easy access to update daily rounds details.
  • Introduced a new primary button variant with enhanced styles for light and dark themes, expanding visual options for users.
  • Updated the Daily Round List Details component to include a new button with a CareIcon for improved user interaction.
• Bug Fixes
  • Corrected the button label in the PatientLogupdate class from "Update Details" to "Update Log" for consistency.

[coderabbitai]

Walkthrough

The changes involve the addition of a new button labeled "Update Log" in the CriticalCarePreview component located in src/components/LogUpdate/CriticalCarePreview.tsx. This button is positioned beneath the existing "Back to Consultation" button and links to a URL for updating daily rounds details using specific props. The integration does not affect existing functionality or logic within the component, maintaining the current data fetching and rendering processes. Additional changes include the introduction of a new button variant in the button configuration and modifications in related components for consistency.

Changes

File Path	Change Summary
src/components/LogUpdate/CriticalCarePreview.tsx	Added "Update Log" button below "Back to Consultation" for updating daily rounds details.
src/components/ui/button.tsx	Introduced a new primary button variant with specific styles for light and dark themes.
cypress/pageobject/Patient/PatientLogupdate.ts	Updated clickUpdateDetail method to reflect the change from "Update Details" to "Update Log".
src/components/Patient/DailyRoundListDetails.tsx	Replaced ButtonV2 with a new Button component and integrated CareIcon for navigation.

Assessment against linked issues

Objective	Addressed	Explanation
Add "Update Details" Button in view details page (#9060)	❌	The button is labeled "Update Log" instead of "Update Details".

Possibly related PRs

• Fix wrong terminology used in place of Log Update #9089: The changes in this PR involve updating terminology from "daily rounds" to "log updates," which directly relates to the modifications made in the main PR that introduced a new "Update Log" button in the CriticalCarePreview component.
• Fixed Breadcrumb to Display Detailed Name Instead of ID #9200: This PR modifies breadcrumb navigation to display patient names instead of IDs, which aligns with the main PR's focus on enhancing user interface elements related to patient updates.
• Adjusted the view change button position #9172: The adjustments to button positions and functionality in this PR are relevant as they reflect ongoing improvements to UI components, similar to the changes made in the main PR for the "Update Log" button.
• Add edit button to immunisation section; replaced buttons with shadcn buttons across PatientsDetail section #9245: This PR addresses the addition of an Edit button in the immunisation section, which is part of the broader effort to enhance the user interface, paralleling the updates made in the main PR regarding the "Update Log" button.

Suggested labels

needs review, tested

Suggested reviewers

• rithviknishad
• Jacobjeevan
• shivankacker

Poem

In the realm of care, a button appears,
"Update Log" now calms all fears.
Beneath the old, it finds its place,
A path to updates, a smoother grace.
With clicks and taps, our tasks align,
In the world of health, all will be fine! 🐇✨

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.

[netlify]

✅ Deploy Preview for care-ohc ready!

Name	Link
🔨 Latest commit	5abfa46
🔍 Latest deploy log	https://app.netlify.com/sites/care-ohc/deploys/674f3d0f7e3dec0008ed1f1d
😎 Deploy Preview	https://deploy-preview-9094--care-ohc.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between c0ffd4a and 3b6d2c3.

📒 Files selected for processing (1)

• src/components/LogUpdate/CriticalCarePreview.tsx (1 hunks)

🔇 Additional comments (2)

src/components/LogUpdate/CriticalCarePreview.tsx (2)

59-69: Button layout integration looks good

The new button is well-integrated into the existing layout with consistent spacing and styling.

---

62-66: Implementation successfully meets PR objectives

The added button provides the required direct navigation to the edit log update page as specified in issue #9060. The URL construction is correct and includes all necessary parameters.

[kihan2518B]

@rithviknishad can you review my pr

[nihal467]

@kihan2518B

• As per the existing design of "Brief Update" and the issue description, position the "Update Details" button at the top-right corner of the card for both the "Community Nurse" and "Detail Log Update" view details pages.

[nihal467]

@kihan2518B keep the button colour primary ,

[rithviknishad]

It's queued for testing @kihan2518B

[nihal467]

LGTM

[github-actions]

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