Enum errors #79
Merged
Enum errors #79
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
|
Oops, this also includes #77. Eh, will rebase… |
| public var path: [String] | ||
| public let object: AnyObject | ||
| public var rootObject: AnyObject? | ||
| case TypeMismatch(expected: Any.Type, actual: Any.Type, Metadata) |
Closed
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.
DecodingErrorenumDecodingError.InfotoDecodingError.MetadataContext: #60, #65
Was trying to use Decodable with a Result type and came across this error:
Perhaps the protocol
DecodingErrorshould be an enum like before.Reasons:
definitelyperhaps feels more swiftyOne could also argue that non
DecodingErrorserrors shouldn't be wrapped, but just passed through, but have implemented wrapping here.