Generator ignores properties if they are not defined in metadata.py
When new leaves for actions and conditions are generated, the generator ignores undefined properties.
Example
OpenSCENARIO 1.2.0 extended TrafficSwarmAction w.r.t to 1.1.1:
- Property
initialSpeedRange
created - Property
directionOfTravelDistribution
created
Actual Behavior
- IF the properties underlying type is not primitive (e.g. double)
- AND there is no conversion rule defined in
metadata.py
- RESULT the generator ignores (skips) the property
Expected Behavior
- The base class of TrafficSwarmAction is extended, even if the underlying types are not primitives (e.g. double)
- Thereby the generator follows the following pattern (e.g. for
initialSpeedRange
with non-primitive typeRange
):
Converter:ConvertScenarioRange(trafficSwarmAction->GetInitialSpeedRange)
Source:engine/gen/Conversion/OscToMantle/ConvertScenarioRange.h
(Stub)
Member:OPENSCENARIO::Range initialSpeedRange;