@angular/upgrade 14.0.0-next.13 → 14.0.0-next.16

package/static/testing/{testing.d.ts → index.d.ts}

@@ -1,146 +1,147 @@
 /**
- * @license Angular v14.0.0-next.13
+ * @license Angular v14.0.0-next.16
  * (c) 2010-2022 Google LLC. https://angular.io/
  * License: MIT
  */
 
-import { Type } from '@angular/core';
-
-
-/**
- * A helper function to use when unit testing AngularJS services that depend upon downgraded Angular
- * services.
- *
- * This function returns an AngularJS module that is configured to wire up the AngularJS and Angular
- * injectors without the need to actually bootstrap a hybrid application.
- * This makes it simpler and faster to unit test services.
- *
- * Use the returned AngularJS module in a call to
- * [`angular.mocks.module`](https://docs.angularjs.org/api/ngMock/function/angular.mock.module) to
- * include this module in the unit test injector.
- *
- * In the following code snippet, we are configuring the `$injector` with two modules:
- * The AngularJS `ng1AppModule`, which is the AngularJS part of our hybrid application and the
- * `Ng2AppModule`, which is the Angular part.
- *
- * <code-example path="upgrade/static/ts/full/module.spec.ts"
- * region="angularjs-setup"></code-example>
- *
- * Once this is done we can get hold of services via the AngularJS `$injector` as normal.
- * Services that are (or have dependencies on) a downgraded Angular service, will be instantiated as
- * needed by the Angular root `Injector`.
- *
- * In the following code snippet, `heroesService` is a downgraded Angular service that we are
- * accessing from AngularJS.
- *
- * <code-example path="upgrade/static/ts/full/module.spec.ts"
- * region="angularjs-spec"></code-example>
- *
- * <div class="alert is-important">
- *
- * This helper is for testing services not components.
- * For Component testing you must still bootstrap a hybrid app. See `UpgradeModule` or
- * `downgradeModule` for more information.
- *
- * </div>
- *
- * <div class="alert is-important">
- *
- * The resulting configuration does not wire up AngularJS digests to Zone hooks. It is the
- * responsibility of the test writer to call `$rootScope.$apply`, as necessary, to trigger
- * AngularJS handlers of async events from Angular.
- *
- * </div>
- *
- * <div class="alert is-important">
- *
- * The helper sets up global variables to hold the shared Angular and AngularJS injectors.
- *
- * * Only call this helper once per spec.
- * * Do not use `createAngularJSTestingModule` in the same spec as `createAngularTestingModule`.
- *
- * </div>
- *
- * Here is the example application and its unit tests that use `createAngularTestingModule`
- * and `createAngularJSTestingModule`.
- *
- * <code-tabs>
- *  <code-pane header="module.spec.ts" path="upgrade/static/ts/full/module.spec.ts"></code-pane>
- *  <code-pane header="module.ts" path="upgrade/static/ts/full/module.ts"></code-pane>
- * </code-tabs>
- *
- *
- * @param angularModules a collection of Angular modules to include in the configuration.
- *
- * @publicApi
- */
-export declare function createAngularJSTestingModule(angularModules: any[]): string;
-
-/**
- * A helper function to use when unit testing Angular services that depend upon upgraded AngularJS
- * services.
- *
- * This function returns an `NgModule` decorated class that is configured to wire up the Angular
- * and AngularJS injectors without the need to actually bootstrap a hybrid application.
- * This makes it simpler and faster to unit test services.
- *
- * Use the returned class as an "import" when configuring the `TestBed`.
- *
- * In the following code snippet, we are configuring the TestBed with two imports.
- * The `Ng2AppModule` is the Angular part of our hybrid application and the `ng1AppModule` is the
- * AngularJS part.
- *
- * <code-example path="upgrade/static/ts/full/module.spec.ts" region="angular-setup"></code-example>
- *
- * Once this is done we can get hold of services via the Angular `Injector` as normal.
- * Services that are (or have dependencies on) an upgraded AngularJS service, will be instantiated
- * as needed by the AngularJS `$injector`.
- *
- * In the following code snippet, `HeroesService` is an Angular service that depends upon an
- * AngularJS service, `titleCase`.
- *
- * <code-example path="upgrade/static/ts/full/module.spec.ts" region="angular-spec"></code-example>
- *
- * <div class="alert is-important">
- *
- * This helper is for testing services not Components.
- * For Component testing you must still bootstrap a hybrid app. See `UpgradeModule` or
- * `downgradeModule` for more information.
- *
- * </div>
- *
- * <div class="alert is-important">
- *
- * The resulting configuration does not wire up AngularJS digests to Zone hooks. It is the
- * responsibility of the test writer to call `$rootScope.$apply`, as necessary, to trigger
- * AngularJS handlers of async events from Angular.
- *
- * </div>
- *
- * <div class="alert is-important">
- *
- * The helper sets up global variables to hold the shared Angular and AngularJS injectors.
- *
- * * Only call this helper once per spec.
- * * Do not use `createAngularTestingModule` in the same spec as `createAngularJSTestingModule`.
- *
- * </div>
- *
- * Here is the example application and its unit tests that use `createAngularTestingModule`
- * and `createAngularJSTestingModule`.
- *
- * <code-tabs>
- *  <code-pane header="module.spec.ts" path="upgrade/static/ts/full/module.spec.ts"></code-pane>
- *  <code-pane header="module.ts" path="upgrade/static/ts/full/module.ts"></code-pane>
- * </code-tabs>
- *
- *
- * @param angularJSModules a collection of the names of AngularJS modules to include in the
- * configuration.
- * @param [strictDi] whether the AngularJS injector should have `strictDI` enabled.
- *
- * @publicApi
- */
-export declare function createAngularTestingModule(angularJSModules: string[], strictDi?: boolean): Type<any>;
-
-export { }
+
+import { Type } from '@angular/core';
+
+
+/**
+ * A helper function to use when unit testing AngularJS services that depend upon downgraded Angular
+ * services.
+ *
+ * This function returns an AngularJS module that is configured to wire up the AngularJS and Angular
+ * injectors without the need to actually bootstrap a hybrid application.
+ * This makes it simpler and faster to unit test services.
+ *
+ * Use the returned AngularJS module in a call to
+ * [`angular.mocks.module`](https://docs.angularjs.org/api/ngMock/function/angular.mock.module) to
+ * include this module in the unit test injector.
+ *
+ * In the following code snippet, we are configuring the `$injector` with two modules:
+ * The AngularJS `ng1AppModule`, which is the AngularJS part of our hybrid application and the
+ * `Ng2AppModule`, which is the Angular part.
+ *
+ * <code-example path="upgrade/static/ts/full/module.spec.ts"
+ * region="angularjs-setup"></code-example>
+ *
+ * Once this is done we can get hold of services via the AngularJS `$injector` as normal.
+ * Services that are (or have dependencies on) a downgraded Angular service, will be instantiated as
+ * needed by the Angular root `Injector`.
+ *
+ * In the following code snippet, `heroesService` is a downgraded Angular service that we are
+ * accessing from AngularJS.
+ *
+ * <code-example path="upgrade/static/ts/full/module.spec.ts"
+ * region="angularjs-spec"></code-example>
+ *
+ * <div class="alert is-important">
+ *
+ * This helper is for testing services not components.
+ * For Component testing you must still bootstrap a hybrid app. See `UpgradeModule` or
+ * `downgradeModule` for more information.
+ *
+ * </div>
+ *
+ * <div class="alert is-important">
+ *
+ * The resulting configuration does not wire up AngularJS digests to Zone hooks. It is the
+ * responsibility of the test writer to call `$rootScope.$apply`, as necessary, to trigger
+ * AngularJS handlers of async events from Angular.
+ *
+ * </div>
+ *
+ * <div class="alert is-important">
+ *
+ * The helper sets up global variables to hold the shared Angular and AngularJS injectors.
+ *
+ * * Only call this helper once per spec.
+ * * Do not use `createAngularJSTestingModule` in the same spec as `createAngularTestingModule`.
+ *
+ * </div>
+ *
+ * Here is the example application and its unit tests that use `createAngularTestingModule`
+ * and `createAngularJSTestingModule`.
+ *
+ * <code-tabs>
+ *  <code-pane header="module.spec.ts" path="upgrade/static/ts/full/module.spec.ts"></code-pane>
+ *  <code-pane header="module.ts" path="upgrade/static/ts/full/module.ts"></code-pane>
+ * </code-tabs>
+ *
+ *
+ * @param angularModules a collection of Angular modules to include in the configuration.
+ *
+ * @publicApi
+ */
+export declare function createAngularJSTestingModule(angularModules: any[]): string;
+
+/**
+ * A helper function to use when unit testing Angular services that depend upon upgraded AngularJS
+ * services.
+ *
+ * This function returns an `NgModule` decorated class that is configured to wire up the Angular
+ * and AngularJS injectors without the need to actually bootstrap a hybrid application.
+ * This makes it simpler and faster to unit test services.
+ *
+ * Use the returned class as an "import" when configuring the `TestBed`.
+ *
+ * In the following code snippet, we are configuring the TestBed with two imports.
+ * The `Ng2AppModule` is the Angular part of our hybrid application and the `ng1AppModule` is the
+ * AngularJS part.
+ *
+ * <code-example path="upgrade/static/ts/full/module.spec.ts" region="angular-setup"></code-example>
+ *
+ * Once this is done we can get hold of services via the Angular `Injector` as normal.
+ * Services that are (or have dependencies on) an upgraded AngularJS service, will be instantiated
+ * as needed by the AngularJS `$injector`.
+ *
+ * In the following code snippet, `HeroesService` is an Angular service that depends upon an
+ * AngularJS service, `titleCase`.
+ *
+ * <code-example path="upgrade/static/ts/full/module.spec.ts" region="angular-spec"></code-example>
+ *
+ * <div class="alert is-important">
+ *
+ * This helper is for testing services not Components.
+ * For Component testing you must still bootstrap a hybrid app. See `UpgradeModule` or
+ * `downgradeModule` for more information.
+ *
+ * </div>
+ *
+ * <div class="alert is-important">
+ *
+ * The resulting configuration does not wire up AngularJS digests to Zone hooks. It is the
+ * responsibility of the test writer to call `$rootScope.$apply`, as necessary, to trigger
+ * AngularJS handlers of async events from Angular.
+ *
+ * </div>
+ *
+ * <div class="alert is-important">
+ *
+ * The helper sets up global variables to hold the shared Angular and AngularJS injectors.
+ *
+ * * Only call this helper once per spec.
+ * * Do not use `createAngularTestingModule` in the same spec as `createAngularJSTestingModule`.
+ *
+ * </div>
+ *
+ * Here is the example application and its unit tests that use `createAngularTestingModule`
+ * and `createAngularJSTestingModule`.
+ *
+ * <code-tabs>
+ *  <code-pane header="module.spec.ts" path="upgrade/static/ts/full/module.spec.ts"></code-pane>
+ *  <code-pane header="module.ts" path="upgrade/static/ts/full/module.ts"></code-pane>
+ * </code-tabs>
+ *
+ *
+ * @param angularJSModules a collection of the names of AngularJS modules to include in the
+ * configuration.
+ * @param [strictDi] whether the AngularJS injector should have `strictDI` enabled.
+ *
+ * @publicApi
+ */
+export declare function createAngularTestingModule(angularJSModules: string[], strictDi?: boolean): Type<any>;
+
+export { }

package/static/package.json

@@ -1,10 +0,0 @@
-{
-  "name": "@angular/upgrade/static",
-  "sideEffects": false,
-  "fesm2020": "../fesm2020/static.mjs",
-  "fesm2015": "../fesm2015/static.mjs",
-  "esm2020": "../esm2020/static/static.mjs",
-  "typings": "./static.d.ts",
-  "module": "../fesm2015/static.mjs",
-  "es2020": "../fesm2020/static.mjs"
-}

package/static/testing/package.json

@@ -1,9 +0,0 @@
-{
-  "name": "@angular/upgrade/static/testing",
-  "fesm2020": "../../fesm2020/static/testing.mjs",
-  "fesm2015": "../../fesm2015/static/testing.mjs",
-  "esm2020": "../../esm2020/static/testing/testing.mjs",
-  "typings": "./testing.d.ts",
-  "module": "../../fesm2015/static/testing.mjs",
-  "es2020": "../../fesm2020/static/testing.mjs"
-}