-
Notifications
You must be signed in to change notification settings - Fork 12
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
forms.SchemaField.to_python(): check if value already has a target type #45
Conversation
Hi @alexey-sveshnikov, thanks for bringing this up! I could imagine how this can be a problem with the form, but this particular case is a bit elusive for me -- I haven't had any setup with Another point that I want to put into consideration, is that it's not always the case that validation schema is |
@alexey-sveshnikov based on the assumptions above, I prepared this PR to your base branch. These changes are published to PyPI under 0.3.2b1 pre-release -- I would be glad if you can try them against your configuration to test if that would work... |
b8c1192
to
24e37c5
Compare
Try to parse non-string python objects into form field schema
Thank you. I've added
I actually have no stack traces. The exception I got was ValidationError and it has been handled like normal validation error ( |
0.3.2b1 works fine with django-constance! |
Great, thank you! I'll prepare the next patch for PyPI. |
ffa3c6d
to
2d890be
Compare
Hi Savva!
Thank you for the great library! I enjoy using it a lot.
This is a small fix to a problem I encountered after upgrading to v2. I think the patch is pretty much self-explanatory, except for the case which is triggered the bug. It was in a django-constance custom fields config: