Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Wish List

See original GitHub issue

Hey! Just adopted this library for a big project at work. Thanks for putting it together (or at least, thanks for sprucing up the thing you forked it from).

There are a few things that I think would make this a lot more usable. If you’re interested, I’d be happy to submit some PRs:

Implementing the Fantasy Land Spec (mainly just .ap() and .map()) on Ok and Err
Using property accessors to auto-bind .decode() and .decodeThen() to make them easier to use in point-free compositions
Exposing additional metadata in Err to allow more flexible handling, i.e. building validation, etc.

Let me know what you think! Thanks again.

Issue Analytics

State:
Created 4 years ago
Comments:8 (2 by maintainers)

Top GitHub Comments

1reaction

joanllenascommented, May 18, 2019

@nateabele I added a few tests for the Result type and detected a couple of minor issues with the functor interface types, but it’s fixed now. Let me know if you find any issues.

Thanks for your contribution!

1reaction

jorrollcommented, May 17, 2019

@nateabele gotcha, thanks for the explanation! 👍