Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Rewrite visibility advice in build style guide.
Directly from the prior conversation, say both __pkg__ and __subpackages__ are equally appropriate and acceptable. Should I add a section saying to consider __subpackages__ to avoid churn when clients refactor their code? Re-order so the first thing said is the 'thesis' that "Visibility should be scoped as tightly as possible" (since that seems to be the main takeaway for the section). From my own experience, directly caution against using package default_visibility. Note, I am convinced there is a bug regarding default_visibility that is causing too many files to be exposed. Files used as inputs are implicitly exported with default_visibility even if exports_files is never used. This bug as well as people overusing default_visibility has caused substantial headaches when trying to refactor code. RELNOTES: Update visibility advice in build-style PiperOrigin-RevId: 246048587
- Loading branch information