Replies: 2 comments
-
Does the documentation here help you? https://github.com/bazel-contrib/rules_python/tree/main/gazelle#directive-python_default_visibility |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thank you! It does help, but let's say, I cannot tell gazelle to 'add visibility annotation to a py_library, unless a default visibiility has been set at the package level'? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I have a library which I want to make public since it's a base library for many other parts of the codebase. Therefore I set the visibility to public for the whole file:
Running
gazelle
however incorrectly adds a more restrictive visibility annotation, transforming theBUILD
file to:The added visibility is incorrect, as it overwrite the default visibility set at the package level.
Is there a way to fix this behavior, or at least provide a gazelle directive (at the root level) to tell gazelle to not add a visibility field to python targets?
Beta Was this translation helpful? Give feedback.
All reactions