docs: update contributing to use bazel from npm

This commit is contained in:
Alan Agius 2019-04-23 16:01:18 +02:00 committed by Alex Eagle
parent e1269cb520
commit a1c87dd577
2 changed files with 6 additions and 6 deletions

View File

@ -284,18 +284,18 @@ To test if your change effect the public API you need to run the API guardian on
For example in case `@angular-devkit/core` package was modified you need to run:
```bash
bazel test //etc/api:angular_devkit_core_api
yarn bazel test //etc/api:angular_devkit_core_api
```
You can also test all packages by running:
```bash
bazel test //etc/api ...
yarn bazel test //etc/api ...
```
If you modified the public API, the test will fail. To update the golden files you need to run:
```bash
bazel run //etc/api:angular_devkit_core_api.accept
yarn bazel run //etc/api:angular_devkit_core_api.accept
```
**Note**: In some cases we use aliased symbols to create namespaces.

View File

@ -273,18 +273,18 @@ To test if your change effect the public API you need to run the API guardian on
For example in case `@angular-devkit/core` package was modified you need to run:
```bash
bazel test //etc/api:angular_devkit_core_api
yarn bazel test //etc/api:angular_devkit_core_api
```
You can also test all packages by running:
```bash
bazel test //etc/api ...
yarn bazel test //etc/api ...
```
If you modified the public API, the test will fail. To update the golden files you need to run:
```bash
bazel run //etc/api:angular_devkit_core_api.accept
yarn bazel run //etc/api:angular_devkit_core_api.accept
```
**Note**: In some cases we use aliased symbols to create namespaces.