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

Fixed : Newly Added Patient Is Not Instantly Visible in the patient-switcher #10819

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

Conversation

Mahendar0701
Copy link
Contributor

@Mahendar0701 Mahendar0701 commented Feb 26, 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

  • New Features
    • Enhanced the patient registration process to ensure the patient list reflects the latest additions immediately.
    • Improved user experience by automatically retaining the newly registered patient's details for easier future reference.

@Mahendar0701 Mahendar0701 requested a review from a team as a code owner February 26, 2025 07:43
Copy link
Contributor

coderabbitai bot commented Feb 26, 2025

Walkthrough

This change enhances the patient registration process by ensuring that after a patient is created, the system invalidates cached patient data and updates local storage with the new patient’s information. These modifications improve data consistency and state management without altering any exported or public entity declarations.

Changes

File Change Summary
src/pages/PublicAppointments/PatientRegistration.tsx Adds call to queryClient.invalidateQueries({ queryKey: ["patients"] }) to refresh cached patient data and stores the new patient's data in local storage.

Sequence Diagram(s)

sequenceDiagram
    participant UI as PatientRegistration
    participant API as Server
    participant QueryCache as QueryClient
    participant Storage as localStorage

    UI->>API: createPatient(data)
    API-->>UI: success(responseData)
    UI->>QueryCache: invalidateQueries(["patients"])
    UI->>Storage: setItem("selectedPatient", JSON.stringify(responseData))
Loading

Possibly related PRs

Suggested labels

needs review, tested

Suggested reviewers

  • rithviknishad
  • Jacobjeevan

Poem

Hopping through code in the soft moonlight,
I nibbled some queries to make them bright.
Cached tales are cleared with a swift little jump,
Storing new patients without a single bump.
With twitching whiskers, I celebrate each line—
CodeRabbit’s cheer makes everything fine!
🐰✨

Tip

CodeRabbit's docstrings feature is now available as part of our Pro Plan! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.


📜 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 6ffedec and aa5e987.

📒 Files selected for processing (1)
  • src/pages/PublicAppointments/PatientRegistration.tsx (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: cypress-run (1)
🔇 Additional comments (2)
src/pages/PublicAppointments/PatientRegistration.tsx (2)

181-183: Good implementation of query invalidation!

Invalidating the patients query is essential to ensure the patient-switcher component displays the newly created patient immediately, addressing the issue mentioned in the PR title. This ensures any components relying on patient data will refetch and receive the up-to-date information.


185-185: Excellent addition of localStorage persistence

Storing the newly created patient's data in localStorage ensures the patient-switcher can immediately access the selected patient without waiting for a refetch. This complements the query invalidation by providing immediate access to the new patient's information.

✨ Finishing Touches
  • 📝 Generate Docstrings

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.
  • @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 26, 2025

Deploy Preview for care-ohc ready!

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

@rithviknishad rithviknishad added reviewed reviewed by a core member and removed needs review labels Feb 26, 2025
publish("patient:upsert", data);
localStorage.setItem("selectedPatient", JSON.stringify(data));
Copy link
Member

Choose a reason for hiding this comment

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

Why should we store the patient data in localstorage? @Jacobjeevan @rithviknishad ?
If its for the ID we should probably add patient id to the routes. The data would be avilable in the context right 🤔

Copy link
Member

Choose a reason for hiding this comment

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

I assumed this was a requirement, since I've been seeing caching things to local storage for all public patient related workflow since the beginning 😬

Copy link
Contributor

@Jacobjeevan Jacobjeevan Feb 28, 2025

Choose a reason for hiding this comment

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

We can remove this local storage.

@Mahendar0701 go ahead and do that here, patient-switcher and in PatientUserProvider.

@nihal467
Copy link
Member

@rithviknishad is it ready for review, seem like a discussion going on !

@nihal467 nihal467 added the question Further information is requested label Feb 27, 2025
@Mahendar0701
Copy link
Contributor Author

@rithviknishad let me know if I need to modify anything in this PR

@rithviknishad
Copy link
Member

@Jacobjeevan

@Jacobjeevan Jacobjeevan added changes required and removed question Further information is requested needs testing reviewed reviewed by a core member labels Feb 28, 2025
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.

Newly Added Patient Is Not Instantly Visible in the Patient List of patient dashboard
5 participants