-
Notifications
You must be signed in to change notification settings - Fork 6
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
Refactor: some fetcher-related code #121
Refactor: some fetcher-related code #121
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
4ad98bb
to
6c4213b
Compare
6c4213b
to
89d499d
Compare
Rebased. |
|
||
if ( | ||
isAxiosError(error) && | ||
error.response?.data && |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
error.response?.data && | |
error.response && | |
error.response.data && |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The type of response here is still Nullable, probably because AxiosError might be thrown before and during the request?
export interface AxiosError<T = any> extends Error {
...,
response?: AxiosResponse<T>;
...,
}
89d499d
to
860f49f
Compare
Rebased. |
860f49f
to
119d0ea
Compare
Rebased. |
119d0ea
to
b4056f9
Compare
This PR extracts the types related to fetcher from the components to ExplorerService and index.d.ts, preparing for the next step of refactoring to the models level.