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
The way that I currently work around this is to have wrapper rules that take a base dep, and just return this dep's providers and applies a transition. This works (for the most part), but it's a source of confusion and frustration for users. Is this the best we can do for now?
The text was updated successfully, but these errors were encountered:
What you described seems like the best approach right now. But it's not the case that there are no plans to support per-target transitions in buck2, so there may be better ways to do this in the future.
Actually, I haven't played with them yet, but doesn't the brand new incoming transition API implement per-target transitions now?
In the meantime, I've solved my actual problem by switching to config modifiers (and thus not requiring the transitions to begin with), but I'll leave the issue open for now, as it is still generally relevant.
https://buck2.build/docs/rule_authors/configuration_transitions/#per-target-transition states that there are no plans to add per-target transitions to Buck2.
The way that I currently work around this is to have wrapper rules that take a base dep, and just return this dep's providers and applies a transition. This works (for the most part), but it's a source of confusion and frustration for users. Is this the best we can do for now?
The text was updated successfully, but these errors were encountered: