Skip to content

Conversation

mulias
Copy link
Contributor

@mulias mulias commented Jan 26, 2019

  • Improve how error messages are constructed when a decoder fails. I still don't love it, but it's a step in the right direction.
  • Add decoders and utilities to help with managing imperfect data. The result decoder introduces a composable way to let parts of a decoder fail, without failing the full decoder. The Result.errors and Decoder.mapError utilities help work with the result decoder.
  • Provide an example of how these tools can be used to validate an array of data, filtering out and logging failures.

Elias Mulhall added 7 commits January 26, 2019 16:45
Decoder to prevent error propagation. Always succeeds, but instead of
returning the decoded value, return a `Result` object containing either
the successfully decoded value, or the decoder failure error.
Counterpart to Result.successes
@mulias mulias force-pushed the em/result-decoder branch from 57d15c1 to 697ae94 Compare January 27, 2019 02:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant