From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

:wave: Hello! Is there a way to add a value to a `SetProperty&lt;&gt;` from a provider that may be `Missing` and not have the entire set conclude it is `Missing`?

I worked around this by an _ugly_ hack:
```  internal val subprojectRootsMap: MapProperty&lt;String, Boolean&gt; = objects.mapProperty&lt;String, Boolean&gt;().empty()
  val subprojectRoots = subprojectRootsMap.asTrueSetProvider()

  private fun MapProperty&lt;String, Boolean&gt;.asTrueSetProvider(): Provider&lt;Set&lt;String&gt;&gt; {
    return objects.setProperty&lt;String&gt;()
        .value(this.map { it.filterValues { v -&gt; v }.keys })
        .apply {
          finalizeValueOnRead()
        }
  }```

<https://github.com/gradle/gradle/issues/18352|https://github.com/gradle/gradle/issues/18352>

Have you considered doing `addAll` with a provider that can never be empty? I.e. your provider that might be empty should map to a singleton set but you can then do `orElse(Set.of())`? Then your set property is never empty due to other providers. I’m going on your initial question, not your workaround.

The `addAll(…)` was adding single elements.  Of which _any_ could be empty. but it turns out if _any_ are empty the entire collection is empty :grimacing:

Yes but if you add non empty provider containing an empty set, it should be fine no?

So each of your elements become singleton sets potentially empty sets, but the provider is never empty

Oh, something like:
`setProperty.addAll(boolProperty.map { setOfNotNull("foo".takeIf { it } })`