Checked for duplicates

No - I haven't checked

Is this a regression?

No - This is a new bug

Version

3.0.1

Describe the bug

The command expansion service incorrectly interprets all Duration-type activity arguments (that is, Duration as a value schema type) as having a value of zero. From a little debugging, it seems like parse is returning a duration of zero when parsing the serialized value, which comes as an integer number of microseconds.

Relevant sequencing server function:

Reproduction

Write a command expansion rule that uses a Duration-type activity parameter and see that the value of the parameter is deserialized for use in the expansion rule as zero.

For example, the below uses GrowBanana and prints out the string value of the duration (which comes back as PT0S).

export default function MyExpansion(props: {
  activityInstance: ActivityType,
  channelDictionary: ChannelDictionary | null
  parameterDictionaries : ParameterDictionary[]
}): ExpansionReturn {
  const { startTime, attributes } = props.activityInstance;
  return [A(startTime.add(attributes.arguments.growingDuration)).SEQ_ECHO(attributes.arguments.growingDuration.toString())];
}

Logs

No response

System Info

Aerie 3.0.1 local

Severity

Moderate