'coerce' still ignores 'nullable': True

#269 was fixed, but only for integer:

>>> v = cerberus.Validator({'foo': {'coerce': int, 'nullable': True, 'type': 'integer'}})
>>> v.normalized({'foo': None})
{'foo': None}

Just replace integer to string:

>>> v = cerberus.Validator({'foo': {'coerce': str, 'nullable': True, 'type': 'string'}})
>>> v.normalized({'foo': None})

Expected behavior: {'foo': None}

Actual behavior: {'foo': 'None'}

So I still have to use a workaround 'coerce': lambda x: str(x) if x is not None else None

But now I’m not sure if it’s a bug or a feature (duplicate of #142?). If this is a feature, please describe this behavior in the documentation

[dkellner]

@funkyfuture You’re delegating to Vietnam here, so much for the heat 😉. I will take a look at it and get back to you until wednesday.

[funkyfuture]

not sure which of the previously behaviours you mean. 😉 anyway, no, for now we shouldn’t change any of that. just fix your tests (and possibly code to comply w/ them).