Which future handlers does this apply to? Optional. Specify any number of positive integers. The number represents an index ahead of the current handler. For example, 1 is the next handler and 2 is the handler after next. You can specify  to apply to the current handler, however in that case you must specify "value", and not "from", since the arguments will be applied before the response object from the handler is available. If omitted, the mapping applies to the next handler (equivalent to a value of  for this field)
Dot notation property e.g. files.filename to copy from the command response's data field (set via response.data.setObj) of this chained handler to a future chained handler. If mapFromArguments is specified, the mapping will be from the overall command's arguments (the command comprised of these chained handlers and mappings).
Mutually exclusive with 'value'. The dot notation field is retrieved with the dataobject-parser package.
If you specify this, values will be copied from the overall command's arguments instead of the command response of the current handler. Has no meaning if paired with 'value'
Is this mapping optional? Unless this is true, an error will be thrown if "from" is specified and the specified field is not found on the command response.
The name of an argument e.g. "filename" that will be inserted into the "arguments" field of the handler parameters for the future chained handler. Required.
Hard-code a value to pass to the "to" argument field. Mutually exclusive with "from". Note: the value should be serializable, since command definitions should be able to be fully represented in JSON. Values that are not preserved when doing JSON.parse(JSON.stringify(value)) will cause an error.
Generated using TypeDoc
Interface describing constructing command line arguments for chained handlers.