Fixing an issue that type 'null' and 'undefined' is not assignable to validateStatus when typescript strict option is enabled#3200
Merged
jasonsaayman merged 1 commit intoaxios:masterfrom Oct 20, 2020
Conversation
chinesedfan
suggested changes
Aug 15, 2020
Contributor
chinesedfan
left a comment
There was a problem hiding this comment.
Thanks for your update. And in order to avoid similar mistakes, can you update the test file with a new case? In addition, validateStatus? has included undefined I think.
Contributor
|
@cprayer Ping for updating. |
… validateStatus when typescript strict option is enabled
fe85e35 to
89c40f3
Compare
Contributor
Author
|
@chinesedfan Before -> validateStatus?: ((status: number) => boolean | null) After - validateStatus?: ((status: number) => boolean) | null TS2345 Error of line 341, 345 is irrelevant to the validateStatus option. So I don't care about this. |
chinesedfan
approved these changes
Oct 17, 2020
jasonsaayman
approved these changes
Oct 20, 2020
Member
jasonsaayman
left a comment
There was a problem hiding this comment.
This seems to be a good solution to this issue.
This was referenced Jan 5, 2021
This was referenced Mar 5, 2021
This was referenced Mar 18, 2021
Closed
mbargiel
pushed a commit
to mbargiel/axios
that referenced
this pull request
Jan 27, 2022
… validateStatus when typescript strict option is enabled (axios#3200)
This was referenced Oct 27, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In previous my PR(#2773), I had missed about two things.
So I fix above things in this PR.