You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I received some complaints from a user that there's some very confusing behavior surrounding returned providers from a Skylark rule implementation.
Namely, if a rule implementation returns multiple providers of the same type, i.e.
The current behavior is obviously buggy. We should throw an error instead.
Since it's a breaking change, we should use a --incompatible flag. This will allow users to check their code and fix it, before we make it a hard error in Bazel.
Indeed. I must have lost track of this particular issue, as I filed a duplicate #5902 and tracked this fix there. Oops!
I want to leave that bug open to track the migration to the new flag. So perhaps we can close this?
I received some complaints from a user that there's some very confusing behavior surrounding returned providers from a Skylark rule implementation.
Namely, if a rule implementation returns multiple providers of the same type, i.e.
that the last such provider is the only one propagated, and each other provider is silently dropped.
This reportedly led to about a day of lost work for this user, so this is likely a pattern we should error against.
The text was updated successfully, but these errors were encountered: