Open philtweir opened 2 months ago
1-26:
Can pass incorrect types in workflow steps and they end up being rendered without warning. For example,
@task() def increment(num: int) -> int: return num + 1 result = increment(num="Hello World") workflow = run(result) cwl = render(workflow) yaml.dump(cwl, sys.stdout, indent=2)
renders
class: Workflow cwlVersion: 1.2 inputs: {} outputs: out: label: out outputSource: increment-87042095119bafeb4cbfea12f9986bb1/out type: int steps: increment-87042095119bafeb4cbfea12f9986bb1: in: num: default: Hello World out: - out run: increment
1-27: The same issue, but when typing bugs are present in the task code, for example:
@task() def increment(num: int) -> int: return "Phil loves mac" result = increment(num=2) workflow = run(result) cwl = render(workflow) yaml.dump(cwl, sys.stdout, indent=2)
@philtweir We should discuss this and decide if it is in scope of the initial feature request. If not, we should clarify this behavior in the documentation.
This feature is pending strategic alignment, and thus not targeted for release/0.9.1 . FYI: @KamenDimitrov97 @philtweir
1-26:
Can pass incorrect types in workflow steps and they end up being rendered without warning. For example,
renders
1-27: The same issue, but when typing bugs are present in the task code, for example:
@philtweir We should discuss this and decide if it is in scope of the initial feature request. If not, we should clarify this behavior in the documentation.