Lines Matching refs:visibility

161 E.g. The following will set the default visibility for all the modules defined in the package and
162 any subpackages that do not set their own default visibility (irrespective of whether they are in
282 The `visibility` property on a module controls whether the module can be
284 in the same package. This is based on the Bazel visibility mechanism.
286 If specified the `visibility` property must contain at least one rule.
289 * `["//visibility:public"]`: Anyone can use this module.
290 * `["//visibility:private"]`: Only rules in the module's package (not its
292 * `["//visibility:override"]`: Discards any rules inherited from defaults or a
293 creating module. Can only be used at the beginning of a list of visibility
312 * `["//visibility:legacy_public"]`: The default visibility, behaves as
313 `//visibility:public` for now. It is an error if it is used in a module.
315 The visibility rules of `//visibility:public` and `//visibility:private` cannot
316 be combined with any other visibility specifications, except
317 `//visibility:public` is allowed to override visibility specifications imported
325 If a module does not specify the `visibility` property then it uses the
333 global default of `//visibility:legacy_public`.
335 The `visibility` property has no effect on a defaults module although it does
336 apply to any non-defaults module that uses it. To set the visibility of a
341 global refactoring will be done to change this to `//visibility:private` at
344 `default_visibility = [//visibility:legacy_public]` added. It will then be the
345 owner's responsibility to replace that with a more appropriate visibility.
498 by all of the vendor's other modules using the normal namespace and visibility