On 12/08/2022 09:57, Krzysztof Kozlowski wrote:
On 12/08/2022 01:09, Arınç ÜNAL wrote:
-patternProperties:
- "^(ethernet-)?ports$":
- type: object
Actually four patches...
I don't find this change explained in commit msg. What is more, it looks
incorrect. All properties and patternProperties should be explained in
top-level part.
Defining such properties (with big piece of YAML) in each if:then: is no
readable.
I can't figure out another way. I need to require certain properties for
a compatible string AND certain enum/const for certain properties which
are inside patternProperties for "^(ethernet-)?port@[0-9]+$" by reading
the compatible string.
requiring properties is not equal to defining them and nothing stops you
from defining all properties top-level and requiring them in
allOf:if:then:patternProperties.
If I put allOf:if:then under patternProperties, I can't do the latter.
You can.
Other than readability to human eyes, binding check works as intended,
in case there's no other way to do it.
I don't see the problem in doing it and readability is one of main
factors of code admission to Linux kernel.
One more thought - if your schema around allOf:if:then grows too much,
it is actually a sign that it might benefit from splitting. Either into
two separate schemas or into common+two separate.
Best regards,
Krzysztof