@angular-wave/angular.ts 0.7.0-beta.0 → 0.7.0-beta.1

package/@types/router/transition/transition-service.d.ts

@@ -23,9 +23,9 @@ export namespace defaultTransOpts {
 export class TransitionProvider {
   static $inject: string[];
   /**
-   * @param {import('../globals').UIRouterGlobals} globals
+   * @param {import('../globals.js').RouterGlobals} globals
    */
-  constructor(globals: any, viewService: any);
+  constructor(globals: import("../globals.js").RouterGlobals, viewService: any);
   _transitionCount: number;
   /** The transition hook types, such as `onEnter`, `onStart`, etc */
   _eventTypes: any[];
@@ -33,7 +33,7 @@ export class TransitionProvider {
   _registeredHooks: {};
   /** The  paths on a criteria object */
   _criteriaPaths: {};
-  globals: any;
+  globals: import("../globals.js").RouterGlobals;
   $view: any;
   _deregisterHookFns: {};
   _pluginapi: any;

package/@types/router/transition/transition.d.ts

@@ -1,3 +1,4 @@
+/** @typedef {import('./interface.ts').IHookRegistry} IHookRegistry */
 /**
  * Represents a transition between two states.
  *
@@ -5,28 +6,30 @@
  *
  * This object contains all contextual information about the to/from states, parameters, resolves.
  * It has information about all states being entered and exited as a result of the transition.
+ * @implements {IHookRegistry}
  */
-export class Transition {
+export class Transition implements IHookRegistry {
   /**
    * Creates a new Transition object.
    *
    * If the target state is not valid, an error is thrown.
    *
-   * @internal
-   *
    * @param fromPath The path of [[PathNode]]s from which the transition is leaving.  The last node in the `fromPath`
    *        encapsulates the "from state".
    * @param targetState The target state and parameters being transitioned to (also, the transition options)
    * @param {import('../transition/transition-service.js').TransitionProvider} transitionService The [[TransitionService]] instance
-   * @internal
+   * @param {import('../globals.js').RouterGlobals} globals
    */
   constructor(
     fromPath: any,
     targetState: any,
     transitionService: import("../transition/transition-service.js").TransitionProvider,
-    globals: any,
+    globals: import("../globals.js").RouterGlobals,
   );
-  globals: any;
+  /**
+   * @type {import('../globals.js').RouterGlobals}
+   */
+  globals: import("../globals.js").RouterGlobals;
   transitionService: import("../transition/transition-service.js").TransitionProvider;
   _deferred: any;
   /**
@@ -52,6 +55,14 @@ export class Transition {
     exiting: any;
     entering: any;
   };
+  onStart: any;
+  onBefore: any;
+  onSuccess: any;
+  onEnter: any;
+  onRetain: any;
+  onExit: any;
+  onFinish: any;
+  onError: any;
   /**
    * Creates the transition-level hook registration functions
    * (which can then be used to register hooks)
@@ -60,15 +71,13 @@ export class Transition {
   getHooks(hookName: any): any;
   applyViewConfigs(): void;
   /**
-   * @internal
-   * @returns the internal from [State] object
+   * @returns {import('../state/state-object.js').StateObject} the internal from [State] object
    */
-  $from(): any;
+  $from(): import("../state/state-object.js").StateObject;
   /**
-   * @internal
-   * @returns the internal to [State] object
+   * @returns {import('../state/state-object.js').StateObject} the internal to [State] object
    */
-  $to(): any;
+  $to(): import("../state/state-object.js").StateObject;
   /**
    * Returns the "from state"
    *
@@ -76,7 +85,7 @@ export class Transition {
    *
    * @returns The state declaration object for the Transition's ("from state").
    */
-  from(): any;
+  from(): import("../state/interface.ts").StateDeclaration;
   /**
    * Returns the "to state"
    *
@@ -84,7 +93,7 @@ export class Transition {
    *
    * @returns The state declaration object for the Transition's target state ("to state").
    */
-  to(): any;
+  to(): import("../state/interface.ts").StateDeclaration;
   /**
    * Gets the Target State
    *
@@ -340,7 +349,7 @@ export class Transition {
    * @returns true if the Transition is ignored.
    */
   ignored(): boolean;
-  _ignoredReason(): "SameAsPending" | "SameAsCurrent";
+  _ignoredReason(): "SameAsCurrent" | "SameAsPending";
   /**
    * Runs the transition
    *
@@ -386,4 +395,5 @@ export class Transition {
 export namespace Transition {
   export { Transition as diToken };
 }
+export type IHookRegistry = import("./interface.ts").IHookRegistry;
 import { HookBuilder } from "./hook-builder.js";

package/@types/router/view/interface.d.ts

@@ -0,0 +1,44 @@
+import { ViewDeclaration } from "../state/interface.ts";
+import { PathNode } from "../path/path-node.js";
+/** The context ref can be anything that has a `name` and a `parent` reference to another IContextRef */
+export interface ViewContext {
+  name: string;
+  parent: ViewContext;
+}
+export interface ActiveUIView {
+  /** An auto-incremented id */
+  id: number;
+  /** The ui-view short name */
+  name: string;
+  /** The ui-view's fully qualified name */
+  fqn: string;
+  /** The ViewConfig that is currently loaded into the ui-view */
+  config: ViewConfig;
+  /** The state context in which the ui-view tag was created. */
+  creationContext: ViewContext;
+  /** A callback that should apply a ViewConfig (or clear the ui-view, if config is undefined) */
+  configUpdated: (config: ViewConfig) => void;
+}
+/**
+ * This interface represents a [[_ViewDeclaration]] that is bound to a [[PathNode]].
+ *
+ * A `ViewConfig` is the runtime definition of a single view.
+ *
+ * During a transition, `ViewConfig`s are created for each [[_ViewDeclaration]] defined on each "entering" [[StateObject]].
+ * Then, the [[ViewService]] finds any matching `ui-view`(s) in the DOM, and supplies the ui-view
+ * with the `ViewConfig`.  The `ui-view` then loads itself using the information found in the `ViewConfig`.
+ *
+ * A `ViewConfig` if matched with a `ui-view` by finding all `ui-view`s which were created in the
+ * context named by the `uiViewContextAnchor`, and finding the `ui-view` or child `ui-view` that matches
+ * the `uiViewName` address.
+ */
+export interface ViewConfig {
+  $id: number;
+  /** The normalized view declaration from [[State.views]] */
+  viewDecl: ViewDeclaration;
+  /** The node the ViewConfig is bound to */
+  path: PathNode[];
+  loaded: boolean;
+  /** Fetches templates, runs dynamic (controller|template)Provider code, lazy loads Components, etc */
+  load(): Promise<ViewConfig>;
+}

package/@types/router/view/view.d.ts

@@ -20,18 +20,30 @@ export class ViewService {
   _viewConfigFactories: {};
   _listeners: any[];
   _pluginapi: {
-    _rootViewContext: any;
-    _viewConfigFactory: any;
     _registeredUIView: (id: any) => undefined;
     _registeredUIViews: () => any[];
     _activeViewConfigs: () => any[];
     _onSync: (listener: any) => () => any;
   };
   $get: (() => this)[];
-  _rootViewContext(context: any): any;
+  /**
+   * @param {?import('../state/state-object.js').StateObject} context
+   * @return {?import('../state/state-object.js').StateObject}
+   */
+  rootViewContext(
+    context: import("../state/state-object.js").StateObject | null,
+  ): import("../state/state-object.js").StateObject | null;
   _rootContext: any;
-  _viewConfigFactory(factory: any): void;
-  createViewConfig(path: any, decl: any): any[];
+  viewConfigFactory(factory: any): void;
+  /**
+   * @param path
+   * @param decl
+   * @return {import("../state/views.js").ViewConfig}
+   */
+  createViewConfig(
+    path: any,
+    decl: any,
+  ): import("../state/views.js").ViewConfig;
   /**
    * Deactivates a ViewConfig.
    *

package/@types/shared/interface.d.ts

@@ -0,0 +1,6 @@
+export type Mapper<X, T> = (x: X, key?: string | number) => T;
+export interface TypedMap<T> {
+  [key: string]: T;
+}
+export type Predicate<X> = (x?: X) => boolean;
+export type PredicateBinary<X, Y> = (x?: X, y?: Y) => boolean;

package/@types/shared/utils.d.ts

@@ -188,43 +188,13 @@ export function baseExtend(dst: any, objs: any, deep: any): any;
  * to `dst`. You can specify multiple `src` objects. If you want to preserve original objects, you can do so
  * by passing an empty object as the target: `let object = angular.extend({}, object1, object2)`.
  *
- * **Note:** Keep in mind that `angular.extend` does not support recursive merge (deep copy). Use
- * {@link angular.merge} for this.
+ * **Note:** Keep in mind that `angular.extend` does not support recursive merge (deep copy).
  *
  * @param {Object} dst Destination object.
  * @param {...Object} src Source object(s).
  * @returns {Object} Reference to `dst`.
  */
 export function extend(dst: any, ...src: any[]): any;
-/**
- * Deeply extends the destination object `dst` by copying own enumerable properties from the `src` object(s)
- * to `dst`. You can specify multiple `src` objects. If you want to preserve original objects, you can do so
- * by passing an empty object as the target: `let object = angular.merge({}, object1, object2)`.
- *
- * Unlike {@link angular.extend extend()}, `merge()` recursively descends into object properties of source
- * objects, performing a deep copy.
- *
- * @deprecated
- * sinceVersion="1.6.5"
- * This function is deprecated, but will not be removed in the 1.x lifecycle.
- * There are edge cases (see {@link angular.merge#known-issues known issues}) that are not
- * supported by this function. We suggest using another, similar library for all-purpose merging,
- * such as [lodash's merge()](https://lodash.com/docs/4.17.4#merge).
- *
- * @knownIssue
- * This is a list of (known) object types that are not handled correctly by this function:
- * - [`Blob`](https://developer.mozilla.org/docs/Web/API/Blob)
- * - [`MediaStream`](https://developer.mozilla.org/docs/Web/API/MediaStream)
- * - [`CanvasGradient`](https://developer.mozilla.org/docs/Web/API/CanvasGradient)
- * - AngularJS {@link $rootScope.Scope scopes};
- *
- * `angular.merge` also does not support merging objects with circular references.
- *
- * @param {Object} dst Destination object.
- * @param {...Object} src Source object(s).
- * @returns {Object} Reference to `dst`.
- */
-export function merge(dst: any, ...src: any[]): any;
 /**
  * @param {string} str
  * @returns {number}
@@ -361,7 +331,7 @@ export function sliceArgs(args: any, startIndex: any): any;
 export function bind(context: any, fn: any, ...args: any[]): Function;
 /**
  * Serializes input into a JSON-formatted string. Properties with leading $$ characters will be
- * stripped since AngularJS uses this notation internally.
+ * stripped since AngularTS uses this notation internally.
  *
  * @param {Object|Array|Date|string|number|boolean} obj Input to be serialized into JSON.
  * @param {boolean|number} [pretty=2] If set to true, the JSON output will contain newlines and whitespace.
@@ -483,7 +453,7 @@ export function errorHandlingConfig(
 ): ErrorHandlingConfig;
 /**
  * This object provides a utility for producing rich Error messages within
- * AngularJS. It can be called as follows:
+ * AngularTS. It can be called as follows:
  *
  * let exampleMinErr = minErr('example');
  * throw exampleMinErr('one', 'This {0} is {1}', foo, bar);
@@ -550,6 +520,21 @@ export function replaceInline(
   replacedElem: HTMLElement,
   newElem: HTMLElement,
 ): void;
+/**
+ * Checks whether the given object has the specified property as its own (not inherited).
+ *
+ * This is a safe version of `hasOwnProperty` that avoids issues with objects
+ * that have it overridden or missing from their prototype chain.
+ *
+ * @param {object} obj - The object to check.
+ * @param {string|number|symbol} key - The property key to look for.
+ * @returns {boolean} True if the object has the property as its own; otherwise, false.
+ *
+ * @example
+ * hasOwn({ foo: 123 }, 'foo'); // true
+ * hasOwn({}, 'bar'); // false
+ */
+export function hasOwn(obj: object, key: string | number | symbol): boolean;
 export const isProxySymbol: unique symbol;
 export const ngAttrPrefixes: string[];
 /**

package/CHANGELOG.md

@@ -1,4 +1,4 @@
-**AngularJS support has officially ended as of January 2022.
+**AngularTS support has officially ended as of January 2022.
 [See what ending support means](https://docs.angularjs.org/misc/version-support-status)
 and [read the end of life announcement](https://goo.gle/angularjs-end-of-life).**
 
@@ -8,7 +8,7 @@ and [read the end of life announcement](https://goo.gle/angularjs-end-of-life).*
 
 # 1.8.3 ultimate-farewell (2022-04-07)
 
-One final release of AngularJS in order to update package README files on npm.
+One final release of AngularTS in order to update package README files on npm.
 
 <a name="1.8.2"></a>
 
@@ -316,13 +316,13 @@ Note that this only patches jqLite. If you use jQuery 3.5.0 or newer, please rea
 # 1.7.2 extreme-compatiplication (2018-06-12)
 
 In the previous release, we removed a private, undocumented API that was no longer used by
-AngularJS. It turned out that several popular UI libraries (such as
-[AngularJS Material](https://material.angularjs.org/),
+AngularTS. It turned out that several popular UI libraries (such as
+[AngularTS Material](https://material.angularjs.org/),
 [UI Bootstrap](https://angular-ui.github.io/bootstrap/),
 [ngDialog](http://likeastore.github.io/ngDialog/) and probably others) relied on that API.
 
 In order to avoid unnecessary pain for developers, this release reverts the removal of the private
-API and restores compatibility of the aforementioned libraries with the latest AngularJS.
+API and restores compatibility of the aforementioned libraries with the latest AngularTS.
 
 ## Reverts
 
@@ -395,8 +395,8 @@ API and restores compatibility of the aforementioned libraries with the latest A
 **Here are the full changes for the release of 1.7.0 that are not already released in the 1.6.x branch,
 which includes commits from 1.7.0-rc.0 and commits from 1.7.0 directly.**
 
-1.7.0 is the last scheduled release of AngularJS that includes breaking changes. 1.7.x patch
-releases will continue to receive bug fixes and non-breaking features until AngularJS enters Long
+1.7.0 is the last scheduled release of AngularTS that includes breaking changes. 1.7.x patch
+releases will continue to receive bug fixes and non-breaking features until AngularTS enters Long
 Term Support mode (LTS) on July 1st 2018.
 
 ## Bug Fixes
@@ -785,7 +785,7 @@ under the hood, such as `angular.copy()`, `angular.equals()`,
 `angular.forEach()`, and `angular.merge()`.
 
 This in turn affects how dirty checking treats objects that prototypally
-inherit from `Array` (e.g. MobX observable arrays). AngularJS will now
+inherit from `Array` (e.g. MobX observable arrays). AngularTS will now
 be able to handle these objects better when copying or watching.
 
 ### **$sce** :
@@ -1070,9 +1070,9 @@ To migrate your code:
    don't have to do anything to migrate.
 
 2. If you specified `$compileProvider.preAssignBindingsEnabled(false)`, you
-   can remove that statement - since AngularJS 1.6.0 this is the default so your
-   app should still work even in AngularJS 1.6 after such removal. Afterwards,
-   migrating to AngularJS 1.7.0 shouldn't require any further action.
+   can remove that statement - since AngularTS 1.6.0 this is the default so your
+   app should still work even in AngularTS 1.6 after such removal. Afterwards,
+   migrating to AngularTS 1.7.0 shouldn't require any further action.
 
 3. If you specified `$compileProvider.preAssignBindingsEnabled(true)` you need
    to first migrate your code so that the flag can be flipped to `false`. The
@@ -1194,7 +1194,7 @@ The option to instantiate controllers from constructors on the global `window` o
 has been removed. Likewise, the deprecated `$controllerProvider.allowGlobals()`
 method that could enable this behavior, has been removed.
 
-This behavior had been deprecated since AngularJS v1.3.0, because polluting the global scope
+This behavior had been deprecated since AngularTS v1.3.0, because polluting the global scope
 is bad. To migrate, remove the call to $controllerProvider.allowGlobals() in the config, and
 register your controller via the Module API or the $controllerProvider, e.g.
 
@@ -1700,7 +1700,7 @@ under the hood, such as `angular.copy()`, `angular.equals()`,
 `angular.forEach()`, and `angular.merge()`.
 
 This in turn affects how dirty checking treats objects that prototypally
-inherit from `Array` (e.g. MobX observable arrays). AngularJS will now
+inherit from `Array` (e.g. MobX observable arrays). AngularTS will now
 be able to handle these objects better when copying or watching.
 
 ### **$sce** due to:
@@ -1955,9 +1955,9 @@ To migrate your code:
    don't have to do anything to migrate.
 
 2. If you specified `$compileProvider.preAssignBindingsEnabled(false)`, you
-   can remove that statement - since AngularJS 1.6.0 this is the default so your
-   app should still work even in AngularJS 1.6 after such removal. Afterwards,
-   migrating to AngularJS 1.7.0 shouldn't require any further action.
+   can remove that statement - since AngularTS 1.6.0 this is the default so your
+   app should still work even in AngularTS 1.6 after such removal. Afterwards,
+   migrating to AngularTS 1.7.0 shouldn't require any further action.
 
 3. If you specified `$compileProvider.preAssignBindingsEnabled(true)` you need
    to first migrate your code so that the flag can be flipped to `false`. The
@@ -2079,7 +2079,7 @@ The option to instantiate controllers from constructors on the global `window` o
 has been removed. Likewise, the deprecated `$controllerProvider.allowGlobals()`
 method that could enable this behavior, has been removed.
 
-This behavior had been deprecated since AngularJS v1.3.0, because polluting the global scope
+This behavior had been deprecated since AngularTS v1.3.0, because polluting the global scope
 is bad. To migrate, remove the call to $controllerProvider.allowGlobals() in the config, and
 register your controller via the Module API or the $controllerProvider, e.g.
 
@@ -2531,7 +2531,7 @@ $timeout.cancel(promise); // Timeout canceled.
 
 ## Bug Fixes
 
-- **AngularJS:**
+- **AngularTS:**
   - do not auto-bootstrap if the `src` exists but is empty
     ([3536e8](https://github.com/angular/angular.js/commit/3536e83d8a085b02bd6dcec8324800b7e6c734e4))
   - do not auto bootstrap if the currentScript has been clobbered
@@ -3097,7 +3097,7 @@ consolidating all the changes shown in the previous 1.6.0 release candidates.**
 
 Previously, `$compileProvider.preAssignBindingsEnabled` was set to true by default. This means
 bindings were pre-assigned on component/directive controller instances (which made them available
-inside the constructors). In AngularJS 1.5+ the place to put the initialization logic relying on
+inside the constructors). In AngularTS 1.5+ the place to put the initialization logic relying on
 bindings being present is the controller's `$onInit` method.
 
 To migrate follow the example below:
@@ -4297,7 +4297,7 @@ validation), you can overwrite the built-in `step` validator with a custom direc
 # 1.5.9 timeturning-lockdown (2016-11-24)
 
 This is an interim release primarily to publish some security fixes, in particular a modification to
-ensure that AngularJS can pass the linter checks for Mozilla add-ons.
+ensure that AngularTS can pass the linter checks for Mozilla add-ons.
 
 ## Security Fixes
 
@@ -4382,7 +4382,7 @@ ensure that AngularJS can pass the linter checks for Mozilla add-ons.
 
 Previously, `$compileProvider.preAssignBindingsEnabled` was
 set to true by default. This means bindings were pre-assigned in component
-constructors. In AngularJS 1.5+ the place to put the initialization logic
+constructors. In AngularTS 1.5+ the place to put the initialization logic
 relying on bindings being present is the controller `$onInit` method.
 
 To migrate follow the example below:
@@ -6375,7 +6375,7 @@ for more info.
 
 ### Upgrade to 1.5.1
 
-This version of AngularJS is problematic due to a issue during its release. Please upgrade to version [1.5.2](#1.5.2).
+This version of AngularTS is problematic due to a issue during its release. Please upgrade to version [1.5.2](#1.5.2).
 
 - **ngAria:** due to [d06431e5](https://github.com/angular/angular.js/commit/d06431e5309bb0125588877451dc79b935808134),
   Where appropriate, ngAria now applies ARIA to custom controls only, not native inputs. Because of this, support for `aria-multiline` on textareas has been removed.
@@ -6765,7 +6765,7 @@ returned unchanged (without throwing an error).
 
 # 1.5.0-rc.0 oblong-panoptikum (2015-12-09)
 
-This is the first Release Candidate for AngularJS 1.5.0. Please try upgrading your applications and
+This is the first Release Candidate for AngularTS 1.5.0. Please try upgrading your applications and
 report any regressions or other issues you find as soon as possible.
 
 ## Features
@@ -7465,12 +7465,12 @@ before the $parsers are applied. Previously, the modelValue
 
 This fixes issues where `input[date]` and `input[number]` cannot
 be validated because the viewValue string is parsed into
-`Date` and `Number` respectively (starting with AngularJS 1.3).
+`Date` and `Number` respectively (starting with AngularTS 1.3).
 It also brings the directives in line with HTML5 constraint
 validation, which validates against the input value.
 
 This change is unlikely to cause applications to fail, because even
-in AngularJS 1.2, the value that was validated by pattern could have
+in AngularTS 1.2, the value that was validated by pattern could have
 been manipulated by the $parsers, as all validation was done
 inside this pipeline.
 
@@ -7578,12 +7578,12 @@ before the $parsers are applied. Previously, the modelValue
 
 This fixes issues where `input[date]` and `input[number]` cannot
 be validated because the viewValue string is parsed into
-`Date` and `Number` respectively (starting with AngularJS 1.3).
+`Date` and `Number` respectively (starting with AngularTS 1.3).
 It also brings the directives in line with HTML5 constraint
 validation, which validates against the input value.
 
 This change is unlikely to cause applications to fail, because even
-in AngularJS 1.2, the value that was validated by pattern could have
+in AngularTS 1.2, the value that was validated by pattern could have
 been manipulated by the $parsers, as all validation was done
 inside this pipeline.
 
@@ -7793,7 +7793,7 @@ describe("$q.when", function () {
     $timeout,
   ) {
     $q.when("foo");
-    // In AngularJS 1.4.3 a call to `$timeout.flush();` was needed
+    // In AngularTS 1.4.3 a call to `$timeout.flush();` was needed
     $timeout.verifyNoPendingTasks();
   }));
 
@@ -8734,12 +8734,12 @@ place the element containing the ngMessagesInclude directive at the
 end of the container containing the ngMessages directive).
 
 ```html
-<!-- AngularJS 1.3.x -->
+<!-- AngularTS 1.3.x -->
 <div ng-messages="model.$error" ng-messages-include="remote.html">
   <div ng-message="required">Your message is required</div>
 </div>
 
-<!-- AngularJS 1.4.x -->
+<!-- AngularTS 1.4.x -->
 <div ng-messages="model.$error">
   <div ng-message="required">Your message is required</div>
   <div ng-messages-include="remote.html"></div>
@@ -9205,7 +9205,7 @@ it is now implemented in the ngOptions directive itself.
 the `select` directive will now use strict comparison of the `ngModel` scope value against `option`
 values to determine which option is selected. This means `Number` scope values will not be matched
 against numeric option strings.
-In AngularJS 1.3.x, setting `scope.x = 200` would select the `option` with the value 200 in the following `select`:
+In AngularTS 1.3.x, setting `scope.x = 200` would select the `option` with the value 200 in the following `select`:
 
 ```
 <select ng-model="x">
@@ -9214,7 +9214,7 @@ In AngularJS 1.3.x, setting `scope.x = 200` would select the `option` with the v
 </select>
 ```
 
-In AngularJS 1.4.x, the 'unknown option' will be selected.
+In AngularTS 1.4.x, the 'unknown option' will be selected.
 To remedy this, you can simply initialize the model as a string: `scope.x = '200'`, or if you want to
 keep the model as a `Number`, you can do the conversion via `$formatters` and `$parsers` on `ngModel`:
 
@@ -9672,7 +9672,7 @@ bind a getter/getter to the global context, or just reference globals normally w
 ## Breaking Changes
 
 - **$parse:** due to [fbad2805](https://github.com/angular/angular.js/commit/fbad2805703569058a4a860747b0e2d8aee36bdf),
-  you can't use characters that have special meaning in AngularJS expressions (ex.: `.` or `-`)
+  you can't use characters that have special meaning in AngularTS expressions (ex.: `.` or `-`)
   as part of filter's name. Before this commit custom filters could contain special characters
   (like a dot) in their name but this wasn't intentional.
 
@@ -15701,7 +15701,7 @@ _Note: This release also contains all bug fixes available in [1.0.3](#1.0.3)._
 - **jqLite:**
   - support append on document fragment
     ([96ed9ff5](https://github.com/angular/angular.js/commit/96ed9ff59a454486c88bdf92ad9d28ab8864b85e))
-  - fire $destroy event via triggerHandler (this makes AngularJS compatible with **jQuery 1.8.x**)
+  - fire $destroy event via triggerHandler (this makes AngularTS compatible with **jQuery 1.8.x**)
     ([b9a9f91f](https://github.com/angular/angular.js/commit/b9a9f91fbf99b71cfde434b6277f4c7d2533556f),
     [#1512](https://github.com/angular/angular.js/issues/1512))
 - **Filters**
@@ -15807,7 +15807,7 @@ This release also contains all bug fixes available in [1.0.2](#1.0.2).
 
 ## Docs
 
-- Conceptual Overview of AngularJS (high level overview of how things work):
+- Conceptual Overview of AngularTS (high level overview of how things work):
   <http://docs.angularjs.org/guide/concepts>
   ([7a5f25f6](https://github.com/angular/angular.js/commit/7a5f25f6671eb5f51b06615d74a05855ab79f31e))
 - Lots of spelling, grammar and other fixes:
@@ -16103,7 +16103,7 @@ This release also contains all bug fixes available in [1.0.2](#1.0.2).
 
 ## Docs
 
-- Tutorial has been finally updated to AngularJS v1.0! Check it out and provide feedback to make it
+- Tutorial has been finally updated to AngularTS v1.0! Check it out and provide feedback to make it
   even better: <http://docs.angularjs.org/tutorial>
 - <http://docs-next.angularjs.org> now redirects to <http://docs.angularjs.org>
 
@@ -16900,7 +16900,7 @@ behavior and migrate your controllers one at a time: <https://gist.github.com/16
 ## Breaking Changes
 
 - $location related changes - for complete list of api changes see:
-  [Migrating from earlier AngularJS releases](http://docs-next.angularjs.org/#!/guide/dev_guide.services.$location)
+  [Migrating from earlier AngularTS releases](http://docs-next.angularjs.org/#!/guide/dev_guide.services.$location)
 
   - $location api changes:
 
@@ -17538,7 +17538,7 @@ behavior and migrate your controllers one at a time: <https://gist.github.com/16
 ### Breaking changes
 
 - we now support ISO 8601 extended format datetime strings (YYYY-MM-DDTHH:mm:ss.SSSZ) as defined
-  in EcmaScript 5 throughout AngularJS. This means that the following apis switched from
+  in EcmaScript 5 throughout AngularTS. This means that the following apis switched from
   YYYY-MM-DDTHH:mm:ssZ to YYYY-MM-DDTHH:mm:ss.SSSZ (note the added millis) when representing dates:
   - angular.Date.toString
   - angular.String.fromDate

package/CODE_OF_CONDUCT.md

@@ -1,3 +1,3 @@
 # Contributor Code of Conduct
 
-The AngularJS project follows the Code of Conduct defined in [the angular/code-of-conduct repository](https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md). Please read it.
+The AngularTS project follows the Code of Conduct defined in [the angular/code-of-conduct repository](https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md). Please read it.

package/CONTRIBUTING.md

@@ -1,6 +1,6 @@
-# Contributing to AngularJS
+# Contributing to AngularTS
 
-We'd love for you to contribute to our source code and to make AngularJS even better than it is
+We'd love for you to contribute to our source code and to make AngularTS even better than it is
 today! Here are the guidelines we'd like you to follow:
 
 - [Code of Conduct](#coc)
@@ -14,7 +14,7 @@ today! Here are the guidelines we'd like you to follow:
 
 ## <a name="coc"></a> Code of Conduct
 
-Help us keep AngularJS open and inclusive. Please read and follow our [Code of Conduct][coc].
+Help us keep AngularTS open and inclusive. Please read and follow our [Code of Conduct][coc].
 
 ## <a name="requests"></a> Questions, Bugs, Features
 
@@ -37,8 +37,8 @@ support and redirect people to the section you are reading right now.
 Other channels for support are:
 
 - the [Google Group][groups] discussion list
-- the [AngularJS IRC][irc]
-- the [AngularJS Gitter][gitter]
+- the [AngularTS IRC][irc]
+- the [AngularTS Gitter][gitter]
 
 ### <a name="issue"></a> Found an Issue or Bug?
 
@@ -47,7 +47,7 @@ If you find a bug in the source code, you can help us by submitting an issue to
 
 **Please see the [Submission Guidelines](#submit) below.**
 
-**Special Note for Localization Issues:** AngularJS uses the [Google Closure I18N library] to
+**Special Note for Localization Issues:** AngularTS uses the [Google Closure I18N library] to
 generate its own I18N files (the ngLocale module). This means that any changes to these files
 would be lost the next time that we import the library.
 Since the Closure library i18n data is itself auto-generated from the data of the
@@ -99,7 +99,7 @@ with quickly:
 
 - **Overview of the Issue** - if an error is being thrown a non-minified stack trace helps
 - **Motivation for or Use Case** - explain why this is a bug for you
-- **AngularJS Version(s)** - is it a regression?
+- **AngularTS Version(s)** - is it a regression?
 - **Browsers and Operating System** - is this a problem with all browsers or only specific ones?
 - **Reproduce the Error** - provide a live example (using [Plunker][plunker] or
   [JSFiddle][jsfiddle]) or an unambiguous set of steps.
@@ -127,7 +127,7 @@ Before you submit your pull request consider the following guidelines:
 - Create your patch commit, **including appropriate test cases**.
 - Follow our [Coding Rules][developers.rules].
 - If the changes affect public APIs, change or add relevant [documentation][developers.documentation].
-- Run the AngularJS [unit][developers.tests-unit] and [E2E test][developers.tests-e2e] suites, and ensure that all tests
+- Run the AngularTS [unit][developers.tests-unit] and [E2E test][developers.tests-e2e] suites, and ensure that all tests
   pass. It is generally sufficient to run the tests only on Chrome, as our continuous integration test will
   run the tests on additional browsers.
 - Run `yarn grunt eslint` to check that you have followed the automatically enforced coding rules
@@ -165,7 +165,7 @@ Before you submit your pull request consider the following guidelines:
 - If we suggest changes, then:
 
   - Make the required updates.
-  - Re-run the AngularJS test suite to ensure tests are still passing.
+  - Re-run the AngularTS test suite to ensure tests are still passing.
   - Commit your changes to your branch (e.g. `my-fix-branch`).
   - Push the changes to your GitHub repository (this will update your Pull Request).