[bug] AffectedPassInputs does not work when inputs are missing

[dudicoco]

Describe the bug

When configuring a task with affectedPassInputs: true, if the inputs are missing the dir will be passed as an arg to the command.

Steps to reproduce

Define the following task:

  format:
    command: echo
    inputs:
    - '*.sh'
    options:
      affectedFiles: true
      affectedPassInputs: true

If no sh files exist the task will echo ..

Expected behavior

If we pass an empty string the formatter/linter might fail.
Perhaps the task command should be skipped in this case?

[milesj]

@dudicoco The task can't be skipped this late into the process.

If we have no files, we just default to . since the command typically expects something.

[dudicoco]

The problem is that . doesn't take into account exclusions.
For example if I have the following inputs:

inputs:
- '*.sh'
- '!foo.sh'

[milesj]

I'm not sure what the solution is here because some commands error if no argument is provided (eslint, etc), so we pass the . for those use cases. But it doesn't work for other commands...