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
When we define a workflow where one of the tasks will take a list as input. When we use a Promise with an attribute path from another task or sub-workflow as one element of the input, It will throw an error. For instance:
Here, in2 of the input task_2 will be a list of Promise, and promise::_translate_inputs_to_literals will transform it to Literal (LiteralCollection in this case). However, it didn't try to resolve the attribute path of the Promises inside the list. Therefore, this error is received:
This is just an example of a List of Promises. There should be a similar error with Dictionary and Tuple (Tuple is currently under development).
Expected behavior
It should be supported.
Additional context to reproduce
No response
Screenshots
No response
Are you sure this issue hasn't been raised already?
Yes
Have you read the Code of Conduct?
Yes
The text was updated successfully, but these errors were encountered:
Describe the bug
When we define a workflow where one of the tasks will take a list as input. When we use a Promise with an attribute path from another task or sub-workflow as one element of the input, It will throw an error. For instance:
Here,
in2
of the inputtask_2
will be a list of Promise, and promise::_translate_inputs_to_literals will transform it to Literal (LiteralCollection
in this case). However, it didn't try to resolve the attribute path of the Promises inside the list. Therefore, this error is received:This is just an example of a List of Promises. There should be a similar error with Dictionary and Tuple (Tuple is currently under development).
Expected behavior
It should be supported.
Additional context to reproduce
No response
Screenshots
No response
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: