@angular-wave/angular.ts 0.0.29 → 0.0.30

package/index.html

@@ -16,7 +16,7 @@
  
       <!-- <script src="dist/angular-ts.umd.js"></script> -->
       <!-- include spec files here... -->
- 
+
       <script type="module" src="test/directive/boolean.spec.js"></script>
       <script type="module" src="test/directive/form.spec.js"></script>
       <script type="module" src="test/directive/input.spec.js"></script> 
@@ -26,7 +26,7 @@
       <script type="module" src="test/directive/click.spec.js"></script>
       <script type="module" src="test/directive/cloak.spec.js"></script>
       <script type="module" src="test/directive/controller.spec.js"></script>
-      <script type="module" src="test/directive/event.spec.js"></script>
+      <!--   <script type="module" src="test/directive/event.spec.js"></script>
       <script type="module" src="test/directive/href.spec.js"></script>
       <script type="module" src="test/directive/if.spec.js"></script>
       <script type="module" src="test/directive/include.spec.js"></script>
@@ -70,7 +70,6 @@
       <script type="module" src="test/core/on.spec.js"></script>
       <script type="module" src="test/core/prop.spec.js"></script>
       <script type="module" src="test/core/parse.spec.js"></script>
-      <script type="module" src="test/core/pubsub.spec.js"></script>
       <script type="module" src="test/core/q.spec.js"></script>
       <script type="module" src="test/core/root-element.spec.js"></script>
 
@@ -96,8 +95,8 @@
       <script type="module" src="test/shared/common.spec.js"></script>
       <script type="module" src="test/shared/hof.spec.js"></script>
       <script type="module" src="test/shared/strings.spec.js"></script>
-      <script type="module" src="test/shared/utils.spec.js"></script>
-      
+      <script type="module" src="test/shared/utils.spec.js"></script>-->
+      <!-- <script type="module" src="test/core/pubsub.spec.js"></script>-->
       <script type="module" src="test/router/glob.spec.js"></script>
       <script type="module" src="test/router/services.spec.js"></script>
       <script type="module" src="test/router/state-directives.spec.js"></script>
@@ -108,7 +107,7 @@
       <script type="module" src="test/router/view-directive.spec.js"></script>
       <script type="module" src="test/router/view-hook.spec.js"></script>
       <script type="module" src="test/router/view-scroll.spec.js"></script>
-      <script type="module" src="test/router/view.spec.js"></script>
+      <script type="module" src="test/router/view.spec.js"></script> 
 
   
       <!-- <script type="module" src="test/core/interval.spec.js"></script>

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@angular-wave/angular.ts",
   "license": "MIT",
-  "version": "0.0.29",
+  "version": "0.0.30",
   "type": "module",
   "main": "dist/angular-ts.esm.js",
   "browser": "dist/angular-ts.umd.js",

package/src/core/controller.js

@@ -98,7 +98,10 @@ export function $ControllerProvider() {
         //   param `ident` --- An optional label which overrides the label parsed from the controller
         //                     expression, if any.
         let instance;
+
+        /** @type { RegExpMatchArray | null} */
         let match;
+
         let constructor;
         let identifier;
         later = later === true;

package/src/directive/controller.js

@@ -1,59 +1,3 @@
-/**
- * @ngdoc directive
- * @name ngController
- *
- * @description
- * The `ngController` directive attaches a controller class to the view. This is a key aspect of how angular
- * supports the principles behind the Model-View-Controller design pattern.
- *
- * MVC components in angular:
- *
- * * Model — Models are the properties of a scope; scopes are attached to the DOM where scope properties
- *   are accessed through bindings.
- * * View — The template (HTML with data bindings) that is rendered into the View.
- * * Controller — The `ngController` directive specifies a Controller class; the class contains business
- *   logic behind the application to decorate the scope with functions and values
- *
- * Note that you can also attach controllers to the DOM by declaring it in a route definition
- * via the {@link ngRoute.$route $route} service. A common mistake is to declare the controller
- * again using `ng-controller` in the template itself.  This will cause the controller to be attached
- * and executed twice.
- *
- * @element ANY
- * @scope
- * @priority 500
- * @param {String} ngController Name of a constructor function registered with the current
- * {@link ng.$controllerProvider $controllerProvider} or an {@link guide/expression expression}
- * that on the current scope evaluates to a constructor function.
- *
- * The controller instance can be published into a scope property by specifying
- * `ng-controller="as propertyName"`.
- *
- * @example
- * Here is a simple form for editing user contact information. Adding, removing, clearing, and
- * greeting are methods declared on the controller (see source tab). These methods can
- * easily be called from the AngularJS markup. Any changes to the data are automatically reflected
- * in the View without the need for a manual update.
- *
- * Two different declaration styles are included below:
- *
- * * one binds methods and properties directly onto the controller using `this`:
- * `ng-controller="SettingsController1 as settings"`
- * * one injects `$scope` into the controller:
- * `ng-controller="SettingsController2"`
- *
- * The second option is more common in the AngularJS community, and is generally used in boilerplates
- * and in this guide. However, there are advantages to binding properties directly to the controller
- * and avoiding scope.
- *
- * * Using `controller as` makes it obvious which controller you are accessing in the template when
- * multiple controllers apply to an element.
- * * If you are writing your controllers as classes you have easier access to the properties and
- * methods, which will appear on the scope, from inside the controller code.
- * * Since there is always a `.` in the bindings, you don't have to worry about prototypal
- * inheritance masking primitives.
- *
- */
 export const ngControllerDirective = [
   () => ({
     restrict: "A",

package/src/directive/controller.md

@@ -0,0 +1,46 @@
+# ngController Directive
+
+## Description
+
+The `ngController` directive attaches a controller class to the view. This is a key aspect of how Angular supports the principles behind the Model-View-Controller design pattern.
+
+### MVC components in Angular:
+
+- **Model**: Models are the properties of a scope; scopes are attached to the DOM where scope properties are accessed through bindings.
+- **View**: The template (HTML with data bindings) that is rendered into the View.
+- **Controller**: The `ngController` directive specifies a Controller class; the class contains business logic behind the application to decorate the scope with functions and values.
+
+Note that you can also attach controllers to the DOM by declaring it in a route definition via the [$route](https://docs.angularjs.org/api/ngRoute/service/$route) service. A common mistake is to declare the controller again using `ng-controller` in the template itself. This will cause the controller to be attached and executed twice.
+
+## Element
+
+`ANY`
+
+## Scope
+
+Yes
+
+## Priority
+
+500
+
+## Parameter
+
+- **ngController**: Name of a constructor function registered with the current [$controllerProvider](https://docs.angularjs.org/api/ng/provider/$controllerProvider) or an [expression](https://docs.angularjs.org/guide/expression) that on the current scope evaluates to a constructor function.
+
+  The controller instance can be published into a scope property by specifying `ng-controller="as propertyName"`.
+
+## Example
+
+Here is a simple form for editing user contact information. Adding, removing, clearing, and greeting are methods declared on the controller (see source tab). These methods can easily be called from the AngularJS markup. Any changes to the data are automatically reflected in the View without the need for a manual update.
+
+Two different declaration styles are included below:
+
+- One binds methods and properties directly onto the controller using `this`: `ng-controller="SettingsController1 as settings"`
+- One injects `$scope` into the controller: `ng-controller="SettingsController2"`
+
+The second option is more common in the AngularJS community and is generally used in boilerplates and in this guide. However, there are advantages to binding properties directly to the controller and avoiding scope.
+
+- Using `controller as` makes it obvious which controller you are accessing in the template when multiple controllers apply to an element.
+- If you are writing your controllers as classes you have easier access to the properties and methods, which will appear on the scope, from inside the controller code.
+- Since there is always a `.` in the bindings, you don't have to worry about prototypal inheritance masking primitives.

package/src/router/common/trace.js

@@ -81,7 +81,7 @@ const _tid = parse("$id");
 const _rid = parse("router.$id");
 const transLbl = (trans) => `Transition #${_tid(trans)}-${_rid(trans)}`;
 /**
- * Prints UI-Router Transition trace information to the console.
+ * Prints ng-router Transition trace information to the console.
  */
 export class Trace {
   constructor() {

package/src/router/directives/state-directives.js

@@ -1,7 +1,7 @@
 /**
  * # Angular 1 Directives
  *
- * These are the directives included in UI-Router for Angular 1.
+ * These are the directives included in ng-router for Angular 1.
  * These directives are used in templates to create viewports and link/navigate to states.
  *
  */

package/src/router/hooks/update-globals.js

@@ -1,6 +1,6 @@
 import { copy } from "../../shared/common";
 /**
- * A [[TransitionHookFn]] which updates global UI-Router state
+ * A [[TransitionHookFn]] which updates global ng-router state
  *
  * Registered using `transitionService.onBefore({}, updateGlobalState);`
  *

package/src/router/injectables.js

@@ -61,7 +61,7 @@
  */
 let $stateParams;
 /**
- * Global UI-Router variables
+ * Global ng-router variables
  *
  * The router global state as a **Service Object** (injectable during runtime).
  *
@@ -69,23 +69,23 @@ let $stateParams;
  */
 let $routerGlobals;
 /**
- * The UI-Router instance
+ * The ng-router instance
  *
  * The [[UIRouter]] singleton (the router instance) as a **Service Object** (injectable during runtime).
  *
- * This object is the UI-Router singleton instance, created by angular dependency injection during application bootstrap.
- * It has references to the other UI-Router services
+ * This object is the ng-router singleton instance, created by angular dependency injection during application bootstrap.
+ * It has references to the other ng-router services
  *
  * #### Note: This object is also exposed as [[$routerProvider]] for injection during angular config time.
  */
 let $router;
 /**
- * The UI-Router instance
+ * The ng-router instance
  *
  * The [[UIRouter]] singleton (the router instance) as a **Provider Object** (injectable during config phase).
  *
- * This object is the UI-Router singleton instance, created by angular dependency injection during application bootstrap.
- * It has references to the other UI-Router services
+ * This object is the ng-router singleton instance, created by angular dependency injection during application bootstrap.
+ * It has references to the other ng-router services
  *
  * #### Note: This object is also exposed as [[$router]] for injection during runtime.
  */
@@ -193,7 +193,7 @@ let $stateRegistryProvider;
  * The [[UIViewScrollProvider]] as a **Provider Object** (injectable during config time).
  *
  * This angular service exposes the [[UIViewScrollProvider]] singleton and is
- * used to disable UI-Router's scroll behavior.
+ * used to disable ng-router's scroll behavior.
  */
 let $ngViewScrollProvider;
 /**

package/src/router/resolve/resolve-context.js

@@ -26,7 +26,7 @@ export const NATIVE_INJECTOR_TOKEN = "Native Injector";
 /**
  * Encapsulates Dependency Injection for a path of nodes
  *
- * UI-Router states are organized as a tree.
+ * ng-router states are organized as a tree.
  * A nested state has a path of ancestors to the root of the tree.
  * When a state is being activated, each element in the path is wrapped as a [[PathNode]].
  * A `PathNode` is a stateful object that holds things like parameters and resolvables for the state being activated.

package/src/router/router.js

@@ -20,7 +20,7 @@ import { registerRedirectToHook } from "./hooks/redirect-to";
 let routerId = 0;
 
 /**
- * An instance of UI-Router.
+ * An instance of ng-router.
  * @class
  *
  * This object contains references to service APIs which define your application's routing behavior.
@@ -118,78 +118,8 @@ export class UIRouter {
 
     this.transitionService._deregisterHookFns.activateViews =
       registerActivateViews(this.transitionService, this.viewService);
-
-    /** @internal plugin instances are registered here */
-    this._plugins = {};
     this.viewService._pluginapi._rootViewContext(this.stateRegistry.root());
     this.globals.$current = this.stateRegistry.root();
     this.globals.current = this.globals.$current.self;
   }
-
-  /**
-   * Adds a plugin to UI-Router
-   *
-   * This method adds a UI-Router Plugin.
-   * A plugin can enhance or change UI-Router behavior using any public API.
-   *
-   * #### Example:
-   * ```js
-   * import { MyCoolPlugin } from "ui-router-cool-plugin";
-   *
-   * var plugin = router.addPlugin(MyCoolPlugin);
-   * ```
-   *
-   * ### Plugin authoring
-   *
-   * A plugin is simply a class (or constructor function) which accepts a [[UIRouter]] instance and (optionally) an options object.
-   *
-   * The plugin can implement its functionality using any of the public APIs of [[UIRouter]].
-   * For example, it may configure router options or add a Transition Hook.
-   *
-   * The plugin can then be published as a separate module.
-   *
-   * #### Example:
-   * ```js
-   * export class MyAuthPlugin implements UIRouterPlugin {
-   *   constructor(router: UIRouter, options: any) {
-   *     this.name = "MyAuthPlugin";
-   *     let $transitions = router.transitionService;
-   *     let $state = router.stateService;
-   *
-   *     let authCriteria = {
-   *       to: (state) => state.data && state.data.requiresAuth
-   *     };
-   *
-   *     function authHook(transition: Transition) {
-   *       let authService = transition.injector().get('AuthService');
-   *       if (!authService.isAuthenticated()) {
-   *         return $state.target('login');
-   *       }
-   *     }
-   *
-   *     $transitions.onStart(authCriteria, authHook);
-   *   }
-   * }
-   * ```
-   *
-   * @param plugin one of:
-   *        - a plugin class which implements [[UIRouterPlugin]]
-   *        - a constructor function for a [[UIRouterPlugin]] which accepts a [[UIRouter]] instance
-   *        - a factory function which accepts a [[UIRouter]] instance and returns a [[UIRouterPlugin]] instance
-   * @param options options to pass to the plugin class/factory
-   * @returns the registered plugin instance
-   */
-  plugin(plugin, options = {}) {
-    const pluginInstance = new plugin(this, options);
-    if (!pluginInstance.name)
-      throw new Error(
-        "Required property `name` missing on plugin: " + pluginInstance,
-      );
-    return (this._plugins[pluginInstance.name] = pluginInstance);
-  }
-  getPlugin(pluginName) {
-    return pluginName
-      ? this._plugins[pluginName]
-      : Object.values(this._plugins);
-  }
 }

package/src/router/services.js

@@ -1,8 +1,8 @@
 /**
  * # Angular 1 types
  *
- * UI-Router core provides various Typescript types which you can use for code completion and validating parameter values, etc.
- * The customizations to the core types for Angular UI-Router are documented here.
+ * ng-router core provides various Typescript types which you can use for code completion and validating parameter values, etc.
+ * The customizations to the core types for ng-router are documented here.
  *
  * The optional [[$resolve]] service is also documented here.
  *
@@ -13,10 +13,7 @@ import { applyPairs, unnestR } from "../shared/common";
 import { isString } from "../shared/utils";
 import { trace } from "./common/trace";
 import { UIRouter } from "./router";
-import { getNg1ViewConfigFactory } from "./state/views";
-
 import { StateProvider } from "./state-provider";
-import { ResolveContext } from "./resolve/resolve-context";
 
 /** @type {angular.UIRouter}} */
 export let router = null;
@@ -29,12 +26,6 @@ export function $routerProvider($locationProvider) {
     router.stateRegistry,
     router.stateService,
   );
-  router.viewService._pluginapi._viewConfigFactory(
-    "ng1",
-    getNg1ViewConfigFactory(),
-  );
-  // Disable decoding of params by UrlMatcherFactory because $location already handles this
-  router.urlService.config._decodeParams = false;
 
   /**
    * Applys ng1-specific path parameter encoding
@@ -135,28 +126,3 @@ export const getLocals = (ctx) => {
   });
   return tuples.reduce(applyPairs, {});
 };
-
-/**
- * This is a [[StateBuilder.builder]] function for angular1 `onEnter`, `onExit`,
- * `onRetain` callback hooks on a [[Ng1StateDeclaration]].
- *
- * When the [[StateBuilder]] builds a [[StateObject]] object from a raw [[StateDeclaration]], this builder
- * ensures that those hooks are injectable for @uirouter/angularjs (ng1).
- *
- * @internalapi
- */
-const getStateHookBuilder = (hookName) =>
-  function stateHookBuilder(stateObject) {
-    const hook = stateObject[hookName];
-    const pathname = hookName === "onExit" ? "from" : "to";
-    function decoratedNg1Hook(trans, state) {
-      const resolveContext = new ResolveContext(trans.treeChanges(pathname));
-      const subContext = resolveContext.subContext(state.$$state());
-      const locals = Object.assign(getLocals(subContext), {
-        $state$: state,
-        $transition$: trans,
-      });
-      return services.$injector.invoke(hook, this, locals);
-    }
-    return hook ? decoratedNg1Hook : undefined;
-  };

package/src/router/state/state-object.js

@@ -3,7 +3,7 @@ import { propEq } from "../../shared/hof";
 import { Glob } from "../common/glob";
 import { isFunction, isObject } from "../../shared/utils";
 /**
- * Internal representation of a UI-Router state.
+ * Internal representation of a ng-router state.
  *
  * Instances of this class are created when a [[StateDeclaration]] is registered with the [[StateRegistry]].
  *

package/src/router/state/state-registry.js

@@ -125,7 +125,7 @@ export class StateRegistry {
    * Gets the implicit root state
    *
    * Gets the root of the state tree.
-   * The root state is implicitly created by UI-Router.
+   * The root state is implicitly created by ng-router.
    * Note: this returns the internal [[StateObject]] representation, not a [[StateDeclaration]]
    *
    * @return the root [[StateObject]]

package/src/router/state/target-state.js

@@ -22,7 +22,7 @@ import { stringify } from "../../shared/strings";
  * 3) and transition options
  * 4) the registered state object (the [[StateDeclaration]])
  *
- * Many UI-Router APIs such as [[StateService.go]] take a [[StateOrName]] argument which can
+ * Many ng-router APIs such as [[StateService.go]] take a [[StateOrName]] argument which can
  * either be a *state object* (a [[StateDeclaration]] or [[StateObject]]) or a *state name* (a string).
  * The `TargetState` class normalizes those options.
  *

package/src/router/state/views.js

@@ -11,7 +11,7 @@ export function getNg1ViewConfigFactory() {
   let templateFactory = null;
   return (path, view) => {
     templateFactory =
-      templateFactory || services.$injector.get("$templateFactory");
+      templateFactory || services.$injector.get("$templateFactory"); // TODO: remove static injector
     return [new Ng1ViewConfig(path, view, templateFactory)];
   };
 }

package/src/router/url/url-config.js

@@ -18,8 +18,6 @@ export class UrlConfig {
     /** @type {ParamTypes} */
     this.paramTypes = new ParamTypes();
     /** @type {boolean} */
-    this._decodeParams = true;
-    /** @type {boolean} */
     this._isCaseInsensitive = false;
     /** @type {boolean} */
     this._isStrictMode = true;

package/src/router/url/url-matcher-factory.js

@@ -41,7 +41,6 @@ export class UrlMatcherFactory {
     const globalConfig = {
       strict: urlConfig._isStrictMode,
       caseInsensitive: urlConfig._isCaseInsensitive,
-      decodeParams: urlConfig._decodeParams,
     };
     return new UrlMatcher(
       pattern,

package/src/router/url/url-matcher.js

@@ -39,7 +39,6 @@ const defaultConfig = {
   state: { params: {} },
   strict: true,
   caseInsensitive: true,
-  decodeParams: true,
 };
 /**
  * Matches URLs against patterns.
@@ -313,13 +312,6 @@ export class UrlMatcher {
   }
   _getDecodedParamValue(value, param) {
     if (isDefined(value)) {
-      if (this.config.decodeParams && !param.type.raw) {
-        if (Array.isArray(value)) {
-          value = value.map((paramValue) => decodeURIComponent(paramValue));
-        } else {
-          value = decodeURIComponent(value);
-        }
-      }
       value = param.type.decode(value);
     }
     return param.value(value);

package/src/router/url/url-service.js

@@ -213,9 +213,9 @@ export class UrlService {
    * Starts or stops listening for URL changes
    *
    * Call this sometime after calling [[deferIntercept]] to start monitoring the url.
-   * This causes UI-Router to start listening for changes to the URL, if it wasn't already listening.
+   * This causes ng-router to start listening for changes to the URL, if it wasn't already listening.
    *
-   * If called with `false`, UI-Router will stop listening (call listen(true) to start listening again).
+   * If called with `false`, ng-router will stop listening (call listen(true) to start listening again).
    *
    * #### Example:
    * ```js
@@ -243,15 +243,15 @@ export class UrlService {
   /**
    * Disables monitoring of the URL.
    *
-   * Call this method before UI-Router has bootstrapped.
-   * It will stop UI-Router from performing the initial url sync.
+   * Call this method before ng-router has bootstrapped.
+   * It will stop ng-router from performing the initial url sync.
    *
    * This can be useful to perform some asynchronous initialization before the router starts.
-   * Once the initialization is complete, call [[listen]] to tell UI-Router to start watching and synchronizing the URL.
+   * Once the initialization is complete, call [[listen]] to tell ng-router to start watching and synchronizing the URL.
    *
    * #### Example:
    * ```js
-   * // Prevent UI-Router from automatically intercepting URL changes when it starts;
+   * // Prevent ng-router from automatically intercepting URL changes when it starts;
    * urlService.deferIntercept();
    *
    * fetch('/states.json').then(resp => resp.json()).then(data => {

package/src/router/view/view.js

@@ -8,6 +8,7 @@ import {
 import { curry, prop } from "../../shared/hof";
 import { isString } from "../../shared/utils";
 import { trace } from "../common/trace";
+import { getNg1ViewConfigFactory } from "../state/views";
 /**
  * The View service
  *
@@ -45,6 +46,7 @@ export class ViewService {
         return () => removeFrom(this._listeners, listener);
       },
     };
+    this._pluginapi._viewConfigFactory("ng1", getNg1ViewConfigFactory());
   }
 
   /**

package/src/shared/common.js

@@ -1,5 +1,5 @@
 /**
- * Random utility functions used in the UI-Router code
+ * Random utility functions used in the ng-router code
  *
  * These functions are exported, but are subject to change without notice.
  *

package/types/router/core/common/coreservices.d.ts

@@ -39,7 +39,7 @@ export interface CoreServices {
  * Implementors should pass these through to the underlying URL mechanism.
  * The underlying URL mechanism might be browser APIs, framework APIs, or some 3rd party URL management library.
  *
- * UI-Router Core includes three basic implementations:
+ * Router Core includes three basic implementations:
  *
  * - [[PushStateLocationService]]
  * - [[HashLocationService]]
@@ -61,7 +61,7 @@ export interface LocationServices {
  * Implementors should pass these through to the underlying URL APIs.
  * The underlying URL mechanism might be browser APIs, framework APIs, or some 3rd party URL management library.
  *
- * UI-Router Core includes two basic implementations:
+ * Router Core includes two basic implementations:
  *
  * - [[BrowserLocationConfig]]
  * - [[MemoryLocationConfig]]

package/types/router/core/common/trace.d.ts

@@ -1,6 +1,6 @@
 import { Transition } from "../transition/transition";
 import { ViewTuple } from "../view";
-import { ActiveUIView, ViewConfig, ViewContext } from "../view/interface";
+import { ActiveNGView, ViewConfig, ViewContext } from "../view/interface";
 import { Resolvable } from "../resolve/resolvable";
 import { PathNode } from "../path/pathNode";
 import { PolicyWhen } from "../resolve/interface";
@@ -24,12 +24,12 @@ declare enum Category {
   RESOLVE = 0,
   TRANSITION = 1,
   HOOK = 2,
-  UIVIEW = 3,
+  NGVIEW = 3,
   VIEWCONFIG = 4,
 }
 export { Category };
 /**
- * Prints UI-Router Transition trace information to the console.
+ * Prints Router Transition trace information to the console.
  */
 export declare class Trace {
   /** @internal */
@@ -101,17 +101,17 @@ export declare class Trace {
   /** @internal called by ui-router code */
   traceSuccess(finalState: StateObject, trans: Transition): void;
   /** @internal called by ui-router code */
-  traceUIViewEvent(event: string, viewData: ActiveUIView, extra?: string): void;
+  traceNGViewEvent(event: string, viewData: ActiveNGView, extra?: string): void;
   /** @internal called by ui-router code */
-  traceUIViewConfigUpdated(viewData: ActiveUIView, context: ViewContext): void;
+  traceNGViewConfigUpdated(viewData: ActiveNGView, context: ViewContext): void;
   /** @internal called by ui-router code */
-  traceUIViewFill(viewData: ActiveUIView, html: string): void;
+  traceNGViewFill(viewData: ActiveNGView, html: string): void;
   /** @internal called by ui-router code */
   traceViewSync(pairs: ViewTuple[]): void;
   /** @internal called by ui-router code */
   traceViewServiceEvent(event: string, viewConfig: ViewConfig): void;
   /** @internal called by ui-router code */
-  traceViewServiceUIViewEvent(event: string, viewData: ActiveUIView): void;
+  traceViewServiceNGViewEvent(event: string, viewData: ActiveNGView): void;
 }
 /**
  * The [[Trace]] singleton

package/types/router/core/globals.d.ts

@@ -3,12 +3,13 @@ import { StateDeclaration } from "./state/interface";
 import { StateObject } from "./state/stateObject";
 import { Transition } from "./transition/transition";
 import { Queue } from "./common/queue";
+/**
  * Global router state
  *
  * This is where we hold the global mutable state such as current state, current
  * params, current transition, etc.
  */
-export declare class UIRouterGlobals {
+export declare class RouterGlobals {
   /**
    * Current parameter values
    *