@bazel/buildozer
Advanced tools
Comparing version 4.0.1 to 4.2.1
{ | ||
"name": "@bazel/buildozer", | ||
"description": "A command line tool to rewrite multiple BUILD files using standard commands", | ||
"version": "4.0.1", | ||
"version": "4.2.1", | ||
"license": "Apache-2.0", | ||
@@ -6,0 +6,0 @@ "bin": { |
@@ -22,6 +22,9 @@ # Buildozer | ||
Here, `label-list` is a space-separated list of Bazel labels, for example | ||
`//path/to/pkg1:rule1 //path/to/pkg2:rule2`. Buildozer reads commands from | ||
`FILE` (`-` for stdin (format: `|`-separated command line arguments to buildozer, | ||
excluding flags)) | ||
`//path/to/pkg1:rule1 //path/to/pkg2:rule2`. | ||
When `-f FILE` is used, buildozer reads commands from `FILE` (`-` for stdin). | ||
Format: lines of `|`-separated sets of commands and labels (`command args|label|label...`). | ||
When the label is a single '*', then the command will be applied to all | ||
elements of label-list from the command line. | ||
You should specify at least one command and one target. Buildozer will execute | ||
@@ -88,3 +91,4 @@ all commands on all targets. Commands are executed in order, files are processed | ||
* `new <rule_kind> <rule_name> [(before|after) <relative_rule_name>]`: Add a | ||
new rule at the end of the BUILD file (before/after `<relative_rule>`). | ||
new rule at the end of the BUILD file (before/after `<relative_rule>`). The | ||
identifier `__pkg__` can be used to position rules relative to package(). | ||
* `print <attr(s)>` | ||
@@ -91,0 +95,0 @@ * `remove <attr>`: Removes attribute `attr`. |
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Native code
Supply chain riskContains native code (e.g., compiled binaries or shared libraries). Including native code can obscure malicious behavior.
Found 1 instance in 1 package
34723441
11
297
7