Nullable Types

[neotek]

Hi
I really like your component. But I have problems with nullable types.
They are just ignored.
My Schema looks as follows, any only Start and Limit are rendered:

Is there a way to support these?

Thanks

[davidlgj]

I guess we have made the assumption that "type" in the schema always is a
string. We can't support setting null right now (see answer below), but
at least you should be allowed to use them. So it's a bug.

The problem is that an input field doesn't have a "null" state. Today
erasing a field you typed in removes that value (ie. undefined) so it can
trigger "required" validation. If it would instead be a "null" that would
basically mean that you never can erase a field and hence never trigger
"required". So to support nullable we would need to supplement the input
with some other form of control so you can explicitly set it to 'null' (or
vice-verse change it so an empty input means 'null' but you can also
explicitly set it to "empty")

/david

[mike-marcacci]

Hey @neotek, this might help... try setting your schema like this:

{
    "type": "object",
    "properties": {
        ...
        "query": {
            "type": ["null", "string"],
            "default": null
        }
        ...
    }
}

As @davidlgj mentioned, you sacrifice the "required" aspect, but I suspect this is what you're hoping to achieve.

[johnwebbcole]

@mike-marcacci this solution doesn't work on the example page... the form element looses it's title and apparently it's data binding.

[Dervisevic]

We should be able to handle this in some fashion right?

[fiddur]

If type is an array of two types in the schema, one of which is "null", the form should be generated based on the other one. It's a special case, but might be more common than other combination of types. We used that here before changing praxis to remove the field instead of setting it to null.

[davidlgj]

I'm marking this as a bug. I don't think we should support some kind of extra field for the user to actually set null, but we shouldn't fail if "type" property in a schema is a list with null in it, as @fiddur says we should handle it by taking the non null value as the default.