-
-
Notifications
You must be signed in to change notification settings - Fork 13
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: error type is useApiData
is a FetchError
#38
fix: error type is useApiData
is a FetchError
#38
Conversation
β Deploy Preview for nuxt-api-party ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Good catch! And great work. Thank you very much! Will review later. Just wanna send some flowers. π» |
useApiData
31972d0
to
e87a789
Compare
e87a789
to
42c3a5d
Compare
42c3a5d
to
120f6a3
Compare
Do you think this will this still be relevant with #44? |
I've made changes to be more minimal. With #44, the types should be more reflective of what they are at runtime. There is an exception of course if there's a transport error in the request or some other bug causing an exception. |
useApiData
useApiData
is a FetchError
Wonderful! |
π Linked issue
β Type of change
π Description
The error type in useApiData is incorrect. It's actual type is a
NuxtError
with thedata
type dependent on whetherclient: true
is set. Ifclient: true
,data
is the response data from the API. Otherwise it is set to what looks like aIFetchError
.π Checklist