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 : Cancelled requests in appointments page and Remove files button from actions #10219

Open
wants to merge 22 commits into
base: develop
Choose a base branch
from

Conversation

Mahendar0701
Copy link
Contributor

@Mahendar0701 Mahendar0701 commented Jan 27, 2025

Proposed Changes

@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

Summary by CodeRabbit

  • New Features

    • Enhanced patient home page with interactive tooltips for date information.
    • Replaced patient file upload button with a new plugin component for patient actions.
  • Improvements

    • Introduced conditional querying in the appointments page to optimize server requests based on date parameters.

@Mahendar0701 Mahendar0701 requested a review from a team as a code owner January 27, 2025 17:34
Copy link
Contributor

coderabbitai bot commented Jan 27, 2025

Walkthrough

The pull request introduces two primary changes: the addition of tooltip functionality to the PatientHome component for displaying patient-related dates, and the implementation of an enabled property in the AppointmentsPage component's useQuery hooks. The tooltip implementation replaces the previous static date display with an interactive tooltip, while the query modification ensures that API calls are only made when both date_from and date_to parameters are present.

Changes

File Change Summary
src/components/Patient/PatientHome.tsx - Added tooltip imports from UI library
- Replaced date display with tooltip-based implementation
- Removed patient file upload button
- Integrated PLUGIN_Component for patient actions
src/pages/Appointments/AppointmentsPage.tsx - Modified useQuery hook to use enabled property for conditional query execution

Assessment against linked issues

Objective Addressed Explanation
Use query.debounced in appointments page [#10192] No implementation of query.debounced was made.
Remove view patient files button [#10192]
Avoid cancelled calls in appointments page [#10192] The implementation does not utilize query.debounced to prevent cancelled calls.

Possibly related PRs

  • changed modified_date to created_date on PatientHome page #9309: The changes in the main PR, which introduce tooltip functionality for displaying dates in the PatientHome component, are related to the retrieved PR that modifies how the creation and modification dates are displayed in the same component.
  • Update tooltip position and rotation in Discussion Notes panel #8938: The changes in the main PR, which involve the implementation of tooltip functionality in the PatientHome component, are related to the adjustments made to tooltip positioning and visibility in the PatientNotesSlideover component.
  • Patient Registration form refactor #9854: The changes in the main PR, which involve the integration of a PLUGIN_Component in the PatientHome component, are directly related to the modifications in the retrieved PR, where a similar PLUGIN_Component is also introduced in the PatientInfoCard component.

Suggested Labels

changes required

Suggested Reviewers

  • rithviknishad
  • Jacobjeevan

Poem

🐰 A rabbit's tale of code so bright,
Tooltips dancing with pure delight!
Debounced queries, smooth and clean,
Enhancing UX on every screen.
Code hops forward with graceful might! 🚀

Tip

🌐 Web search-backed reviews and chat
  • We have enabled web search-based reviews and chat for all users. This feature allows CodeRabbit to access the latest documentation and information on the web.
  • You can disable this feature by setting web_search: false in the knowledge_base settings.
  • Please share any feedback in the Discord discussion.

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between dd56e6c and 7e3d035.

📒 Files selected for processing (1)
  • src/components/Patient/PatientHome.tsx (4 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/components/Patient/PatientHome.tsx
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: cypress-run (1)

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 Jan 27, 2025

Deploy Preview for care-ohc ready!

Name Link
🔨 Latest commit 7e3d035
🔍 Latest deploy log https://app.netlify.com/sites/care-ohc/deploys/67a24854432fe60008204c39
😎 Deploy Preview https://deploy-preview-10219--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.

@Mahendar0701 Mahendar0701 changed the title Fix : Cancel requests in appointments page and Remove files button from actions Fix : Cancelled requests in appointments page and Remove files button from actions Jan 27, 2025
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 (2)
src/components/Patient/PatientHome.tsx (2)

171-186: Consider increasing the tooltip delay duration.

The tooltip implementation is good, but a 1ms delay might cause unintended tooltip flickers during mouse movement. Consider increasing delayDuration to a more standard value (e.g., 200-300ms) for better UX.

-                    <TooltipProvider delayDuration={1}>
+                    <TooltipProvider delayDuration={200}>

199-214: Consider extracting a reusable date tooltip component.

The tooltip implementation is duplicated between modified and created dates. Consider extracting this into a reusable component to improve maintainability and reduce code duplication.

Example implementation:

const DateTooltip = ({ date }: { date: string | null }) => (
  <TooltipProvider delayDuration={200}>
    <Tooltip>
      <TooltipTrigger asChild>
        <span>
          {date ? relativeDate(date) : "--:--"}
        </span>
      </TooltipTrigger>
      <TooltipContent>
        {date ? formatDateTime(date) : "--:--"}
      </TooltipContent>
    </Tooltip>
  </TooltipProvider>
);

Usage:

-                    <TooltipProvider delayDuration={1}>
-                      <Tooltip>
-                        <TooltipTrigger asChild>
-                          <span>
-                            {patientData.created_date
-                              ? relativeDate(patientData.created_date)
-                              : "--:--"}
-                          </span>
-                        </TooltipTrigger>
-                        <TooltipContent>
-                          {patientData.created_date
-                            ? formatDateTime(patientData.created_date)
-                            : "--:--"}
-                        </TooltipContent>
-                      </Tooltip>
-                    </TooltipProvider>
+                    <DateTooltip date={patientData.created_date} />
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between a481488 and 4f5a68e.

📒 Files selected for processing (2)
  • src/components/Patient/PatientHome.tsx (3 hunks)
  • src/pages/Appointments/AppointmentsPage.tsx (2 hunks)
🔇 Additional comments (3)
src/components/Patient/PatientHome.tsx (1)

8-13: LGTM!

The tooltip component imports are correctly structured and properly utilized in the implementation.

src/pages/Appointments/AppointmentsPage.tsx (2)

669-669: LGTM! Good performance optimization.

The use of query.debounced is a good optimization that will help reduce unnecessary API calls during rapid parameter changes.


778-778: LGTM! Consistent implementation.

The use of query.debounced is consistent with the implementation in AppointmentColumn, maintaining a uniform approach to API call optimization.

@rithviknishad rithviknishad added invalid This doesn't seem right and removed needs testing needs review labels Jan 29, 2025
@rithviknishad rithviknishad removed their request for review January 30, 2025 05:25
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/Patient/PatientHome.tsx (1)

182-197: Consider extracting the date tooltip into a reusable component.

The tooltip implementation is duplicated for both modified and created dates. Consider extracting this into a reusable component to improve maintainability.

+ // Create a new file: src/components/Common/DateTooltip.tsx
+ import {
+   Tooltip,
+   TooltipContent,
+   TooltipProvider,
+   TooltipTrigger,
+ } from "@/components/ui/tooltip";
+ import { formatDateTime, relativeDate } from "@/Utils/utils";
+ 
+ interface DateTooltipProps {
+   date?: string;
+   delayDuration?: number;
+ }
+ 
+ export const DateTooltip = ({ date, delayDuration = 1 }: DateTooltipProps) => (
+   <TooltipProvider delayDuration={delayDuration}>
+     <Tooltip>
+       <TooltipTrigger asChild>
+         <span>
+           {date ? relativeDate(date) : "--:--"}
+         </span>
+       </TooltipTrigger>
+       <TooltipContent>
+         {date ? formatDateTime(date) : "--:--"}
+       </TooltipContent>
+     </Tooltip>
+   </TooltipProvider>
+ );

// In PatientHome.tsx
- <TooltipProvider delayDuration={1}>
-   <Tooltip>
-     <TooltipTrigger asChild>
-       <span>
-         {patientData.modified_date
-           ? relativeDate(patientData.modified_date)
-           : "--:--"}
-       </span>
-     </TooltipTrigger>
-     <TooltipContent>
-       {patientData.modified_date
-         ? formatDateTime(patientData.modified_date)
-         : "--:--"}
-     </TooltipContent>
-   </Tooltip>
- </TooltipProvider>
+ <DateTooltip date={patientData.modified_date} />

- <TooltipProvider delayDuration={1}>
-   <Tooltip>
-     <TooltipTrigger asChild>
-       <span>
-         {patientData.created_date
-           ? relativeDate(patientData.created_date)
-           : "--:--"}
-       </span>
-     </TooltipTrigger>
-     <TooltipContent>
-       {patientData.created_date
-         ? formatDateTime(patientData.created_date)
-         : "--:--"}
-     </TooltipContent>
-   </Tooltip>
- </TooltipProvider>
+ <DateTooltip date={patientData.created_date} />

Also applies to: 210-225

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 8a6808b and b0f9d31.

📒 Files selected for processing (2)
  • src/components/Patient/PatientHome.tsx (3 hunks)
  • src/pages/Appointments/AppointmentsPage.tsx (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/pages/Appointments/AppointmentsPage.tsx
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: cypress-run (1)
🔇 Additional comments (2)
src/components/Patient/PatientHome.tsx (2)

8-13: LGTM! Clean import structure for tooltip components.

The imports are well-organized and properly structured using named imports.


182-197: Great UX improvement with tooltips!

The implementation provides a good user experience by:

  • Showing relative dates for quick reference
  • Providing detailed datetime information in tooltips
  • Using consistent delay duration
  • Handling null/undefined dates gracefully

Also applies to: 210-225

@Jacobjeevan Jacobjeevan removed the invalid This doesn't seem right label Feb 3, 2025
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/Patient/PatientHome.tsx (1)

203-227: Consider extracting the date display logic into a reusable component.

The tooltip implementation for created_date is identical to modified_date. To improve maintainability and reduce code duplication, consider extracting this pattern into a reusable component.

Example implementation:

type DateDisplayProps = {
  date: string | null;
  label: string;
  user?: {
    first_name?: string;
    last_name?: string;
  };
};

const DateDisplay: React.FC<DateDisplayProps> = ({ date, label, user }) => (
  <div>
    <div className="text-xs font-normal leading-5 text-gray-600">
      {label}
      <div className="font-semibold text-gray-900">
        {user?.first_name} {user?.last_name}
      </div>
    </div>
    <div className="whitespace-normal text-sm font-semibold text-gray-900">
      {date ? (
        <TooltipProvider delayDuration={1}>
          <Tooltip>
            <TooltipTrigger asChild>
              <span>{relativeTime(date)}</span>
            </TooltipTrigger>
            <TooltipContent>
              {formatDateTime(date)}
            </TooltipContent>
          </Tooltip>
        </TooltipProvider>
      ) : (
        "--:--"
      )}
    </div>
  </div>
);

Usage:

-<div>
-  <div className="text-xs font-normal leading-5 text-gray-600">
-    {t("last_updated_by")}
-    <div className="font-semibold text-gray-900">
-      {patientData.updated_by?.first_name}{" "}
-      {patientData.updated_by?.last_name}
-    </div>
-  </div>
-  ...
-</div>
+<DateDisplay
+  date={patientData.modified_date}
+  label={t("last_updated_by")}
+  user={patientData.updated_by}
+/>
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 084219f and dd56e6c.

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

8-13: LGTM!

The imports are well-organized and include all necessary components for the tooltip implementation.

Also applies to: 26-26


174-199: LGTM! Changes align with previous review feedback.

The implementation successfully addresses the previous review comments:

  • Tooltip is only rendered when modified_date is available
  • Using relativeTime for display with detailed tooltip
  • Updated by name is properly placed in a separate div

Copy link
Contributor

@Jacobjeevan Jacobjeevan left a comment

Choose a reason for hiding this comment

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

LGTM.

I'd suggest adjusting the font size (smaller than the user's name) + font color of the times as well, something with grey. Test and see what works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Avoid cancelled calls in appointments page | Remove view files from action section
3 participants