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 page crash due to patient user context #9836

Closed
wants to merge 1 commit into from

Conversation

shivankacker
Copy link
Member

@shivankacker shivankacker commented Jan 7, 2025

Screen.Recording.2025-01-08.at.4.33.18.AM.mov

Possible fix

@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

    • Introduced a new patient context hook that allows for nullable patient context
    • Enhanced flexibility in handling patient data retrieval
  • Refactor

    • Updated context hook to provide more robust error handling
    • Modified patient context import and usage in sidebar component

@shivankacker shivankacker requested a review from a team as a code owner January 7, 2025 23:30
Copy link
Contributor

coderabbitai bot commented Jan 7, 2025

Walkthrough

This pull request introduces a new useNullablePatientContext hook in the patient user context management system. The modification allows for a more flexible approach to handling patient context by returning null instead of throwing an error when the context is not available. The change impacts the AppSidebar component, which now uses the new nullable context hook to retrieve patient user information.

Changes

File Change Summary
src/hooks/usePatientUser.ts Added useNullablePatientContext() method that returns null instead of throwing an error when context is unavailable
src/components/ui/sidebar/app-sidebar.tsx Updated import to use useNullablePatientContext and modified context retrieval logic

Possibly related PRs

Suggested labels

needs testing, needs review, P1

Suggested reviewers

  • rithviknishad
  • Jacobjeevan

Poem

🐰 A Context Hook, Soft and Light
Nullable now, no error's might
Patient data flows with grace
Null returns without a trace
Coding magic, rabbit's delight! 🌈


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

Deploy Preview for care-ohc ready!

Name Link
🔨 Latest commit bbb8b02
🔍 Latest deploy log https://app.netlify.com/sites/care-ohc/deploys/677db91ffc9ef00008920ffa
😎 Deploy Preview https://deploy-preview-9836--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.

Copy link

Deploying care-fe with  Cloudflare Pages  Cloudflare Pages

Latest commit: bbb8b02
Status: ✅  Deploy successful!
Preview URL: https://47dbd077.care-fe.pages.dev
Branch Preview URL: https://fix-patient-context-error.care-fe.pages.dev

View logs

Copy link

cypress bot commented Jan 7, 2025

CARE    Run #4189

Run Properties:  status check passed Passed #4189  •  git commit bbb8b0295b: Fix page crash due to patient user context
Project CARE
Branch Review fix-patient-context-error
Run status status check passed Passed #4189
Run duration 01m 15s
Commit git commit bbb8b0295b: Fix page crash due to patient user context
Committer Shivank Kacker
View all properties for this run ↗︎

Test results
Tests that failed  Failures 0
Tests that were flaky  Flaky 0
Tests that did not run due to a developer annotating a test with .skip  Pending 0
Tests that did not run due to a failure in a mocha hook  Skipped 0
Tests that passed  Passing 4
View all changes introduced in this branch ↗︎

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/hooks/usePatientUser.ts (1)

15-21: LGTM! Consider adding JSDoc comments.

The implementation correctly addresses the page crash by providing a nullable alternative to usePatientContext. This is a good pattern for handling optional contexts.

Consider adding JSDoc comments to document the behavior:

+/**
+ * Hook to access the PatientUserContext without throwing when context is missing.
+ * @returns The patient user context if available, null otherwise
+ */
export function useNullablePatientContext() {
  const ctx = useContext(PatientUserContext);
  if (!ctx) {
    return null;
  }
  return ctx;
}
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f1210af and bbb8b02.

📒 Files selected for processing (2)
  • src/components/ui/sidebar/app-sidebar.tsx (2 hunks)
  • src/hooks/usePatientUser.ts (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: OSSAR-Scan
🔇 Additional comments (1)
src/components/ui/sidebar/app-sidebar.tsx (1)

27-27: LGTM! Verify crash resolution.

The switch to useNullablePatientContext and the safe handling of null values should effectively prevent the page crash.

Let's verify this fixes all potential crash scenarios by checking for any unguarded context usage:

Also applies to: 146-146

✅ Verification successful

✅ Crash prevention verified

All uses of patientUserContext are properly guarded with null checks, preventing any potential crashes from accessing properties on undefined/null values.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for direct property access on patientUserContext that might crash
rg "patientUserContext\." src/components/ui/sidebar/app-sidebar.tsx

# Search for potential usage of context without null checks
ast-grep --pattern 'patientUserContext && $_' src/components/ui/sidebar/app-sidebar.tsx

Length of output: 1594

@shivankacker shivankacker added the bug Something isn't working label Jan 7, 2025
@khavinshankar
Copy link
Member

@shivankacker Can't we return null in usePatientContext itself instead of creating a new one, also is it only erroring out here?

@gigincg
Copy link
Member

gigincg commented Jan 8, 2025

Solved with b7d8b6b

@gigincg gigincg closed this Jan 8, 2025
@sainak sainak deleted the fix-patient-context-error branch January 24, 2025 15:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants