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
Whenever I start using a new Starlark rule, the first step is to load() it in my BUILD file. Therefore it would be handy if the Stardoc output for each rule showed an appropriate load() statement that I could directly copy-paste. That way, users don't have to manually tweak the path to the .bzl file, change the final slash to a colon, etc., which is pure avoidable tedium.
The text was updated successfully, but these errors were encountered:
That sounds like a nice feature. It might not be applicable in all environments since the repo might be imported by a different non-standard name in the user's WORKSPACE file, but that use is comparatively rare.
Whenever I start using a new Starlark rule, the first step is to
load()
it in my BUILD file. Therefore it would be handy if the Stardoc output for each rule showed an appropriateload()
statement that I could directly copy-paste. That way, users don't have to manually tweak the path to the.bzl
file, change the final slash to a colon, etc., which is pure avoidable tedium.The text was updated successfully, but these errors were encountered: