Nx true affected

[omer-za]

Hey nx team.
I would like to open a discussion about the nx affected algorithm.
Today when asking for affected project I get a long list of projects even if they are not really affected by change cause of a dummy check of project dependency tree while most of my projects doesn't really have a direct usage of the affected function.

It's making all our CI CD pipeline to be executed for no real reason because of that and really slows us down.

There's an open source project that tried to resolve this issue that you can try to get some insights on how to do it internally. https://github.com/lemonade-hq/traf

I think it is the most critical algorithm for most of the end users in order to save computing time 🙏

[jaysoo]

Thanks @omer-za for opening this discussion. What you're proposing is interesting, and I will discuss this with the team to see if we a want to add support for this. I think it will need to be a new plugin API that hooks into the affected logic. So users can run:

nx add @acme/granular-nx-affected

And that will register the plugin.

I'm not sure if want to enable this behavior by default unless we can guarantee correctness. But having the ability extend affected, even beyond TS, makes some sense.

[omer-za]

I'm find with having this as a opt in capability, I do think that once we can guarantee correctness and having the right tests in place it can become the default behaviour