We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It's frankly annoying to have to handle happy and sad path separately in a try..catch, especially when they can be a quite common thing.
Let's avoid this, we should only throw on exceptional scenarios (e.g. unexpected content-type from #9)
We'll follow a similar response as oazapfts, like so:
const { status, data, headers } = await rpc.get('...');
The text was updated successfully, but these errors were encountered:
No branches or pull requests
It's frankly annoying to have to handle happy and sad path separately in a try..catch, especially when they can be a quite common thing.
Let's avoid this, we should only throw on exceptional scenarios (e.g. unexpected content-type from #9)
We'll follow a similar response as oazapfts, like so:
The text was updated successfully, but these errors were encountered: