-
Notifications
You must be signed in to change notification settings - Fork 935
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
yup.ref(...).transform is not a function #423
Comments
yes that's right, a
|
That's perfect! Thanks :) |
It looks like |
This can be closed. |
For future readers. Right now reference documentation is wrong and second argument for
|
I HAVE NO IDEA WHEN I ADDED THAT AND DON'T REMEMBER WHY :P |
Well, you might have the same need as the opener of this issue. A valid need. Unlike |
Yeah there a few crufty things originally added I think to match joi, but they aren't used and we aren't really trying to match joi anymore. I'm glad for the second pair of eyes on the old code 👍 |
Trying to create a computed field that depends on another one. Something like:
Is
.ref
not designed for something like this? If not, is there anything else I could try?I would like to keep this logic on a schema level if possible.
Thanks!
The text was updated successfully, but these errors were encountered: