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
VSS Syntax support the use of types/structs, it is however not used in standard VSS catalog yet
For JSON VSS-tools two supports two variants when using struct, if the -ot argument is used the type/struct information will end up in a separate JSON file, otherwise in the same file
KUKSA Databroker does not support structs, it does not support having a type JSON as (second) input and the Proto files does not support sending struct data.
In the referenced comment above the user gets Error: ParseError
The goal of this issue is not to introduce struct support, that is a topic for later, if ever. Instead it intend to make it more visible that we do not support structs. Proposed measures:
Make sure that we in documentation clearly state what part of VSS (syntax) that we do not support.
Make sure that we give a reasonable error message if using structs, both for the variant when the JSON file actually contain struct information and for the case when no struct input is given (i.e. only signal file, no struct/type file) or only struct input (i.e. no signal file)
Possibly something like: "Databroker does not support VSS Structs"
There is a possibility that VSS_project may add signals using structs in a later release. We could consider changing Databroker behavior so it just ignores signals signals using struct data (but give warning) rather than exit. That way we could provide partial support for VSS-models including struct data.
The text was updated successfully, but these errors were encountered:
This issue is created based on COVESA/vss-tools#241 (comment)
In short:
-ot
argument is used the type/struct information will end up in a separate JSON file, otherwise in the same fileIn the referenced comment above the user gets
Error: ParseError
The goal of this issue is not to introduce struct support, that is a topic for later, if ever. Instead it intend to make it more visible that we do not support structs. Proposed measures:
Possibly something like: "Databroker does not support VSS Structs"
There is a possibility that VSS_project may add signals using structs in a later release. We could consider changing Databroker behavior so it just ignores signals signals using struct data (but give warning) rather than exit. That way we could provide partial support for VSS-models including struct data.
The text was updated successfully, but these errors were encountered: