One InputTracker per build

[davidmorgan]

For #3811, review and merge #3876 first.

Unify test and non-test input tracking by having one input tracker per build, using the current primary input ID as a key.

[github-actions]

PR Health

Changelog Entry ❗

Package	Changed Files
package:build_resolvers	build_resolvers/lib/src/analysis_driver_model.dart

Changes to files need to be accounted for in their respective changelogs.

This check can be disabled by tagging the PR with skip-changelog-check.

[jakemac53]

I don't believe this is safe to do this way, if I understand it correctly. The keys in this map would need to be the output ids, instead of the primary input id.

The reason being that an asset can be a primary input to any number of different actions.

I would try adding a test where there are two builders with the same input extension, but which read different additional files during the build, and make sure they don't pick up each other's dependencies.

[davidmorgan]

Thanks.

That was my suspicion too ... I'll look at adding test coverage as you suggest.

It might make sense to just number the build actions incrementally :)

[jakemac53]

There are numbered phases, and each phase only applies a single builder, so this would be safe if they were per phase and not per entire build.

[jakemac53]

Another consideration here is this will retain these sets much longer in memory (for an entire build), instead of releasing them as soon as a build step completes.

Doing this per phase will have the same problem because phases don't actually execute sequentially.