DGP: Rename conflicting 'maybeCreate' helper function. #3763
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.
DGPv1 and v2 both have a similar utility function:
fun <T> NamedDomainObjectContainer<T>.maybeCreate
. However, their behaviour is slightly different.v1: find the item by name, OR create the item and configure it.
v2: maybe create the item, AND exist the new/existing item.
The only usage of v1's version was in the
gradleConfiguration.kt
, so this PR moves it and renames it tofindOrCreate()
, to avoid confusion.