-
Notifications
You must be signed in to change notification settings - Fork 145
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
Allow None value for strings #274
Comments
jenstroeger
changed the title
Allow
Allow None value for strings
Oct 18, 2016
None
value for strings
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My question seems somewhat similar to other
None
related problems, e.g. #140, #186, #204.It seems to me that deserializing a
None
string should yield the same, instead ofcolander.Invalid: {'name': 'Required'}
which is misleading becausename
does indeed exist:A proposed solution can be found on Stackoverflow but it seems more like a workaround for this issue than a proper solution.
The text was updated successfully, but these errors were encountered: