Implement lossy decoding for scalar values#214
Open
garrettrayj wants to merge 1 commit into
Open
Conversation
garrettrayj
force-pushed
the
lossy-decoding
branch
from
742283b to
12f9b54
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds a
lossyparameter, default false, toFeedand typed initializers. When true, if there's an error decoding a value nil is filled in instead of the whole parse operation erroring out.Related to #173. This solution is not particularly graceful, but it does the trick when you just need basic info and can tolerate missing fields due to malformed values.