221 lines
5.8 KiB
TypeScript
Raw Normal View History

/**
* @license
* Copyright Google Inc. All Rights Reserved.
*
* Use of this source code is governed by an MIT-style license that can be
* found in the LICENSE file at https://angular.io/license
*/
import {Type} from '../type';
/**
2016-09-14 09:43:01 -07:00
* @whatItDoes Configures the {@link Injector} to return an instance of `Type` when `Type' is used
* as token.
* @howToUse
* ```
* @Injectable()
* class MyService {}
*
* const provider: TypeProvider = MyService;
* ```
*
* @description
2015-04-15 22:35:38 +00:00
*
* Create an instance by invoking the `new` operator and supplying additional arguments.
* This form is a short form of `TypeProvider`;
2015-04-15 22:35:38 +00:00
*
2016-09-14 09:43:01 -07:00
* For more details, see the {@linkDocs guide/dependency-injection "Dependency Injection Guide"}.
*
2016-09-14 09:43:01 -07:00
* ### Example
2015-04-15 22:35:38 +00:00
*
2016-09-14 09:43:01 -07:00
* {@example core/di/ts/provider_spec.ts region='TypeProvider'}
*
* @stable
*/
export interface TypeProvider extends Type<any> {}
2015-04-15 22:35:38 +00:00
/**
2016-09-14 09:43:01 -07:00
* @whatItDoes Configures the {@link Injector} to return a value for a token.
* @howToUse
* ```
* const provider: ValueProvider = {provide: 'someToken', useValue: 'someValue'};
* ```
*
* @description
* For more details, see the {@linkDocs guide/dependency-injection "Dependency Injection Guide"}.
*
* ### Example
*
2016-09-14 09:43:01 -07:00
* {@example core/di/ts/provider_spec.ts region='ValueProvider'}
*
* @stable
*/
export interface ValueProvider {
2015-04-15 22:35:38 +00:00
/**
feat(core): Add type information to injector.get() (#13785) - Introduce `InjectionToken<T>` which is a parameterized and type-safe version of `OpaqueToken`. DEPRECATION: - `OpaqueToken` is now deprecated, use `InjectionToken<T>` instead. - `Injector.get(token: any, notFoundValue?: any): any` is now deprecated use the same method which is now overloaded as `Injector.get<T>(token: Type<T>|InjectionToken<T>, notFoundValue?: T): T;`. Migration - Replace `OpaqueToken` with `InjectionToken<?>` and parameterize it. - Migrate your code to only use `Type<?>` or `InjectionToken<?>` as injection tokens. Using other tokens will not be supported in the future. BREAKING CHANGE: - Because `injector.get()` is now parameterize it is possible that code which used to work no longer type checks. Example would be if one injects `Foo` but configures it as `{provide: Foo, useClass: MockFoo}`. The injection instance will be that of `MockFoo` but the type will be `Foo` instead of `any` as in the past. This means that it was possible to call a method on `MockFoo` in the past which now will fail type check. See this example: ``` class Foo {} class MockFoo extends Foo { setupMock(); } var PROVIDERS = [ {provide: Foo, useClass: MockFoo} ]; ... function myTest(injector: Injector) { var foo = injector.get(Foo); // This line used to work since `foo` used to be `any` before this // change, it will now be `Foo`, and `Foo` does not have `setUpMock()`. // The fix is to downcast: `injector.get(Foo) as MockFoo`. foo.setUpMock(); } ``` PR Close #13785
2017-01-03 16:54:46 -08:00
* An injection token. (Typically an instance of `Type` or `InjectionToken`, but can be `any`).
2015-04-15 22:35:38 +00:00
*/
provide: any;
2015-04-15 22:35:38 +00:00
/**
* The value to inject.
2015-04-15 22:35:38 +00:00
*/
useValue: any;
2015-04-15 22:35:38 +00:00
/**
* If true, then injector returns an array of instances. This is useful to allow multiple
* providers spread across many files to provide configuration information to a common token.
2015-04-15 22:35:38 +00:00
*
* ### Example
2015-04-15 22:35:38 +00:00
*
2016-09-14 09:43:01 -07:00
* {@example core/di/ts/provider_spec.ts region='MultiProviderAspect'}
2015-04-15 22:35:38 +00:00
*/
multi?: boolean;
}
2015-04-15 22:35:38 +00:00
/**
2016-09-14 09:43:01 -07:00
* @whatItDoes Configures the {@link Injector} to return an instance of `useClass` for a token.
* @howToUse
* ```
* @Injectable()
* class MyService {}
*
2016-09-14 09:43:01 -07:00
* const provider: ClassProvider = {provide: 'someToken', useClass: MyService};
* ```
*
2016-09-14 09:43:01 -07:00
* @description
* For more details, see the {@linkDocs guide/dependency-injection "Dependency Injection Guide"}.
*
2016-09-14 09:43:01 -07:00
* ### Example
*
2016-09-14 09:43:01 -07:00
* {@example core/di/ts/provider_spec.ts region='ClassProvider'}
*
2016-09-14 09:43:01 -07:00
* Note that following two providers are not equal:
* {@example core/di/ts/provider_spec.ts region='ClassProviderDifference'}
*
* @stable
*/
export interface ClassProvider {
2015-04-15 22:35:38 +00:00
/**
feat(core): Add type information to injector.get() (#13785) - Introduce `InjectionToken<T>` which is a parameterized and type-safe version of `OpaqueToken`. DEPRECATION: - `OpaqueToken` is now deprecated, use `InjectionToken<T>` instead. - `Injector.get(token: any, notFoundValue?: any): any` is now deprecated use the same method which is now overloaded as `Injector.get<T>(token: Type<T>|InjectionToken<T>, notFoundValue?: T): T;`. Migration - Replace `OpaqueToken` with `InjectionToken<?>` and parameterize it. - Migrate your code to only use `Type<?>` or `InjectionToken<?>` as injection tokens. Using other tokens will not be supported in the future. BREAKING CHANGE: - Because `injector.get()` is now parameterize it is possible that code which used to work no longer type checks. Example would be if one injects `Foo` but configures it as `{provide: Foo, useClass: MockFoo}`. The injection instance will be that of `MockFoo` but the type will be `Foo` instead of `any` as in the past. This means that it was possible to call a method on `MockFoo` in the past which now will fail type check. See this example: ``` class Foo {} class MockFoo extends Foo { setupMock(); } var PROVIDERS = [ {provide: Foo, useClass: MockFoo} ]; ... function myTest(injector: Injector) { var foo = injector.get(Foo); // This line used to work since `foo` used to be `any` before this // change, it will now be `Foo`, and `Foo` does not have `setUpMock()`. // The fix is to downcast: `injector.get(Foo) as MockFoo`. foo.setUpMock(); } ``` PR Close #13785
2017-01-03 16:54:46 -08:00
* An injection token. (Typically an instance of `Type` or `InjectionToken`, but can be `any`).
2015-04-15 22:35:38 +00:00
*/
provide: any;
2015-04-15 22:35:38 +00:00
/**
* Class to instantiate for the `token`.
2015-04-15 22:35:38 +00:00
*/
useClass: Type<any>;
2015-04-15 22:35:38 +00:00
/**
* If true, then injector returns an array of instances. This is useful to allow multiple
* providers spread across many files to provide configuration information to a common token.
*
2015-09-17 13:12:50 -07:00
* ### Example
*
2016-09-14 09:43:01 -07:00
* {@example core/di/ts/provider_spec.ts region='MultiProviderAspect'}
2015-04-15 22:35:38 +00:00
*/
multi?: boolean;
}
/**
2016-09-14 09:43:01 -07:00
* @whatItDoes Configures the {@link Injector} to return a value of another `useExisting` token.
* @howToUse
* ```
* const provider: ExistingProvider = {provide: 'someToken', useExisting: 'someOtherToken'};
* ```
*
2016-09-14 09:43:01 -07:00
* @description
* For more details, see the {@linkDocs guide/dependency-injection "Dependency Injection Guide"}.
*
2016-09-14 09:43:01 -07:00
* ### Example
*
2016-09-14 09:43:01 -07:00
* {@example core/di/ts/provider_spec.ts region='ExistingProvider'}
*
* @stable
*/
export interface ExistingProvider {
/**
feat(core): Add type information to injector.get() (#13785) - Introduce `InjectionToken<T>` which is a parameterized and type-safe version of `OpaqueToken`. DEPRECATION: - `OpaqueToken` is now deprecated, use `InjectionToken<T>` instead. - `Injector.get(token: any, notFoundValue?: any): any` is now deprecated use the same method which is now overloaded as `Injector.get<T>(token: Type<T>|InjectionToken<T>, notFoundValue?: T): T;`. Migration - Replace `OpaqueToken` with `InjectionToken<?>` and parameterize it. - Migrate your code to only use `Type<?>` or `InjectionToken<?>` as injection tokens. Using other tokens will not be supported in the future. BREAKING CHANGE: - Because `injector.get()` is now parameterize it is possible that code which used to work no longer type checks. Example would be if one injects `Foo` but configures it as `{provide: Foo, useClass: MockFoo}`. The injection instance will be that of `MockFoo` but the type will be `Foo` instead of `any` as in the past. This means that it was possible to call a method on `MockFoo` in the past which now will fail type check. See this example: ``` class Foo {} class MockFoo extends Foo { setupMock(); } var PROVIDERS = [ {provide: Foo, useClass: MockFoo} ]; ... function myTest(injector: Injector) { var foo = injector.get(Foo); // This line used to work since `foo` used to be `any` before this // change, it will now be `Foo`, and `Foo` does not have `setUpMock()`. // The fix is to downcast: `injector.get(Foo) as MockFoo`. foo.setUpMock(); } ``` PR Close #13785
2017-01-03 16:54:46 -08:00
* An injection token. (Typically an instance of `Type` or `InjectionToken`, but can be `any`).
*/
provide: any;
/**
* Existing `token` to return. (equivalent to `injector.get(useExisting)`)
*/
useExisting: any;
/**
* If true, then injector returns an array of instances. This is useful to allow multiple
* providers spread across many files to provide configuration information to a common token.
*
* ### Example
*
2016-09-14 09:43:01 -07:00
* {@example core/di/ts/provider_spec.ts region='MultiProviderAspect'}
*/
multi?: boolean;
}
2015-09-17 13:12:50 -07:00
/**
2016-09-14 09:43:01 -07:00
* @whatItDoes Configures the {@link Injector} to return a value by invoking a `useFactory`
* function.
* @howToUse
* ```
* function serviceFactory() { ... }
*
* const provider: FactoryProvider = {provide: 'someToken', useFactory: serviceFactory, deps: []};
* ```
*
* @description
* For more details, see the {@linkDocs guide/dependency-injection "Dependency Injection Guide"}.
2015-04-17 03:29:05 -07:00
*
* ### Example
2015-09-03 16:17:23 -07:00
*
2016-09-14 09:43:01 -07:00
* {@example core/di/ts/provider_spec.ts region='FactoryProvider'}
*
2016-09-14 09:43:01 -07:00
* Dependencies can also be marked as optional:
* {@example core/di/ts/provider_spec.ts region='FactoryProviderOptionalDeps'}
*
* @stable
*/
export interface FactoryProvider {
2015-04-15 22:35:38 +00:00
/**
feat(core): Add type information to injector.get() (#13785) - Introduce `InjectionToken<T>` which is a parameterized and type-safe version of `OpaqueToken`. DEPRECATION: - `OpaqueToken` is now deprecated, use `InjectionToken<T>` instead. - `Injector.get(token: any, notFoundValue?: any): any` is now deprecated use the same method which is now overloaded as `Injector.get<T>(token: Type<T>|InjectionToken<T>, notFoundValue?: T): T;`. Migration - Replace `OpaqueToken` with `InjectionToken<?>` and parameterize it. - Migrate your code to only use `Type<?>` or `InjectionToken<?>` as injection tokens. Using other tokens will not be supported in the future. BREAKING CHANGE: - Because `injector.get()` is now parameterize it is possible that code which used to work no longer type checks. Example would be if one injects `Foo` but configures it as `{provide: Foo, useClass: MockFoo}`. The injection instance will be that of `MockFoo` but the type will be `Foo` instead of `any` as in the past. This means that it was possible to call a method on `MockFoo` in the past which now will fail type check. See this example: ``` class Foo {} class MockFoo extends Foo { setupMock(); } var PROVIDERS = [ {provide: Foo, useClass: MockFoo} ]; ... function myTest(injector: Injector) { var foo = injector.get(Foo); // This line used to work since `foo` used to be `any` before this // change, it will now be `Foo`, and `Foo` does not have `setUpMock()`. // The fix is to downcast: `injector.get(Foo) as MockFoo`. foo.setUpMock(); } ``` PR Close #13785
2017-01-03 16:54:46 -08:00
* An injection token. (Typically an instance of `Type` or `InjectionToken`, but can be `any`).
2015-04-15 22:35:38 +00:00
*/
provide: any;
2015-04-15 22:35:38 +00:00
/**
* A function to invoke to create a value for this `token`. The function is invoked with
* resolved values of `token`s in the `deps` field.
2015-04-15 22:35:38 +00:00
*/
useFactory: Function;
2015-04-15 22:35:38 +00:00
/**
* A list of `token`s which need to be resolved by the injector. The list of values is then
* used as arguments to the `useFactory` function.
2015-04-15 22:35:38 +00:00
*/
deps?: any[];
2015-04-15 22:35:38 +00:00
/**
* If true, then injector returns an array of instances. This is useful to allow multiple
* providers spread across many files to provide configuration information to a common token.
2015-04-15 22:35:38 +00:00
*
* ### Example
2015-04-15 22:35:38 +00:00
*
2016-09-14 09:43:01 -07:00
* {@example core/di/ts/provider_spec.ts region='MultiProviderAspect'}
2015-04-15 22:35:38 +00:00
*/
multi?: boolean;
}
/**
2016-09-14 09:43:01 -07:00
* @whatItDoes Describes how the {@link Injector} should be configured.
* @howToUse
* See {@link TypeProvider}, {@link ValueProvider}, {@link ClassProvider}, {@link ExistingProvider},
* {@link FactoryProvider}.
*
2016-09-14 09:43:01 -07:00
* @description
* For more details, see the {@linkDocs guide/dependency-injection "Dependency Injection Guide"}.
*
* @stable
*/
export type Provider =
TypeProvider | ValueProvider | ClassProvider | ExistingProvider | FactoryProvider | any[];