How to handle null values? (invalid type: null (expected string))

[ms88privat]

Hello,

my specified form schema matches the properties of a model which is coming from a backend server.
A lot of the properties are not necessarily required and have therefore a 'null value'.

For example:
model = {name: null, id: 32}.
So my schema looks like this:
schema = {type: 'object', properties: {name: {type: 'string'}. id: {type: 'integer'}.

The problem is, that i can not validate the form because of null != string.

I really do not want to parse all of the models and properties beforehand....
I think it is related to #146 but there is no solution?

Thank you very much

[Dervisevic]

In #146 they do mention the workaround that would allow it, but you would lose the required validation. You mentioned they are not necessarily required so maybe this would work for you.

[ms88privat]

setting type: ['null', 'string] does not work. It will not render the input field.

[Dervisevic]

Ah, i see. Then its the same issue. I'll tag it as an enhancement.

On Mon, Jan 5, 2015 at 12:40 AM, Denis Dervisevic echuu88@gmail.com
wrote:

On Mon, Jan 5, 2015 at 12:13 AM, ms88privat notifications@github.com
wrote:

setting type: ['null', 'string] does not work. It will not render the input field.

Reply to this email directly or view it on GitHub:
#193 (comment)

[Dervisevic]

Duplicates #146

[fiddur]

As stated in #146 this is fixable with multiple types, but if you have control over the backend, I would suggest skipping the field with null value, so that model is just { "id": 32 } when there is no name. That gives a cleaner schema, using "required" to say what is required and not having to have multiple types on all non-required fields.

[ms88privat]

Thanks for the reply but I do not have control over the backend. The field is not visible if I use the array syntax title: ['null','string']. Am I doing something wrong or is there a misunderstanding? Thank you.

[davidlgj]

I've marked #146 as a bug, it shouldn't break at least. Please move any further comments over on that issue.