// Type definitions for Angular v2.0.0-39 // Project: http://angular.io/ // Definitions by: angular team // Definitions: https://github.com/borisyankov/DefinitelyTyped // *********************************************************** // This file is generated by the Angular build process. // Please do not create manual edits or send pull requests // modifying this file. // *********************************************************** // angular2/angular2 depends transitively on these libraries. // If you don't have them installed you can install them using TSD // https://github.com/DefinitelyTyped/tsd /// // angular2/web_worker/worker depends transitively on these libraries. // If you don't have them installed you can install them using TSD // https://github.com/DefinitelyTyped/tsd /// // angular2/web_worker/ui depends transitively on these libraries. // If you don't have them installed you can install them using TSD // https://github.com/DefinitelyTyped/tsd /// interface Map {} declare module ng { // See https://github.com/Microsoft/TypeScript/issues/1168 class BaseException /* extends Error */ { message: string; stack: string; toString(): string; } interface InjectableReference {} } declare module ngWorker { // See https://github.com/Microsoft/TypeScript/issues/1168 class BaseException /* extends Error */ { message: string; stack: string; toString(): string; } interface InjectableReference {} } declare module ngUi { // See https://github.com/Microsoft/TypeScript/issues/1168 class BaseException /* extends Error */ { message: string; stack: string; toString(): string; } interface InjectableReference {} } declare module ng { /** * Declares an injectable parameter to be a live list of directives or variable * bindings from the content children of a directive. * * ### Example ([live demo](http://plnkr.co/edit/lY9m8HLy7z06vDoUaSN2?p=preview)) * * Assume that `` component would like to get a list its children `` * components as shown in this example: * * ```html * * ... * {{o.text}} * * ``` * * The preferred solution is to query for `Pane` directives using this decorator. * * ```javascript * @Component({ * selector: 'pane', * inputs: ['title'] * }) * @View(...) * class Pane { * title:string; * } * * @Component({ * selector: 'tabs' * }) * @View({ * template: ` *
    *
  • {{pane.title}}
  • *
* * ` * }) * class Tabs { * panes: QueryList; * constructor(@Query(Pane) panes:QueryList) { * this.panes = panes; * } * } * ``` * * A query can look for variable bindings by passing in a string with desired binding symbol. * * ### Example ([live demo](http://plnkr.co/edit/sT2j25cH1dURAyBRCKx1?p=preview)) * ```html * *
...
*
* * @Component({ * selector: 'foo' * }) * @View(...) * class seeker { * constructor(@Query('findme') elList: QueryList) {...} * } * ``` * * In this case the object that is injected depend on the type of the variable * binding. It can be an ElementRef, a directive or a component. * * Passing in a comma separated list of variable bindings will query for all of them. * * ```html * *
...
*
...
*
* * @Component({ * selector: 'foo' * }) * @View(...) * class Seeker { * constructor(@Query('findMe, findMeToo') elList: QueryList) {...} * } * ``` * * Configure whether query looks for direct children or all descendants * of the querying element, by using the `descendants` parameter. * It is set to `false` by default. * * ### Example ([live demo](http://plnkr.co/edit/wtGeB977bv7qvA5FTYl9?p=preview)) * ```html * * a * b * * c * * * ``` * * When querying for items, the first container will see only `a` and `b` by default, * but with `Query(TextDirective, {descendants: true})` it will see `c` too. * * The queried directives are kept in a depth-first pre-order with respect to their * positions in the DOM. * * Query does not look deep into any subcomponent views. * * Query is updated as part of the change-detection cycle. Since change detection * happens after construction of a directive, QueryList will always be empty when observed in the * constructor. * * The injected object is an unmodifiable live list. * See {@link QueryList} for more details. */ class QueryMetadata extends DependencyMetadata { constructor(_selector: Type | string, {descendants, first}?: {descendants?: boolean, first?: boolean}); /** * whether we want to query only direct children (false) or all * children (true). */ descendants: boolean; first: boolean; /** * always `false` to differentiate it with {@link ViewQueryMetadata}. */ isViewQuery: boolean; /** * what this is querying for. */ selector: any; /** * whether this is querying for a variable binding or a directive. */ isVarBindingQuery: boolean; /** * returns a list of variable bindings this is querying for. * Only applicable if this is a variable bindings query. */ varBindings: string[]; toString(): string; } /** * Configures a content query. * * Content queries are set before the `afterContentInit` callback is called. * * ### Example * * ``` * @Directive({ * selector: 'someDir' * }) * class SomeDir { * @ContentChildren(ChildDirective) contentChildren: QueryList; * * afterContentInit() { * // contentChildren is set * } * } * ``` */ class ContentChildrenMetadata extends QueryMetadata { constructor(_selector: Type | string, {descendants}?: {descendants?: boolean}); } /** * Configures a content query. * * Content queries are set before the `afterContentInit` callback is called. * * ### Example * * ``` * @Directive({ * selector: 'someDir' * }) * class SomeDir { * @ContentChild(ChildDirective) contentChild; * * afterContentInit() { * // contentChild is set * } * } * ``` */ class ContentChildMetadata extends QueryMetadata { constructor(_selector: Type | string); } /** * Configures a view query. * * View queries are set before the `afterViewInit` callback is called. * * ### Example * * ``` * @Component({ * selector: 'someDir' * }) * @View({templateUrl: 'someTemplate', directives: [ItemDirective]}) * class SomeDir { * @ViewChildren(ItemDirective) viewChildren: QueryList; * * afterViewInit() { * // viewChildren is set * } * } * ``` */ class ViewChildrenMetadata extends ViewQueryMetadata { constructor(_selector: Type | string); } /** * Similar to {@link QueryMetadata}, but querying the component view, instead of * the content children. * * ### Example ([live demo](http://plnkr.co/edit/eNsFHDf7YjyM6IzKxM1j?p=preview)) * * ```javascript * @Component({...}) * @View({ * template: ` * a * b * c * ` * }) * class MyComponent { * shown: boolean; * * constructor(private @Query(Item) items:QueryList) { * items.onChange(() => console.log(items.length)); * } * } * ``` * * Supports the same querying parameters as {@link QueryMetadata}, except * `descendants`. This always queries the whole view. * * As `shown` is flipped between true and false, items will contain zero of one * items. * * Specifies that a {@link QueryList} should be injected. * * The injected object is an iterable and observable live list. * See {@link QueryList} for more details. */ class ViewQueryMetadata extends QueryMetadata { constructor(_selector: Type | string, {descendants, first}?: {descendants?: boolean, first?: boolean}); /** * always `true` to differentiate it with {@link QueryMetadata}. */ isViewQuery: any; toString(): string; } /** * Configures a view query. * * View queries are set before the `afterViewInit` callback is called. * * ### Example * * ``` * @Component({ * selector: 'someDir' * }) * @View({templateUrl: 'someTemplate', directives: [ItemDirective]}) * class SomeDir { * @ViewChild(ItemDirective) viewChild:ItemDirective; * * afterViewInit() { * // viewChild is set * } * } * ``` */ class ViewChildMetadata extends ViewQueryMetadata { constructor(_selector: Type | string); } /** * Specifies that a constant attribute value should be injected. * * The directive can inject constant string literals of host element attributes. * * ## Example * * Suppose we have an `` element and want to know its `type`. * * ```html * * ``` * * A decorator can inject string literal `text` like so: * * ```javascript * @Directive({ * selector: `input' * }) * class InputDirective { * constructor(@Attribute('type') type) { * // type would be `text` in this example * } * } * ``` */ class AttributeMetadata extends DependencyMetadata { constructor(attributeName: string); attributeName: string; token: any; toString(): string; } /** * Declare reusable UI building blocks for an application. * * Each Angular component requires a single `@Component` and at least one `@View` annotation. The * `@Component` * annotation specifies when a component is instantiated, and which properties and hostListeners it * binds to. * * When a component is instantiated, Angular * - creates a shadow DOM for the component. * - loads the selected template into the shadow DOM. * - creates all the injectable objects configured with `bindings` and `viewBindings`. * * All template expressions and statements are then evaluated against the component instance. * * For details on the `@View` annotation, see {@link ViewMetadata}. * * ## Lifecycle hooks * * When the component class implements some {@link angular2/lifecycle_hooks} the callbacks are * called by the change detection at defined points in time during the life of the component. * * ## Example * * ``` * @Component({ * selector: 'greet' * }) * @View({ * template: 'Hello {{name}}!' * }) * class Greet { * name: string; * * constructor() { * this.name = 'World'; * } * } * ``` */ class ComponentMetadata extends DirectiveMetadata { constructor({selector, inputs, outputs, properties, events, host, exportAs, moduleId, bindings, viewBindings, changeDetection, queries}?: { selector?: string, inputs?: string[], outputs?: string[], properties?: string[], events?: string[], host?: {[key: string]: string}, bindings?: any[], exportAs?: string, moduleId?: string, viewBindings?: any[], queries?: {[key: string]: any}, changeDetection?: ChangeDetectionStrategy, }); /** * Defines the used change detection strategy. * * When a component is instantiated, Angular creates a change detector, which is responsible for * propagating the component's bindings. * * The `changeDetection` property defines, whether the change detection will be checked every time * or only when the component tells it to do so. */ changeDetection: ChangeDetectionStrategy; /** * Defines the set of injectable objects that are visible to its view DOM children. * * ## Simple Example * * Here is an example of a class that can be injected: * * ``` * class Greeter { * greet(name:string) { * return 'Hello ' + name + '!'; * } * } * * @Directive({ * selector: 'needs-greeter' * }) * class NeedsGreeter { * greeter:Greeter; * * constructor(greeter:Greeter) { * this.greeter = greeter; * } * } * * @Component({ * selector: 'greet', * viewBindings: [ * Greeter * ] * }) * @View({ * template: ``, * directives: [NeedsGreeter] * }) * class HelloWorld { * } * * ``` */ viewBindings: any[]; } /** * Directives allow you to attach behavior to elements in the DOM. * * {@link DirectiveMetadata}s with an embedded view are called {@link ComponentMetadata}s. * * A directive consists of a single directive annotation and a controller class. When the * directive's `selector` matches * elements in the DOM, the following steps occur: * * 1. For each directive, the `ElementInjector` attempts to resolve the directive's constructor * arguments. * 2. Angular instantiates directives for each matched element using `ElementInjector` in a * depth-first order, * as declared in the HTML. * * ## Understanding How Injection Works * * There are three stages of injection resolution. * - *Pre-existing Injectors*: * - The terminal {@link Injector} cannot resolve dependencies. It either throws an error or, if * the dependency was * specified as `@Optional`, returns `null`. * - The platform injector resolves browser singleton resources, such as: cookies, title, * location, and others. * - *Component Injectors*: Each component instance has its own {@link Injector}, and they follow * the same parent-child hierarchy * as the component instances in the DOM. * - *Element Injectors*: Each component instance has a Shadow DOM. Within the Shadow DOM each * element has an `ElementInjector` * which follow the same parent-child hierarchy as the DOM elements themselves. * * When a template is instantiated, it also must instantiate the corresponding directives in a * depth-first order. The * current `ElementInjector` resolves the constructor dependencies for each directive. * * Angular then resolves dependencies as follows, according to the order in which they appear in the * {@link ViewMetadata}: * * 1. Dependencies on the current element * 2. Dependencies on element injectors and their parents until it encounters a Shadow DOM boundary * 3. Dependencies on component injectors and their parents until it encounters the root component * 4. Dependencies on pre-existing injectors * * * The `ElementInjector` can inject other directives, element-specific special objects, or it can * delegate to the parent * injector. * * To inject other directives, declare the constructor parameter as: * - `directive:DirectiveType`: a directive on the current element only * - `@Host() directive:DirectiveType`: any directive that matches the type between the current * element and the * Shadow DOM root. * - `@Query(DirectiveType) query:QueryList`: A live collection of direct child * directives. * - `@QueryDescendants(DirectiveType) query:QueryList`: A live collection of any * child directives. * * To inject element-specific special objects, declare the constructor parameter as: * - `element: ElementRef` to obtain a reference to logical element in the view. * - `viewContainer: ViewContainerRef` to control child template instantiation, for * {@link DirectiveMetadata} directives only * - `bindingPropagation: BindingPropagation` to control change detection in a more granular way. * * ## Example * * The following example demonstrates how dependency injection resolves constructor arguments in * practice. * * * Assume this HTML template: * * ``` *
*
*
*
*
*
*
*
*
*
* ``` * * With the following `dependency` decorator and `SomeService` injectable class. * * ``` * @Injectable() * class SomeService { * } * * @Directive({ * selector: '[dependency]', * inputs: [ * 'id: dependency' * ] * }) * class Dependency { * id:string; * } * ``` * * Let's step through the different ways in which `MyDirective` could be declared... * * * ### No injection * * Here the constructor is declared with no arguments, therefore nothing is injected into * `MyDirective`. * * ``` * @Directive({ selector: '[my-directive]' }) * class MyDirective { * constructor() { * } * } * ``` * * This directive would be instantiated with no dependencies. * * * ### Component-level injection * * Directives can inject any injectable instance from the closest component injector or any of its * parents. * * Here, the constructor declares a parameter, `someService`, and injects the `SomeService` type * from the parent * component's injector. * ``` * @Directive({ selector: '[my-directive]' }) * class MyDirective { * constructor(someService: SomeService) { * } * } * ``` * * This directive would be instantiated with a dependency on `SomeService`. * * * ### Injecting a directive from the current element * * Directives can inject other directives declared on the current element. * * ``` * @Directive({ selector: '[my-directive]' }) * class MyDirective { * constructor(dependency: Dependency) { * expect(dependency.id).toEqual(3); * } * } * ``` * This directive would be instantiated with `Dependency` declared at the same element, in this case * `dependency="3"`. * * ### Injecting a directive from any ancestor elements * * Directives can inject other directives declared on any ancestor element (in the current Shadow * DOM), i.e. on the current element, the * parent element, or its parents. * ``` * @Directive({ selector: '[my-directive]' }) * class MyDirective { * constructor(@Host() dependency: Dependency) { * expect(dependency.id).toEqual(2); * } * } * ``` * * `@Host` checks the current element, the parent, as well as its parents recursively. If * `dependency="2"` didn't * exist on the direct parent, this injection would * have returned * `dependency="1"`. * * * ### Injecting a live collection of direct child directives * * * A directive can also query for other child directives. Since parent directives are instantiated * before child directives, a directive can't simply inject the list of child directives. Instead, * the directive injects a {@link QueryList}, which updates its contents as children are added, * removed, or moved by a directive that uses a {@link ViewContainerRef} such as a `ng-for`, an * `ng-if`, or an `ng-switch`. * * ``` * @Directive({ selector: '[my-directive]' }) * class MyDirective { * constructor(@Query(Dependency) dependencies:QueryList) { * } * } * ``` * * This directive would be instantiated with a {@link QueryList} which contains `Dependency` 4 and * 6. Here, `Dependency` 5 would not be included, because it is not a direct child. * * ### Injecting a live collection of descendant directives * * By passing the descendant flag to `@Query` above, we can include the children of the child * elements. * * ``` * @Directive({ selector: '[my-directive]' }) * class MyDirective { * constructor(@Query(Dependency, {descendants: true}) dependencies:QueryList) { * } * } * ``` * * This directive would be instantiated with a Query which would contain `Dependency` 4, 5 and 6. * * ### Optional injection * * The normal behavior of directives is to return an error when a specified dependency cannot be * resolved. If you * would like to inject `null` on unresolved dependency instead, you can annotate that dependency * with `@Optional()`. * This explicitly permits the author of a template to treat some of the surrounding directives as * optional. * * ``` * @Directive({ selector: '[my-directive]' }) * class MyDirective { * constructor(@Optional() dependency:Dependency) { * } * } * ``` * * This directive would be instantiated with a `Dependency` directive found on the current element. * If none can be * found, the injector supplies `null` instead of throwing an error. * * ## Example * * Here we use a decorator directive to simply define basic tool-tip behavior. * * ``` * @Directive({ * selector: '[tooltip]', * inputs: [ * 'text: tooltip' * ], * host: { * '(mouseenter)': 'onMouseEnter()', * '(mouseleave)': 'onMouseLeave()' * } * }) * class Tooltip{ * text:string; * overlay:Overlay; // NOT YET IMPLEMENTED * overlayManager:OverlayManager; // NOT YET IMPLEMENTED * * constructor(overlayManager:OverlayManager) { * this.overlay = overlay; * } * * onMouseEnter() { * // exact signature to be determined * this.overlay = this.overlayManager.open(text, ...); * } * * onMouseLeave() { * this.overlay.close(); * this.overlay = null; * } * } * ``` * In our HTML template, we can then add this behavior to a `
` or any other element with the * `tooltip` selector, * like so: * * ``` *
* ``` * * Directives can also control the instantiation, destruction, and positioning of inline template * elements: * * A directive uses a {@link ViewContainerRef} to instantiate, insert, move, and destroy views at * runtime. * The {@link ViewContainerRef} is created as a result of `