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
Effectively, DecodableType is aliased to Type if a struct does not have an array field
Problem is: TransportOptionsStruct referenced from the command does not have an array, so Type ends up being aliased to DecodableType - but it contains a field to a struct (TransportTriggerOptionsStruct) which does have an array, an then we get a compiler failure
When deciding whether TransportOptionsStruct should have its DecodableType aliased to Type, we also need to check if its children (such as TransportTriggerOptionsStruct) are also eligible, otherwise it cannot alias
The text was updated successfully, but these errors were encountered:
ZAP templates currently decide how to generate
Type
vsDecodableType
based onstruct_contains_array
However, this only works if the array is a field in the struct; if the array is contained > 1 level (a struct referencing a struct with an array field), the resulting
cluster-objects
generated file is invalidFix @ #1501
Effectively,
DecodableType
is aliased toType
if a struct does not have an array fieldProblem is:
TransportOptionsStruct
referenced from the command does not have an array, soType
ends up being aliased toDecodableType
- but it contains a field to a struct (TransportTriggerOptionsStruct
) which does have an array, an then we get a compiler failureWhen deciding whether
TransportOptionsStruct
should have itsDecodableType
aliased toType
, we also need to check if its children (such asTransportTriggerOptionsStruct
) are also eligible, otherwise it cannot aliasThe text was updated successfully, but these errors were encountered: