From f7e13755835e249251149f8f438a69f9e036f0de Mon Sep 17 00:00:00 2001
From: David Reher <david.reher@gmx.de>
Date: Wed, 23 Dec 2015 13:11:57 +0100
Subject: [PATCH] added controller interfaces and test file

---
 angularjs/angular-component-router.d.ts | 107 ++++++++++++++++++++++++
 1 file changed, 107 insertions(+)

diff --git a/angularjs/angular-component-router.d.ts b/angularjs/angular-component-router.d.ts
index b4ee317cc..da93596ca 100644
--- a/angularjs/angular-component-router.d.ts
+++ b/angularjs/angular-component-router.d.ts
@@ -319,4 +319,111 @@ declare module angular {
         specificity: number;
         params: {[key: string]: any};
     }
+
+    /**
+     * Defines route lifecycle method `routerOnActivate`, which is called by the router at the end of a
+     * successful route navigation.
+     *
+     * For a single component's navigation, only one of either {@link OnActivate} or {@link OnReuse}
+     * will be called depending on the result of {@link CanReuse}.
+     *
+     * The `routerOnActivate` hook is called with two {@link ComponentInstruction}s as parameters, the
+     * first
+     * representing the current route being navigated to, and the second parameter representing the
+     * previous route or `null`.
+     *
+     * If `routerOnActivate` returns a promise, the route change will wait until the promise settles to
+     * instantiate and activate child components.
+     *
+     * ### Example
+     * {@example router/ts/on_activate/on_activate_example.ts region='routerOnActivate'}
+     */
+    interface OnActivate {
+        $routerOnActivate(next?: angular.ComponentInstruction, prev?: angular.ComponentInstruction): any;
+    }
+
+    /**
+     * Defines route lifecycle method `routerCanDeactivate`, which is called by the router to determine
+     * if a component can be removed as part of a navigation.
+     *
+     * The `routerCanDeactivate` hook is called with two {@link ComponentInstruction}s as parameters,
+     * the
+     * first representing the current route being navigated to, and the second parameter
+     * representing the previous route.
+     *
+     * If `routerCanDeactivate` returns or resolves to `false`, the navigation is cancelled. If it
+     * returns or
+     * resolves to `true`, then the navigation continues, and the component will be deactivated
+     * (the {@link OnDeactivate} hook will be run) and removed.
+     *
+     * If `routerCanDeactivate` throws or rejects, the navigation is also cancelled.
+     *
+     * ### Example
+     * {@example router/ts/can_deactivate/can_deactivate_example.ts region='routerCanDeactivate'}
+     */
+    interface CanDeactivate {
+        $routerCanDeactivate(next?: ComponentInstruction, prev?: ComponentInstruction): boolean | Promise<boolean>;
+    }
+
+    /**
+     * Defines route lifecycle method `routerOnDeactivate`, which is called by the router before
+     * destroying
+     * a component as part of a route change.
+     *
+     * The `routerOnDeactivate` hook is called with two {@link ComponentInstruction}s as parameters, the
+     * first
+     * representing the current route being navigated to, and the second parameter representing the
+     * previous route.
+     *
+     * If `routerOnDeactivate` returns a promise, the route change will wait until the promise settles.
+     *
+     * ### Example
+     * {@example router/ts/on_deactivate/on_deactivate_example.ts region='routerOnDeactivate'}
+     */
+    interface OnDeactivate {
+        $routerOnDeactivate(next?: angular.ComponentInstruction, prev?: angular.ComponentInstruction): any;
+    }
+
+    /**
+     * Defines route lifecycle method `routerCanReuse`, which is called by the router to determine
+     * whether a
+     * component should be reused across routes, or whether to destroy and instantiate a new component.
+     *
+     * The `routerCanReuse` hook is called with two {@link ComponentInstruction}s as parameters, the
+     * first
+     * representing the current route being navigated to, and the second parameter representing the
+     * previous route.
+     *
+     * If `routerCanReuse` returns or resolves to `true`, the component instance will be reused and the
+     * {@link OnDeactivate} hook will be run. If `routerCanReuse` returns or resolves to `false`, a new
+     * component will be instantiated, and the existing component will be deactivated and removed as
+     * part of the navigation.
+     *
+     * If `routerCanReuse` throws or rejects, the navigation will be cancelled.
+     *
+     * ### Example
+     * {@example router/ts/reuse/reuse_example.ts region='reuseCmp'}
+     */
+    interface CanReuse {
+        $routerCanReuse(next?: angular.ComponentInstruction, prev?: angular.ComponentInstruction): boolean | Promise<boolean>;
+    }
+
+    /**
+     * Defines route lifecycle method `routerOnReuse`, which is called by the router at the end of a
+     * successful route navigation when {@link CanReuse} is implemented and returns or resolves to true.
+     *
+     * For a single component's navigation, only one of either {@link OnActivate} or {@link OnReuse}
+     * will be called, depending on the result of {@link CanReuse}.
+     *
+     * The `routerOnReuse` hook is called with two {@link ComponentInstruction}s as parameters, the
+     * first
+     * representing the current route being navigated to, and the second parameter representing the
+     * previous route or `null`.
+     *
+     * ### Example
+     * {@example router/ts/reuse/reuse_example.ts region='reuseCmp'}
+     */
+    interface OnReuse {
+        $routerOnReuse(next?: angular.ComponentInstruction, prev?: angular.ComponentInstruction): any;
+    }
 }