ESLint Inferred Task Options

[patrickhousley]

It seems like inferred tasks are not built on top of their non-inferred counterpart or does not make use it's executor. For example, for eslint, if you use an inferred task, it runs eslint binary directly instead of making use of the eslint executor. This means some of the options like --print-config does not work for inferred tasks. And I don't think this is the first time I have seen this. I guess the question here, or maybe the feature ask, is that inferred tasks build or make use of the already built out executors. Was there a reason that was not done?