feat(types): added data generic to WretchResponseChain #234
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.
Hi, @elbywan
Thank you so much for this library! Currently, I'm building an API client on top of it, and I'd like to have the ability to describe response types at the API level, as well as empower API client users to handle errors with catchers.
Here's how it currently works:
In this case, I cannot specify the type at the api level and have to specify it at the time of calling json(). Additionally, without changes at the api client level, I cannot handle another error using catchers.
After the proposed changes, it's expected to work as follows:
With these changes, I can specify the type at the api client level, sparing api client users from having to think about it. Additionally, it will be correctly outputted in json(). Support for catchers is included - I can handle any error without modifying the api client.
There might be other solutions to my problem, and I'd be glad to hear about them. If I missed anything, I'd be happy to add it.