Fixes token not refreshing in background

[rithviknishad]

Proposed Changes

• Fixes token not refreshing in background

@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 background session refresh that maintains active user sessions reliably, even when the component isn’t visible to you.

[coderabbitai]

Walkthrough

The changes introduce a new property, refetchIntervalInBackground, to the token refresh query configuration in the AuthUserProvider component. This property, set to true, enables the query to continue fetching data in the background when the component is not actively displayed. The existing refetchInterval remains unchanged, maintaining the periodic token refresh behavior based on the configured interval. No alterations were made to the exported or public entity declarations.

Changes

File	Change Summary
src/Providers/AuthUserProvider.tsx	Added refetchIntervalInBackground: true to the tokenRefreshQuery configuration to enable background data fetching. Retained refetchInterval logic.

Sequence Diagram(s)

sequenceDiagram
    participant A as AuthUserProvider
    participant Q as tokenRefreshQuery
    participant S as Server

    A->>Q: Configure token refresh with refetchInterval & refetchIntervalInBackground
    Q->>S: Request token refresh (even when not visible)
    S-->>Q: Return new token
    Q-->>A: Update token in background

Loading

Suggested reviewers

• shivankacker
• Jacobjeevan

Poem

In the code’s bright light, I've hopped anew,
A rabbit weaving magic, in a tweak so true.
Background fetch whispers in the silent night,
Tokens refresh quietly, keeping all things right.
Hoppy cheers to improvements, under starry byte!
🐇✨

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.

[netlify]

❌ Deploy Preview for care-ohc failed.

Name	Link
🔨 Latest commit	d61e949
🔍 Latest deploy log	https://app.netlify.com/sites/care-ohc/deploys/67ab2b6ddbee42000846676b

[cloudflare-workers-and-pages]

Deploying care-fe with    Cloudflare Pages

Latest commit:	d61e949
Status:	✅  Deploy successful!
Preview URL:	https://1a36e410.care-fe.pages.dev
Branch Preview URL:	https://rithviknishad-fix-refresh-to.care-fe.pages.dev

View logs

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

src/Providers/AuthUserProvider.tsx (1)

47-55: Consider adding a comment to document the background refresh behavior.

Adding a brief comment would help future maintainers understand why background refresh is necessary for token management.

 const tokenRefreshQuery = useQuery({
+  // Enable background refresh to maintain token validity even when tab is inactive
   queryKey: ["user-refresh-token"],
   queryFn: query(routes.token_refresh, {
     body: { refresh: refreshToken || "" },
   }),
   refetchIntervalInBackground: true,
   refetchInterval: careConfig.auth.tokenRefreshInterval,
   enabled: !!refreshToken && !!user,
 });

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 9f223f8 and d61e949.

📒 Files selected for processing (1)

• src/Providers/AuthUserProvider.tsx (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: cypress-run (1)

🔇 Additional comments (1)

src/Providers/AuthUserProvider.tsx (1)

47-55: LGTM! This change effectively fixes the token refresh issue.

The addition of refetchIntervalInBackground: true ensures that the token continues to refresh even when the browser tab is not active, preventing token expiration issues.

[github-actions]

@rithviknishad Your efforts have helped advance digital healthcare and TeleICU systems. 🚀 Thank you for taking the time out to make CARE better. We hope you continue to innovate and contribute; your impact is immense! 🙌