Address Issue #258: Configuration predicate to control dependency graph creation #259
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.
Adds a new configuration option to allow the consumer to provision of a
Predicate<Configuration>
instance to customize whatConfiguration
instances should be considered when building the dependency graph.For your consideration, adding something like this would be very helpful for us. Appreciate the work y'all have done thus far.
Note that the choice of
Property<Predicate<Configuration>>
was used because:afterEvaluate
issuesConfiguration
instead of just its name