honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: corrected spelling of "ambient".

This commit is contained in:
Noah Medling 2018-04-24 15:15:45 -05:00 committed by Victor Berchet
parent 43a49d3f64
commit 8d0ee34939
No known key found for this signature in database
GPG Key ID: 74ACF42B93D98910
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
aio/content/guide/aot-compiler.md
View File

@ -987,7 +987,7 @@ import { configuration } from './configuration';
The compiler encountered a type and can't determine which module exports that type.
This can happen if you refer to an ambient type.
For example, the `Window` type is an ambiant type declared in the global `.d.ts` file.
For example, the `Window` type is an ambient type declared in the global `.d.ts` file.
You'll get an error if you reference it in the component constructor,
which the compiler must statically analyze.
@ -999,17 +999,17 @@ export class MyComponent {
constructor (private win: Window) { ... }
}
```
TypeScript understands ambiant types so you don't import them.
TypeScript understands ambient types so you don't import them.
The Angular compiler does not understand a type that you neglect to export or import.
In this case, the compiler doesn't understand how to inject something with the `Window` token.
Do not refer to ambient types in metadata expressions.
If you must inject an instance of an ambiant type,
If you must inject an instance of an ambient type,
you can finesse the problem in four steps:
1. Create an injection token for an instance of the ambiant type.
1. Create an injection token for an instance of the ambient type.
1. Create a factory function that returns that instance.
1. Add a `useFactory` provider with that factory function.
1. Use `@Inject` to inject the instance.