| commit | df4ceb468acf4b13e197fd34e08c5e3e5dfdb281 | [log] [tgz] |
|---|---|---|
| author | Benjamin Peterson <bp@benjamin.pe> | Thu Dec 27 08:52:51 2018 -0800 |
| committer | Copybara-Service <copybara-piper@google.com> | Thu Dec 27 08:54:42 2018 -0800 |
| tree | 1941c665f22c76fd6b038e0643a65471d92a664c | |
| parent | d71711807853d321ecba894418db8db7c249c798 [diff] |
Rename SymlinkEvent.to to SymlinkEvent.path and SymlinkEvent.from to SymlinkEvent.target.
This naming has the advantages of
1. Being more consistent with traditional symlink terminology (c.f. `man ln`), other workspace log events ("path" is used for the filesystem entry that is created in the other event messages), and Bazel Starlark APIs ("SymlinkEntry" uses "path" and "target_file").
2. Avoids field names that are likely to be language keywords. In particular, "from" is a keyword in Python.
I assume the compatibility breakage here is okay because the workspace log is all under --experimental_workspace_rules_log_file.
Closes #6885.
PiperOrigin-RevId: 227032207
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel only rebuilds what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
See CONTRIBUTING.md
Bazel is released in ‘Beta’. See the product roadmap to learn about the path toward a stable 1.0 release.