Open gurramkarthiknetha opened 2 days ago
The changes in this pull request focus on modifying the layout and styling of various UI components across multiple files. Key updates include enhancements to margin and spacing for buttons and containers, adjustments to the rendering logic of tooltips, and refinements in the handling of state variables related to user interactions. Additionally, the control flow for managing patient consent records has been improved to ensure better user experience and data integrity.
File Path | Change Summary |
---|---|
src/CAREUI/interactive/FiltersSlideover.tsx |
Updated className of AdvancedFilterButton to include mt-2 for margin-top styling. |
src/components/Common/ButtonV2.tsx |
Added mt-required class to button styles; refined tooltip rendering logic. |
src/components/Common/Menu.tsx |
Added mt-2 class to MenuButton for improved spacing. |
src/components/Facility/FacilityCard.tsx |
Changed class name for facility details layout to include gap-2 ; updated notification button layout. |
src/components/Kanban/Board.tsx |
Enhanced responsiveness with new CSS classes for KanbanBoard and KanbanSection ; clarified data handling. |
src/components/Patient/ManagePatients.tsx |
Updated button layout for filtering/exporting; improved onTabChange logic based on user roles. |
src/components/Patient/PatientConsentRecords.tsx |
Introduced showPCSChangeModal state; modified upload logic to check for existing consent records. |
ButtonV2
component, which is directly related to the changes made in the main PR regarding the AdvancedFilterButton
component's className
property in FiltersSlideover.tsx
.patientRegisterAuth
function, which may relate to UI components that include buttons, similar to the modifications made in the main PR regarding button styling.needs review
, needs testing
π In the code, I hop and play,
With buttons styled in a new way.
Margins added, gaps so neat,
A joyful UI, oh what a treat!
With consent records, we now glide,
In a world where changes abide! πΌ
[!WARNING] There were issues while running some tools. Please review the errors and either fix the toolβs configuration or disable the tool if itβs a critical failure.
π§ eslint (1.23.1)
> If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.src/components/Common/ButtonV2.tsx
Oops! Something went wrong! :( ESLint: 8.57.1 Error: Failed to load parser '@typescript-eslint/parser' declared in '.eslintrc.json': Cannot find module '@typescript-eslint/parser' Require stack: - /.eslintrc.json at Module._resolveFilename (node:internal/modules/cjs/loader:1248:15) at Function.resolve (node:internal/modules/helpers:145:19) at Object.resolve (/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:2346:46) at ConfigArrayFactory._loadParser (/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:3325:39) at ConfigArrayFactory._normalizeObjectConfigDataBody (/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:3099:43) at _normalizeObjectConfigDataBody.next () at ConfigArrayFactory._normalizeObjectConfigData (/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:3040:20) at _normalizeObjectConfigData.next ( ) at ConfigArrayFactory.loadInDirectory (/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:2886:28) at CascadingConfigArrayFactory._loadConfigInAncestors (/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:3871:46)
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?
Name | Link |
---|---|
Latest commit | 88e5236e6936fb8293189979da4128c567f1ef5f |
Latest deploy log | https://app.netlify.com/sites/care-ohc/deploys/673f83093cdac000081c5bca |
Deploy Preview | https://deploy-preview-9161--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.
Also follow the PR format what we have (refer to other PRs). Edit the title to be readable as well.
Also follow the PR format what we have (refer to other PRs). Edit the title to be readable as well.
Also this βοΈ @gurramkarthiknetha
Now i kept from the same branch . Did i need to change any more
@gurramkarthiknetha It's required to follow the original PR template and link the issue in it. Also keep a proper readable title that conveys what has changed in the PR.
this are the changes made by me.
Summary by CodeRabbit
Release Notes
New Features
Improvements
Bug Fixes
These changes aim to enhance user experience and improve functionality across the application.