Graham/angular-cli
1
0
Fork 0
mirror of https://github.com/angular/angular-cli.git synced 2025-05-18 03:23:57 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: remove usage of blacklist from third-party-libraries documentation

Browse Source 
Replace the usage of blacklist with a description of the prevention/disclusion
methods which are beging described.
This commit is contained in:
Joey Perrott 2020-09-22 12:18:43 -07:00 committed by Minko Gechev
parent 88c3acb945
commit dd59bfcc60
1 changed files with 2 additions and 2 deletions

4
docs/design/third-party-libraries.md

@ -143,14 +143,14 @@ that those hooks might not prompt users (no STDIN) and throw an error.
# <a name="providers">Providers</a>
Adding Angular providers to the app should be seamless. The install process will create a
`providers.js` from all the providers contained in all the dependencies. The User can blacklist
`providers.js` from all the providers contained in all the dependencies. The User can disclude
providers it doesn't want.
The `providers.js` file will always be overwritten by the `install` / `uninstall` process. It
needs to exist for toolings to be able to understand dependencies. These providers are global
to the application.
In order to blacklist providers from being global, the user can use the `--no-global-providers`
In order to prevent providers from being global, the user can use the `--no-global-providers`
flag during installation, or can change the dependencies by using `ng providers`. As an example:
```bash