diff --git a/angular2/angular2-tests.ts.tscparams b/angular2/angular2-tests.ts.tscparams index cfedaf198..3f0863ac6 100644 --- a/angular2/angular2-tests.ts.tscparams +++ b/angular2/angular2-tests.ts.tscparams @@ -1 +1 @@ ---experimentalDecorators --target ES5 \ No newline at end of file +--experimentalDecorators --noImplicitAny --target ES5 diff --git a/angular2/angular2.d.ts b/angular2/angular2.d.ts index 0c7b8609e..15d7f1461 100644 --- a/angular2/angular2.d.ts +++ b/angular2/angular2.d.ts @@ -41,23 +41,23 @@ declare module ng { /** * 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}. - * + * * ## Example - * + * * ``` * @Component({ * selector: 'greet' @@ -67,7 +67,7 @@ declare module ng { * }) * class Greet { * name: string; - * + * * constructor() { * this.name = 'World'; * } @@ -75,47 +75,47 @@ declare module ng { * ``` */ class ComponentMetadata extends DirectiveMetadata { - + /** * 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: string; - + /** * 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: [ @@ -128,30 +128,30 @@ declare module ng { * }) * class HelloWorld { * } - * + * * ``` */ viewBindings: List; } - + /** * 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 @@ -165,24 +165,24 @@ declare module ng { * - *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 @@ -192,21 +192,21 @@ declare module ng { * 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: - * + * * ``` *
*
@@ -219,14 +219,14 @@ declare module ng { *
*
* ``` - * + * * With the following `dependency` decorator and `SomeService` injectable class. - * + * * ``` * @Injectable() * class SomeService { * } - * + * * @Directive({ * selector: '[dependency]', * properties: [ @@ -237,15 +237,15 @@ declare module ng { * 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 { @@ -253,15 +253,15 @@ declare module ng { * } * } * ``` - * + * * 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. @@ -272,14 +272,14 @@ declare module ng { * } * } * ``` - * + * * 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 { @@ -290,9 +290,9 @@ declare module ng { * ``` * 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. @@ -304,23 +304,23 @@ declare module ng { * } * } * ``` - * + * * `@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 { @@ -328,15 +328,15 @@ declare module ng { * } * } * ``` - * + * * 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 { @@ -344,18 +344,18 @@ declare module ng { * } * } * ``` - * + * * 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 { @@ -363,15 +363,15 @@ declare module ng { * } * } * ``` - * + * * 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]', @@ -387,16 +387,16 @@ declare module ng { * 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; @@ -406,39 +406,39 @@ declare module ng { * 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 `