-
Notifications
You must be signed in to change notification settings - Fork 359
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
Added "Procedures" in Patient Dashboard. #5034
Added "Procedures" in Patient Dashboard. #5034
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
✅ Deploy Preview for care-egov-staging ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Cypress Tests are failing as usual. Let me know if any other change is required. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- repetitive is not being shown
- table contents are clipped, not scrollable even.
Patient Consultation: https://deploy-preview-5034--care-net.netlify.app/facility/7ab27974-32c8-4e36-bdf9-dbf102524718/patient/36cdd810-c3e1-45dd-993c-2877a46e35de/consultation/48f289bb-8ae2-46d8-b6b1-4840fa6f2385
@rithviknishad , understood will work on it. Do we have to show the "Repetitive" field? How about showing either "Time" or "Frequency" depending on if repetitive field was selected. |
@jeromtom I agree with that. |
SonarCloud Quality Gate failed. 0 Bugs No Coverage information |
Hi, This pr has been automatically marked as stale because it has not had any recent activity. It will be automatically closed if no further activity occurs for 7 more days. Thank you for your contributions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jeromtom I'm still not able to do a horizontal scroll, nor contents visible.
How about using col-span-2 scroll-x-auto
?
useEffect(() => { | ||
function handleWindowResize() { | ||
setWindowSize(getWindowSize()); | ||
} | ||
|
||
window.addEventListener("resize", handleWindowResize); | ||
|
||
return () => { | ||
window.removeEventListener("resize", handleWindowResize); | ||
}; | ||
}, []); | ||
return ( | ||
<> | ||
{windowSize.innerWidth > 1024 ? ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see a reason to have this much complication. Wouldn't tailwind's modifiers be enough?
Hi, This pr has been automatically marked as stale because it has not had any recent activity. It will be automatically closed if no further activity occurs for 7 more days. Thank you for your contributions. |
Hi, @gigincg, @nihal467, @khavinshankar, @mathew-alex, This pr has been automatically closed because it has not had any recent activity. Thank you for your contributions. Feel free to repopen the pr. |
Proposed Changes
@coronasafe/care-fe-code-reviewers @coronasafe/code-reviewers
Merge Checklist