feat(error)!: more specific errors including their source #252
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
A failing file doesnt panic anymore with client-ureq. BREAKING CHANGE: decode_response methods are now private. They probably shouldnt have been public in the first place BREAKING CHANGE: mostly all Error variants are now different (only the Api error response is the same)
ayrat555
approved these changes
Jan 31, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Bugfix: A failing file doesn't panic anymore with client-ureq.
BREAKING CHANGE: decode_response methods are now private. They probably shouldn't have been public in the first place
BREAKING CHANGE: mostly all Error variants are now different (only the Api error response is the same)