You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading to the newer @hey-api/client-fetch, the data object is correctly typed, but the error type is now untyped (previously it was correctly typed)
I am actually surprised this worked before the standalone client. Either way, I think it's because of the 4XX status code. I am adding support for such codes in the next release, please let me know if that fixes it for you!
Description
After upgrading to the newer
@hey-api/client-fetch
, thedata
object is correctly typed, but theerror
type is now untyped (previously it was correctly typed)Spec
This is easy enough to work-around by forcibly casting the objects, but I presume this is an oversight.
The text was updated successfully, but these errors were encountered: