-
Notifications
You must be signed in to change notification settings - Fork 217
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
Extending schema to change properties of existing keys #219
Comments
Hey @mprager Thanks for pointing out the issue. This looks like a bug in voluptuous. Are you interested in submitting a PR for fixing this ? I can point you to the place where you need to investigate this issue. Thanks. |
Hey sure thing. I have some changes I made locally tot he extend function in the Schema Mike On Fri, Sep 30, 2016 at 1:18 AM, Tushar Makkar [email protected]
|
Closed via 99fb7bd |
Currently modifying key types in an existing schema duplicates the keys and causes all objects to fail validation. Consider this example:
The s2 object now cannot pass validation for any object, since all 'a' keys will be considered for the optional key and the required key appears absent.
The text was updated successfully, but these errors were encountered: