Use a Configuration to model the additional dependencies of each run #81
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use a Configuration to model the additional dependencies of each run, since configurations seem to be better at tracking task dependencies.
This does change syntax insofar as adding configurations will now look different.
It'll just be
instead of
This is due to extending the internal configuration from the given configuration, and not converting the configuration into a
Dependency
first.What could be discussed: Should the configuration be transitive by default? I think it should be, since that's how the normal
runtime
configuration would behave.