You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 16, 2021. It is now read-only.
I'm using a backend validator that uses implications. I'd like to transform the AST that it generates into tcomb types and perform validation on the frontend before uploading the files to the server.
This is essentially checking that the optional key bar is filled if it exists in the input. But implication can also be used for password confirmation and other higher order rules.
Is there a way to implement implication to support such use cases in tcomb or one of its sister projects like io-ts?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm using a backend validator that uses implications. I'd like to transform the AST that it generates into tcomb types and perform validation on the frontend before uploading the files to the server.
A simple example of this is the following.
This is essentially checking that the optional key
bar
is filled if it exists in the input. But implication can also be used for password confirmation and other higher order rules.Is there a way to implement implication to support such use cases in tcomb or one of its sister projects like io-ts?
The text was updated successfully, but these errors were encountered: