tree 0513d29831827d71d8192f7d177006d513188236
parent 25f301f841cf874f50ae6cf6ec096e3e48e62851
author alexeagle <alexeagle@google.com> 1515517904 +0100
committer Florian Weikert <fwe@google.com> 1532708764 +0200

The default_tsconfig feature has a design flaw.

If you use this feature, and add a strictness option to your tsconfig.json, code from other workspaces which relies on the default tsconfig.json will be compiled with your new setting, and may fail. This violates the encapsulation guarantee you'd expect: code from another workspace should be compiled with the tsconfig.json from that workspace, and its compilation should not depend on a file owned in a dependent workspace.

If you really want this feature, you can use a macro to declare a variant of ts_library that picks up your default value, like https://github.com/alexeagle/angular-bazel-example/pull/45/files

Fixes #122

PiperOrigin-RevId: 181327885