Hi,

I would be also interested in yaml inputs of actions, but your solution isn’t better than my current workaround

This would be great if it would work

- uses: ChristopherHX/conditional@b4a9649204f81002ec9a4ef7d4bf7d6b2ab7fa55
  with:
    if: ${{steps.cacheaction.outputs.cache-hit != 'true'}}
    step:
      uses: actions/setup-node@v2
      with:
        node-version: ${{inputs.nodever}}

My current workaround is:

- uses: ChristopherHX/conditional@b4a9649204f81002ec9a4ef7d4bf7d6b2ab7fa55
  with:
    if: ${{steps.cacheaction.outputs.cache-hit != 'true'}}
    step: |
      uses: actions/setup-node@v2
      with:
        node-version: ${{inputs.nodever}}

I get trouble once ${{inputs.nodever}} contains newlines or need yaml escaping, which would be no problem with object inputs of my composite action ( or reusable workflows )

BTW actions runner currently allows unknown inputs of actions, this means you can pass arbitary yaml inputs in the input dictionary of with and get every one as INPUT_NAME_OF_YOUR_INPUT environment variable or in the inputs context of composite actions, the only drawback is you get a warning about such undeclared inputs in your log.