Add support for "allOf": [ <constraints> ]

[loiclefevre]

Today, we can't use allOf for defining check constraints:

	"properties": {
		"NAME": {
			"type": "string",
			"extendedType": "string",
			"maxLength": 100,
			"allOf": [
				{
					"minLength": 3
				}
			],
			"minLength": "3",
			"description": "Product name (max length: 100)",
			"title": "Name"
		},

It would be great if it was supported.

[sandrina-p]

Hi @loiclefevre, that's true, it's a bug / missing feature. We are planning a revamp to JSF to allow using allOf inside fields.

Created internal issue

[loiclefevre]

Thanks @sandrina-p, that's good to know!!!

[sandrina-p]

We don't know exactly when, but probably by the beginning of the year :)

[js-ta]

I'm joining in here because this is a problem we're having right now.
We work a lot with $ref to avoid duplicate definitions and frequently use things like

{
	"$schema": "http://json-schema.org/draft-07/schema#",
	"allOf": [
		{
			"$ref": "file:///config-base.json"
		},
		{
			"type": "object",
			"properties": {
				"numb": {
					"$ref": "file:///def.json#/definitions/input-numb",
					"title": "__('Input number')"
				}
			},
			"required": [
				"numb"
			]
		}
	]
}

Unfortunately, this is not working at the moment.
Is this something you want to implement soon or should we find another solution for this issue for the time being?

[sandrina-p]

Hi @js-ta. We don't plan to implement it ourselves soon, but contributions are welcome! Would you like to give it a shot in our source-code? We can then review and release it :)

[js-ta]

Unfortunately I don't have enough time at the moment.
We have to live with a temporary solution for now.
I'll do my best to deliver a working patch as soon as I can.

[sandrina-p]

No problem @js-ta! the allOf got fixed in v1 and we are deprecating v0, so closing this. Here's the migration guide

[loiclefevre]

🤩