You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
or the slightly wider solution
"Multiple references to a list object appends to that list" (sounds like a big change to the language)
asd: [
"a",
]
if_cond {
asd: [
"s",
"d",
]
}
The latter would enable better separation of objects across files, but it seems like a thing that may be impossible to add without enabling/messing with the scope etc. of the internals.
I originally thought this solution was there in the language, it follows the thought of allowing reference of fields disjointly:
a: b: stringa: c: string
but I do see that it's harder when you are referencing an array/list (opposed to a field -- in essence you are referencing the same field).
These help avoid having to use indirection, and list-flattening
@MikkelHJuul thanks for raising this. Please see #165 (comment); there are plans for addressing this in the query extension proposal. Hence I'll mark this issue as closed, but please shout if you think I've missed something.
@MikkelHJuul thanks for raising this. Please see #165 (comment); there are plans for addressing this in the query extension proposal. Hence I'll mark this issue as closed, but please shout if you think I've missed something.
Great, sorry for missing it, I searched for conditional and found nothing. It looks like an implementation of a "spread" operator, very neat and that would certainly fix the issue
When working with lists and conditional elements, when trying to add multiple conditional elements one has to wrap all of these with the condition.
This is the only valid syntax:
There are two possible solutions:
allow multiple objects in the conditional
or the slightly wider solution
"Multiple references to a list object appends to that list" (sounds like a big change to the language)
The latter would enable better separation of objects across files, but it seems like a thing that may be impossible to add without enabling/messing with the scope etc. of the internals.
I originally thought this solution was there in the language, it follows the thought of allowing reference of fields disjointly:
but I do see that it's harder when you are referencing an array/list (opposed to a field -- in essence you are referencing the same field).
These help avoid having to use indirection, and list-flattening
** Additional context **
I wrongfully tried it myself, and had to fix:
MikkelHJuul/ODIM-H5-Validator@1e1aaa1
The text was updated successfully, but these errors were encountered: