angular-cn/third_party/fonts.google.com/open-sans
Paul Gschwendtner 3c7fdc6a9e build: fix routing playground example using external resource (#28490)
Currently the "routing" playground example fails the e2e tests
because it tries to load the OpenSans font using an external
HTTP request. External http requests are not allowed (unless
explicitly enabled) within Bazel in order to ensure that
all targets are built and tested in a hermetic way.

In order to work around this issue in a Bazel idiomatic way,
we just vendor the fonts in the "third_party" folder. Note
that we can technically also enable internet for the RBE
host platform, but it's not a best practice for hermeticity.

The following syntax would allow us to enable internet for
RBE (stated here for tracking)

```
properties: {
  name: "dockerNetwork"
  value: "standard"
}
```

PR Close #28490
2019-02-04 16:51:11 -05:00
..
BUILD.bazel build: fix routing playground example using external resource (#28490) 2019-02-04 16:51:11 -05:00
LICENSE.txt build: fix routing playground example using external resource (#28490) 2019-02-04 16:51:11 -05:00
OpenSans-Bold.ttf build: fix routing playground example using external resource (#28490) 2019-02-04 16:51:11 -05:00
OpenSans-Light.ttf build: fix routing playground example using external resource (#28490) 2019-02-04 16:51:11 -05:00
OpenSans-Regular.ttf build: fix routing playground example using external resource (#28490) 2019-02-04 16:51:11 -05:00
OpenSans-SemiBold.ttf build: fix routing playground example using external resource (#28490) 2019-02-04 16:51:11 -05:00
open-sans.css build: fix routing playground example using external resource (#28490) 2019-02-04 16:51:11 -05:00