commit | 3b5152803c6a2422e4204b7701abfcfe2d1fe7f7 | [log] [tgz] |
---|---|---|
author | rjamet <rjamet@google.com> | Tue Oct 01 07:39:01 2019 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Tue Oct 01 07:39:19 2019 -0700 |
tree | 9c3e0d474641e1ab71a445ee23b7be9930caae5d | |
parent | 50f1e354c7bd0d5219fadf8b28264e99619967c6 [diff] |
Add the possibility to set a rule name in a conformanceRule's config. Tsetse's error whitelisting scheme, when used with Bazel, relies on the rule name as the key to the whitelist object, but our current autogenerated rule names for ConformancePattern rules won't cut it: there could be two different BANNED_NAME rules enabled in the same codebase, who'd have colliding names with the current naming rules. With this change, the configuration of a rule lets you specify its rule name to avoid that collision. PiperOrigin-RevId: 272206672
This repo contains a mirror of some Google-internal bits that support TypeScript development under Bazel.
It contains these utilities:
ts_devserver
: a Go library and binary that runs a fast local web server which concatenates JavaScript on-the-fly. It requires inputs in a named module format (module ids must be contained in the file, not inferred from the file's path).ts_auto_deps
: a Go library and binary which generates BUILD.bazel
files from TypeScript sources.tsc_wrapped
: a TypeScript program which wraps the TypeScript compiler, hosting it under a Bazel worker.tsetse
: a collection of third-party “strictness” checks which we add to the TypeScript compiler.internal/common/*.bzl
: some Starlark utility code for running the ts_library
rule.There are no user-facing bits in this repo. These utilities are consumed in https://github.com/bazelbuild/rules_nodejs/tree/master/packages/typescript
Please file issues for ts_library
rule and other Bazel rules in that repo.