eric-skydio

Sorry for jumping into this late, but I can also provide some context from Skydio, where we also have a pretty extensive list (~8) of internal Gazelle plugins, including Python...

Pinging @jayconrod for design feedback, I'm willing to sink some implementation effort into this but want a :+1: first.

No, since SetAttr would automatically handle PlatformStrings and []string by converting them to the new internal mergeable representations. Since those are the only types currently merged, that should cover all...

As a revision, it may make sense to instead perform that fallback at the time of rule merging rather than when `SetAttr` is called, to more closely match existing behavior.

I saw a similar error when Bazel's --output_base flag was set to a path inside my workspace. Upgrading to later rules_go versions did not seem to resolve it.

@fmeum I finally got around to resurrecting this quite-old PR, which adds experimental support for saving and loading the rule index. This is intended to serve as a building block...

The lens that I have found most clear for thinking about this is thinking about how to handle a single rule with multiple actions, some of which depend on the...

> In case3 above, D have two identical actions generating the same file. It worked on master as of Friday. The "output directory name" patch didn't add anything enforce this....

>> For our use case (@torgil can you confirm for yours) I think we can avoid this problem by instead just requiring that all instances of an action that generate...

@torgil > I don't see this replace output directory name transition as the naming do not propagate to dependencies or third party rules if you for instance are using different...