We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
After upgrading from v5.0.0 to v5.1.0 I'm experiencing an issue with this schema definition:
const definition = { "userId": { "type": String, "required": true }, "userIdType": { "type": String, "required": true, "enum": [ "UserId", "GroupId", "UserEmail" ] } }
When validating a valid object I get "Typecasting failed: No typecaster defined for Object.".
In v5.1.0 when I inspect the created schema object I see this under schema.props (notice the "_type: Object" in "userId"):
schema.props
{ "userId": { _type: Object, /// rest omitted... }, "userId.required": { _type: null, /// rest omitted... } "userId.type": { _type: String, /// rest omitted... }, "userIdType": { _type: String, /// rest omitted... } }
In v5.0.0 when I inspect the created schema object I see this under schema.props (notice the "_type: null" in "userId"):
{ "userId": { _type: null, /// rest omitted... }, "userId.required": { _type: null, /// rest omitted... } "userId.type": { _type: String, /// rest omitted... }, "userIdType": { _type: String, /// rest omitted... } }
Thanks
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi,
After upgrading from v5.0.0 to v5.1.0 I'm experiencing an issue with this schema definition:
When validating a valid object I get "Typecasting failed: No typecaster defined for Object.".
In v5.1.0 when I inspect the created schema object I see this under
schema.props
(notice the "_type: Object" in "userId"):In v5.0.0 when I inspect the created schema object I see this under
schema.props
(notice the "_type: null" in "userId"):Thanks
The text was updated successfully, but these errors were encountered: