Linting only for changed files

[anckaert1998]

Dear

When we currently perform linting (via affected:lint) this lints all the files in all the affected libraries, but I don't see the point in this.
When a file has not been changed there is no use in lint that file because it can not fail.
So I am wondering what the reasoning behind it is or if I'm missing some information

[ahernd2]

We have a similar scenario. We are using sonar analysis on each microfrontend. This is particularly annoying because when a developer changes a file that affects lots of projects, sonar analysis runs for each affected one.

Sonar analysis is very slow and cannot be parallelized like lint can. Additionally it is wasteful as running the analysis against the affected projects provides no advantage. Only the project where the file was changed is the only project that should be scanned.

It would be good to provide a way to tell nx I only want the affected projects that have a physical file change for a particular task.