-
Notifications
You must be signed in to change notification settings - Fork 43
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
Add Fail constraints for instances which don't belong? #49
Comments
Actually, I would prefer to remove the Either that, or we should require that |
I'd agree with removing |
I'd like to further motivate the use of combinators instead of classes. This library is in the realm of parsers, parsing data from foreign data, and I believe parsers normally don't rely on unique type classes. |
Hi guys, Now that person = writeObject
[ "name" .= "chris"
, "age" .= 100
] Is there any current replacement for the above? (I searched Pursuit and couldn't find anything not relating to React that did this) If not, I'd be willing to implement what's needed myself/create another package. Thanks! |
I guess the other option in the above would be to encode just by rewriting as the desired record and the
Although it is a little "risky", as you're not forced to encode all the values involved. |
As mentioned in previous issues, like #30, this library shouldn't include instances for common PS types, instead only instances for JS-native types.
To prevent creation of more issues asking for instances like these, should we add a Fail constraint, as described in paf31/24-days-of-purescript-2016 21. Custom Type Errors? I'd like to add one for Maybe, where the error message instructs to use the Null or Undefined newtype instead.
The text was updated successfully, but these errors were encountered: