Alex Eagle
Alex Eagle
Related to https://github.com/bazelbuild/bazel-gazelle/issues/1173 This fails ``` # gazelle:proto_strip_import_prefix /rt/proto/libs/libbdican # gazelle:proto file # gazelle:go_generate_proto false # gazelle:proto_plugin py implementation builtin:python # gazelle:proto_rule proto_compile implementation stackb:rules_proto:proto_compile # gazelle:proto_rule proto_py_library implementation stackb:rules_proto:proto_py_library...
The logic for taking the basename assumes that outputs are in the same folder with the package. This fix allows a protoc invocation like ``` proto_compile( name = "view_display_proto_compile", output_mappings...
@cgrindel and I are discussing the best way to provide formatting capabilities for Bazel swift users. The first facility required is a Bazel repository rule that fetches a prebuilt formatter...
Currently this is hard-coded to BROWSER: https://github.com/bazelbuild/rules_closure/blob/4c559574447f90751f05155faba4f3344668f666/java/com/google/javascript/jscomp/JsCompilerRunner.java#L64 That causes an error with ES2015 import syntax: ``` ERROR: /usr/local/google/home/alexeagle/Projects/rules_typescript/examples/es6_output/BUILD.bazel:38:1: Compiling 3 JavaScript files to examples/es6_output/closure.js failed: Worker process sent response with...
A `Makefile` is generated during compilation, for example the `ffi-napi` package leaves a file `node_modules/ffi-napi/build/Makefile` on the disk. This file contains an absolute path on the disk, which is non-deterministic:...
A common pathological case is `@com_github_docker_docker` which can spend hundreds of seconds generating BUILD files. Users are stuck waiting for this to run anytime the repository rule is invalidated. @siggisim...
I'm working in a large monorepo migrating to Bazel. The proto imports do not currently match the repo structure. It seems there is no way to instruct the generation of...
This is a major usability hurdle at one of Aspect's clients. Gazelle fails because they have some junk in their repo which is covered by a `.gitignore` so they don't...
I have a package starting with `@` which has been legal in Bazel since somewhere in the pre-1.0 release time. (It's needed to express packages which are also published to...
I'm fixing rules_nodejs right now to let you pick arbitrary status keys in the stamping implementation - then we can remove this change to stamp.sh which was a workaround https://github.com/bazelbuild/bazelisk/commit/541325d070f320e78c2e30d1d6feeaba787c8162#diff-9004e026c175cbe67e8119d1bc0fc801