Remove redundant request interceptor #722
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Originally there were two identical request interceptors, both adding the JWT token header except for login and register requests. However, umi-request's interceptors chain supports async functions naturally, and the Promise returned by the first interceptor is properly handled without needing a second interceptor to process it. Therefore, the second interceptor is redundant and can be safely removed without affecting functionality, simplifying the codebase. Signed-off-by: dodo920306 <[email protected]>
yeasy
approved these changes
Jul 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Originally there were two identical request interceptors, both adding the JWT token header except for login and register requests.
However, umi-request's interceptors chain supports async functions naturally, and the Promise returned by the first interceptor is properly handled without needing a second interceptor to process it.
Therefore, the second interceptor is redundant and can be safely removed without affecting functionality, simplifying the codebase.