Closed iffa closed 1 year ago
got a fix just seeing if I can get a review on it
I think this is still an issue on the latest version.
Something interesting: It happens when my field type is wrapped in createUniqueFieldSchema
Something interesting: It happens when my field type is wrapped in
createUniqueFieldSchema
Ah interesting, maybe we are failing to unwrap properly when branded (which createUniqueSchema uses under the hood). Lets create a new issue for that since it's a different problem technically. (Feel free to make a PR with a failing "type" test as well. See the tests in the PR that closed this issue for reference)
Experiencing the same issue with createUniqueFieldSchema
, props and optional fields
Prop types seems to break when optional/nullable/nullish are not in the correct order. See the reprodcution below
TL;DR:
optional().nullable()
worksnullable().optional()
does notnullish()
does not, as it is equivalent tonullable().optional()