Behaviour when both workflow's step and its tool define a default value for an input

[undu]

In the case where both a workflow defines a default value and the tool in the step also defines one, cwltool picks the default value in the tool.

I haven't seen this behaviour been defined anywhere, and I would expect the values in the tool to be overridden since this is the only way I've seen to 'hardcode' values in workflows, but I don't know if that makes sense for everybody.

For example:
workflow.cwl

[...]
steps:
  step:
    run: tool.cwl
    in:
      parameter:
        default: 'workflow'
[...]

[...]
baseCommand: echo
inputs:
  parameter:
    type: string
    default: tool

This would print tool, I'd expect it to print workflow.

Is this something expected? I can produce conformity tests and tests for cwltool if necessary.

[esanzgar]

I don't see this issue in version 1.0.20170928192020 of the cwtool

[undu]

I see this behaviour with cwltool==1.0.20171017195544.
Hopefully I can get around producing some reproducibility tests.

[tetron]

Should be fixed now.