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
in the parameter declaraions for some scenarios lane IDs are defined. In their usage they need to be strings, but this doesn't work for constraints (e.g. 3 < LaneId < 5). Therefore the parameters should be defined as integer, so they can be used for checking constraints and within expressions. They would need to be implicitly converted to a string when they are used as string attribute for a laneID
The text was updated successfully, but these errors were encountered:
Isn't the lane ID defined as a String in the specification?
Another option to achieve validation of the constraint could be to have a series of Constraint Groups. For example, for allowing only lane IDs between -3 and -5:
in the parameter declaraions for some scenarios lane IDs are defined. In their usage they need to be strings, but this doesn't work for constraints (e.g. 3 < LaneId < 5). Therefore the parameters should be defined as integer, so they can be used for checking constraints and within expressions. They would need to be implicitly converted to a string when they are used as string attribute for a laneID
The text was updated successfully, but these errors were encountered: