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: when the 'refreshToken' expires, it does not re-authenticate #4231

Merged
merged 1 commit into from
Aug 26, 2024

Conversation

likui628
Copy link
Collaborator

@likui628 likui628 commented Aug 26, 2024

Description

closes #4228

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update
  • Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Checklist

ℹ️ Check all checkboxes - this will indicate that you have done everything in accordance with the rules in CONTRIBUTING.

  • If you introduce new functionality, document it. You can run documentation with pnpm run docs:dev command.
  • Run the tests with pnpm test.
  • Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.
  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

Summary by CodeRabbit

  • New Features
    • Enhanced error handling for authentication failures by introducing an automatic re-authentication attempt when a refresh token operation fails. This improves user experience during authentication issues.

Copy link

changeset-bot bot commented Aug 26, 2024

⚠️ No Changeset found

Latest commit: 79f1fe2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Contributor

coderabbitai bot commented Aug 26, 2024

Walkthrough

The changes introduce an asynchronous call to doReAuthenticate() within the authenticateResponseInterceptor function. This addition enhances error handling by attempting to re-authenticate users when a refresh token operation fails, thereby improving the application's response to authentication errors.

Changes

Files Change Summary
packages/effects/request/src/request-client/preset-interceptors.ts Added an asynchronous call to doReAuthenticate() in the authenticateResponseInterceptor function for improved error handling.

Assessment against linked issues

Objective Addressed Explanation
Bug: refresh token失效后 未跳转登录界面 (#4228)

Poem

In the code where bunnies hop,
A token's life may soon stop.
With a call to re-authenticate,
We’ll bounce back, it’s never too late!
So let’s cheer for the fix today,
Hopping forward, come what may! 🐇✨


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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 as 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 resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 20a3868 and 79f1fe2.

Files selected for processing (1)
  • packages/effects/request/src/request-client/preset-interceptors.ts (1 hunks)
Additional comments not posted (1)
packages/effects/request/src/request-client/preset-interceptors.ts (1)

63-64: LGTM! Ensure doReAuthenticate is properly defined.

The changes correctly handle the case where the refresh token fails by calling doReAuthenticate. Ensure that doReAuthenticate is properly defined and handles the re-authentication process correctly.

The code changes are approved.

Run the following script to verify the definition of doReAuthenticate:

Verification successful

doReAuthenticate is properly defined and utilized across the codebase.

The function doReAuthenticate is defined as an async function in several files, indicating it is a utility function used for handling re-authentication processes. Its usage in preset-interceptors.ts is consistent with its purpose. No issues found with its definition or usage.

  • Defined in:
    • playground/src/api/request.ts
    • apps/web-antd/src/api/request.ts
    • apps/web-ele/src/api/request.ts
    • apps/web-naive/src/api/request.ts
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the definition of `doReAuthenticate`.

# Test: Search for the definition of `doReAuthenticate`. Expect: Proper definition and implementation.
rg --type python --type js --type ts $'doReAuthenticate'

Length of output: 86


Script:

#!/bin/bash
# Description: Verify the definition of `doReAuthenticate`.

# Test: Search for the definition of `doReAuthenticate`. Expect: Proper definition and implementation.
rg --type py --type js --type ts $'doReAuthenticate'

Length of output: 954

@vince292007 vince292007 added the bug Something isn't working label Aug 26, 2024
@vince292007 vince292007 merged commit df7757d into main Aug 26, 2024
16 checks passed
@vince292007 vince292007 deleted the fixture/issue-4228 branch August 26, 2024 01:54
@github-actions github-actions bot locked and limited conversation to collaborators Sep 26, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bug: refresh token失效后 未跳转登录界面
2 participants