[Enhancement] Add DecodingError as associated type in decode enum case in ResponseError #1
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.
Hello! I'm using this package for a side project, so thank you for open sourcing it 🙂
This PR is a proposal to add
Swift.DecodingError
as an associated value in the.decode
enum case inResponseError
. The reason: sometimes, when you're debugging an API call with lots of properties and sub-objects, is useful to inspect the Xcode Console and see which property doesn't have the correct type. Without exposingSwift.DecodingError
, this ability is hidden by the package.It's just a proposal so feel free to close it if you don't consider it's applicable for your package!