In my project, we're using bazel_skylib_gazelle_plugin to generate bzl_library targets for producing stardoc documentation. A few of our .bzl files wrap functionality from rules_scala. When building these bzl_library, we get errors:
ERROR: no such target '@@rules_scala+//scala:scala': target 'scala' not declared in package 'scala' defined by /Users/rafiksalama/Library/Caches/bazel/_bazel_rafiksalama/c4824d8210ee1e28e2bc4f237bdd53e8/external/rules_scala+/scala/BUILD
This can be fixed by adding bzl_library targets for the (public) bzl files. I believe this is standard practice for public rulesets and can also be used to extract and publish documentation on the BCR website.
I can send a PR to manually add the missing targets, however, they would be in danger of going out-of-sync. Would you also be okay with accepting a dev dependency on bazel_skylib_gazelle_plugin and wiring up CI checks to ensure they're in-sync?
In my project, we're using
bazel_skylib_gazelle_pluginto generatebzl_librarytargets for producing stardoc documentation. A few of our .bzl files wrap functionality from rules_scala. When building thesebzl_library, we get errors:This can be fixed by adding
bzl_librarytargets for the (public) bzl files. I believe this is standard practice for public rulesets and can also be used to extract and publish documentation on the BCR website.I can send a PR to manually add the missing targets, however, they would be in danger of going out-of-sync. Would you also be okay with accepting a dev dependency on
bazel_skylib_gazelle_pluginand wiring up CI checks to ensure they're in-sync?