Skip to content
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

Introduce strict mode for native converters #221

Closed
tefra opened this issue Jul 28, 2020 · 0 comments
Closed

Introduce strict mode for native converters #221

tefra opened this issue Jul 28, 2020 · 0 comments

Comments

@tefra
Copy link
Owner

tefra commented Jul 28, 2020

The converter to python types protects against Value errors, although this is the preferred behavior, this is hiding a lot of smaller issues. Introduce a strict mode, which will be disabled by default and solve all those inconsistencies.

Example
MaxInclusive.value restriction facet should be string not float, and needs to converted later by using the final field types.

@tefra tefra closed this as completed in 179cd08 Jul 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant