-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
More Complete Examples for Semigroup and Semiring Validation #16
Comments
I think it would be great to have an example project in this repo or in the README - thanks for putting this together! It would be good to try to minimize the dependencies and code as much as possible, I think. |
Yeah, the repo was a bit of a rabbit hole for me this weekend to get comfortable with the library 😅. I'll pare some stuff back and try to PR an example repo soon. I'm thinking an |
How does this look: https://github.com/jkachmar/purescript-validation/tree/feat/add-examples/examples/semigroup ? If that's good, I can do something similar for |
Yeah, this library is frustrating af without a full-blown explanation of it. It's questions like:
Every time I use this library I get annoyed that I have to |
#17 added examples for the Semigroup version. |
Closed by #17? |
This should not be considered closed by #17; that PR only added examples for semigroup validation. Semiring validation is still lacking documentation (although personally, I still think it doesn't deserve to be in core and we should solve that part of the problem by just removing it). |
So #27 would actually close this because it would no longer need to be documented. |
I worked out some more complete examples of validations using the Semigroup and Semiring instances today. They're pretty opinionated, but I think having a more completely worked out example in the repository could help newcomers.
Right now they're in a separate repo here, but if this seems like something the maintainers would like, I can clean them up and put them into a proper PR.
The text was updated successfully, but these errors were encountered: