[chore] Add rows property to field schema

[kgrhartlage]

Description

We already added support for this in the server repo (PR).

I also tried to narrow down the supported combinations of different schema settings.

[ignatiusreza]

why is it applied as a negative logic?? how would it looks like on the rendered documentation schema?

[kgrhartlage]

How else can we make this work? This, for example, is what we do want to support:

type:
  const: boolean
ui:widget:
  type: string
  enum: ['checkbox','switch']

If we nest this in oneOf we also need to add a case for all the possible valid combinations for a boolean field, which cannot include in this combination of settings though, must have ui:widget as optional, and must support the other custom properties and the Draft 07 ones. 🤔

If we nest this in allOf... well then I don't see how we can exclude anything

[kgrhartlage]

I refactored it, we are now left with just one not case. This will require changes on the schema docs, since we have not used the if and then keywords before.

[kgrhartlage]

This is where we would add a description to express the constraint the schema implements. I would likely lean to only adding it to if and not split it up between if and then, since they both belong together anyway.

[ignatiusreza]

This already looks much better 👍

Interesting though that you put the type inside then and the configuration inside if.. I would think that it make more sense to do it the other way around, but not sure if it works, e.g.

if:
  type: string
then:
  ui:widget:
    enum: ['text', 'textarea']

[kgrhartlage]

Yes, we can flip this