honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/packages/core/schematics/BUILD.bazel

32 lines
1.4 KiB
Python
Raw Normal View History

build: upgrade to rules_nodejs 1.0.0 (first stable release) (#34736) Brings in the fix for stamping which was preventing many targets from getting cached. PR Close #34736
2019-12-28 19:37:59 -05:00
load("//tools:defaults.bzl", "pkg_npm")
feat(core): update schematic to migrate to explicit query timing (#28983) Introduces an update schematic for the "@angular/core" package that automatically migrates pre-V8 "ViewChild" and "ContentChild" queries to the new explicit timing syntax. This is not required yet, but with Ivy, queries will be "dynamic" by default. Therefore specifying an explicit query timing ensures that developers can smoothly migrate to Ivy (once it's the default). Read more about the explicit timing API here: https://github.com/angular/angular/pull/28810 PR Close #28983
2019-02-27 14:30:38 -05:00
exports_files([
"tsconfig.json",
"migrations.json",
])
build: upgrade to rules_nodejs 1.0.0 (first stable release) (#34736) Brings in the fix for stamping which was preventing many targets from getting cached. PR Close #34736
2019-12-28 19:37:59 -05:00
pkg_npm(
feat(core): update schematic to migrate to explicit query timing (#28983) Introduces an update schematic for the "@angular/core" package that automatically migrates pre-V8 "ViewChild" and "ContentChild" queries to the new explicit timing syntax. This is not required yet, but with Ivy, queries will be "dynamic" by default. Therefore specifying an explicit query timing ensures that developers can smoothly migrate to Ivy (once it's the default). Read more about the explicit timing API here: https://github.com/angular/angular/pull/28810 PR Close #28983
2019-02-27 14:30:38 -05:00
name = "npm_package",
srcs = ["migrations.json"],
visibility = ["//packages/core:__pkg__"],
fix(core): add missing migration to npm package (#29705) While running `ng update @angular/core --next`, the following error would be displayed: ``` Cannot find module '....\node_modules\@angular\core\schematics\migrations\template-var-assignment\index' ``` This happened because the Schematics migration was referenced, but not included. This commit fixes that bug by including the migration in the Bazel npm package dependencies. PR Close #29705
2019-04-04 05:18:28 -04:00
deps = [
feat(forms): add migration for AbstractControl.parent accesses (#39009) As of #32671, the type of `AbstractControl.parent` can be null which can cause compilation errors in existing apps. These changes add a migration that will append non-null assertions to existing unsafe accesses. ```` // Before console.log(control.parent.value); // After console.log(control.parent!.value); ``` The migration also tries its best to avoid cases where the non-null assertions aren't necessary (e.g. if the `parent` was null checked already). PR Close #39009
2020-09-26 14:35:25 -04:00
"//packages/core/schematics/migrations/abstract-control-parent",
feat(core): Add schematic to fix invalid `Route` configs (#40067) `Route` configs with `redirectTo` as well as `canActivate` are not valid because the `canActivate` guards will never execute. Redirects are applied before activation. There is no error currently for these configs, but another commit will change this so that an error does appear in dev mode. This migration fixes the configs by removing the `canActivate` property. PR Close #40067
2020-12-11 20:16:54 -05:00
"//packages/core/schematics/migrations/can-activate-with-redirect-to",
feat(core): add dynamic queries schematic (#32231) Adds a schematic that will remove the explicit `static: false` flag from dynamic queries. E.g. ```ts import { Directive, ViewChild, ContentChild, ElementRef } from '@angular/core'; @Directive() export class MyDirective { @ViewChild('child', { static: false }) child: any; @ViewChild('secondChild', { read: ElementRef, static: false }) secondChild: ElementRef; @ContentChild('thirdChild', { static: false }) thirdChild: any; } ``` ```ts import { Directive, ViewChild, ContentChild, ElementRef } from '@angular/core'; @Directive() export class MyDirective { @ViewChild('child') child: any; @ViewChild('secondChild', { read: ElementRef }) secondChild: ElementRef; @ContentChild('thirdChild') thirdChild: any; } ``` PR Close #32231
2019-08-21 01:40:30 -04:00
"//packages/core/schematics/migrations/dynamic-queries",
feat(core): add initialNavigation schematic (#36926) Add a schematic to update users to the new v11 `initialNavigation` options for `RouterModule`. This replaces the deprecated/removed `true`, `false`, `legacy_disabled`, and `legacy_enabled` options with the newer `enabledBlocking` and `enabledNonBlocking` options. PR Close #36926
2019-10-13 00:25:58 -04:00
"//packages/core/schematics/migrations/initial-navigation",
refactor(core): wire up missing-injectable migration for ng-update (#32349) Initially the `missing-injectable` migration was only being used in google3. Wiring the migration up in the CLI migrations was planned to be done in a follow-up. PR Close #32349
2019-08-27 09:09:09 -04:00
"//packages/core/schematics/migrations/missing-injectable",
feat(core): add ModuleWithProviders generic type migration (#33217) Static methods that return a type of ModuleWithProviders currently do not have to specify a type because the generic falls back to any. This is problematic because the type of the actual module being returned is not present in the type information. Since Ivy uses d.ts files exclusively for downstream packages (rather than metadata.json files, for example), we no longer have the type of the actual module being created. For this reason, a generic type should be added for ModuleWithProviders that specifies the module type. This will be required for all users in v10, but will only be necessary for users of Ivy in v9. PR Close #33217
2019-10-17 02:40:36 -04:00
"//packages/core/schematics/migrations/module-with-providers",
feat(core): add schematics to move deprecated DOCUMENT import (#29950) PR Close #29950
2019-04-17 00:06:06 -04:00
"//packages/core/schematics/migrations/move-document",
feat(core): add automated migration to replace ViewEncapsulation.Native (#38882) Adds an automated migration that replaces any usages of the deprecated `ViewEncapsulation.Native` with `ViewEncapsulation.ShadowDom`. PR Close #38882
2020-09-17 09:12:08 -04:00
"//packages/core/schematics/migrations/native-view-encapsulation",
feat(router): add migration to update calls to navigateByUrl and createUrlTree with invalid parameters (#38825) In #38227 the signatures of `navigateByUrl` and `createUrlTree` were updated to exclude unsupported properties from their `extras` parameter. This migration looks for the relevant method calls that pass in an `extras` parameter and drops the unsupported properties. **Before:** ``` this._router.navigateByUrl('/', {skipLocationChange: false, fragment: 'foo'}); ``` **After:** ``` this._router.navigateByUrl('/', { /* Removed unsupported properties by Angular migration: fragment. */ skipLocationChange: false }); ``` These changes also move the method call detection logic out of the `Renderer2` migration and into a common place so that it can be reused in other migrations. PR Close #38825
2020-09-12 08:33:06 -04:00
"//packages/core/schematics/migrations/navigation-extras-omissions",
feat(router): Add `relativeLinkResolution` migration to update default value (#38698) The default value for `relativeLinkResolution` is changing from 'legacy' to 'corrected'. This migration updates `RouterModule` configurations that use the default value to now specifically use 'legacy' to prevent breakages when updating. PR Close #38698
2020-06-05 22:40:13 -04:00
"//packages/core/schematics/migrations/relative-link-resolution",
feat(core): add automatic migration from Renderer to Renderer2 (#30936) Adds a schematic and tslint rule that automatically migrate the consumer from `Renderer` to `Renderer2`. Supports: * Renaming imports. * Renaming property and method argument types. * Casting to `Renderer`. * Mapping all of the methods from the `Renderer` to `Renderer2`. Note that some of the `Renderer` methods don't map cleanly between renderers. In these cases the migration adds a helper function at the bottom of the file which ensures that we generate valid code with the same return value as before. E.g. here's what the migration for `createText` looks like. Before: ``` class SomeComponent { createAndAddText() { const node = this._renderer.createText(this._element.nativeElement, 'hello'); node.textContent += ' world'; } } ``` After: ``` class SomeComponent { createAndAddText() { const node = __rendererCreateTextHelper(this._renderer, this._element.nativeElement, 'hello'); node.textContent += ' world'; } } function __rendererCreateTextHelper(renderer: any, parent: any, value: any) { const node = renderer.createText(value); if (parent) { renderer.appendChild(parent, node); } return node; } ``` This PR resolves FW-1344. PR Close #30936
2019-06-09 09:38:18 -04:00
"//packages/core/schematics/migrations/renderer-to-renderer2",
fix(router): create schematic for preserveQueryParams (#38762) Create a schematic for migrating preserveQueryParams to use queryParamsHandler instead. PR Close #38762
2020-10-12 14:13:57 -04:00
"//packages/core/schematics/migrations/router-preserve-query-params",
fix(core): add missing migration to npm package (#29705) While running `ng update @angular/core --next`, the following error would be displayed: ``` Cannot find module '....\node_modules\@angular\core\schematics\migrations\template-var-assignment\index' ``` This happened because the Schematics migration was referenced, but not included. This commit fixes that bug by including the migration in the Bazel npm package dependencies. PR Close #29705
2019-04-04 05:18:28 -04:00
"//packages/core/schematics/migrations/static-queries",
"//packages/core/schematics/migrations/template-var-assignment",
feat(core): add undecorated classes with decorated fields schematic (#32130) Adds a schematic that adds a `Directive` decorator to undecorated classes that have fields that use Angular decorators. PR Close #32130
2019-08-15 05:40:53 -04:00
"//packages/core/schematics/migrations/undecorated-classes-with-decorated-fields",
feat(core): add undecorated classes migration schematic (#31650) Introduces a new migration schematic that follows the given migration plan: https://hackmd.io/@alx/S1XKqMZeS. First case: The schematic detects decorated directives which inherit a constructor. The migration ensures that all base classes until the class with the explicit constructor are properly decorated with "@Directive()" or "@Component". In case one of these classes is not decorated, the schematic adds the abstract "@Directive()" decorator automatically. Second case: The schematic detects undecorated declarations and copies the inherited "@Directive()", "@Component" or "@Pipe" decorator to the undecorated derived class. This involves non-trivial import rewriting, identifier aliasing and AOT metadata serializing (as decorators are not always part of source files) PR Close #31650
2019-07-24 06:07:07 -04:00
"//packages/core/schematics/migrations/undecorated-classes-with-di",
feat(core): add automated migration to replace async with waitForAsync (#39212) Adds a migration that finds all imports and calls to the deprecated `async` function from `@angular/core/testing` and replaces them with `waitForAsync`. These changes also move a bit of code out of the `Renderer2` migration so that it can be reused. PR Close #39212
2020-10-12 12:07:34 -04:00
"//packages/core/schematics/migrations/wait-for-async",
fix(core): add missing migration to npm package (#29705) While running `ng update @angular/core --next`, the following error would be displayed: ``` Cannot find module '....\node_modules\@angular\core\schematics\migrations\template-var-assignment\index' ``` This happened because the Schematics migration was referenced, but not included. This commit fixes that bug by including the migration in the Bazel npm package dependencies. PR Close #29705
2019-04-04 05:18:28 -04:00
],
feat(core): update schematic to migrate to explicit query timing (#28983) Introduces an update schematic for the "@angular/core" package that automatically migrates pre-V8 "ViewChild" and "ContentChild" queries to the new explicit timing syntax. This is not required yet, but with Ivy, queries will be "dynamic" by default. Therefore specifying an explicit query timing ensures that developers can smoothly migrate to Ivy (once it's the default). Read more about the explicit timing API here: https://github.com/angular/angular/pull/28810 PR Close #28983
2019-02-27 14:30:38 -05:00
)