Skip to content

In "Inputs" > "Array Inputs", there should be more emphasis on where inputBinding appears #400

Open
@zoe-translates

Description

@zoe-translates

The `inputBinding` can appear either on the outer array parameter definition
or the inner array element definition, and these produce different behavior when
constructing the command line, as shown above.

This bit wasn't very clear, because it didn't clarify where "as above" specifically referred to, and what sort of "different behavior[s]" were expected.

It's clear that the text meant to direct the user's attention to filesB in the array-inputs.cwl file, where comparison with the other two inputs should lead to an observation about inputBinding on array vs. array elements.

But for one thing, this wasn't made clear. The user should've been given direct instruction about where to look. The code block was a bit far up, and its content a bit complicated with multiple levels of nesting.

In addition, it was difficult to reach a conclusion about "the different effect of inputBinding on array vs. array elements" just by observation alone. filesB differs from the other two inputs not just by the presence of inputBinding for elements (even this may not be clear to a new user). So it would be useful to explain in words the difference of behaviors with or without inputBinding on elements.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions