- πΊπΈUnited States effulgentsia
@catch, I, and others met a few days ago to discuss option #3 in the proposed resolution. I included that in an XB refactoring proposal in π Refactor the XB field type to be multi-valued, to de-jsonify the tree, and to reference the field_union type of the prop values Active .
- π«π·France pdureau Paris
Hello Panagiotis,
This would be my (non tested) proposal for slots. Remove the
-
from/"$defs"/slotDefinition/patternProperties/"^[a-zA-Z0-9_-]$"
. So:/"$defs"/slotDefinition/patternProperties/"^[a-zA-Z0-9_]$"
Unfortunately, I don't think it is possible to enforce it for props because we are edelegating the schema to
http://json-schema.org/draft-04/schema#
- π¬π·Greece vensires
@pdureau, I am not so familiar with the *.schema.json syntax etc but we currently have the following:
"props": { "$ref": "http://json-schema.org/draft-04/schema#" }, "slots": { "$ref": "#/$defs/slotDefinition" },
So, where could these constraints be added in the schema.json file?
- First commit to issue fork.
Automatically closed - issue fixed for 2 weeks with no activity.
Automatically closed - issue fixed for 2 weeks with no activity.
Automatically closed - issue fixed for 2 weeks with no activity.
- πΊπΈUnited States smustgrave
So is consensus to use #3? So we can update the remaining tasks so it's clear what's being proposed here.
Test failures appeared to be random.
Applied a super nitpicky return type as a new function.
Tagging for tests - First commit to issue fork.