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

37 lines
1.3 KiB
Python
Raw Normal View History

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
load("//tools:defaults.bzl", "jasmine_node_test", "ts_library")
ts_library(
name = "test_lib",
testonly = True,
srcs = glob(["**/*.ts"]),
data = [
test(core): run schematic tests with public migration collection (#30198) 572b54967c969c88c61970650fb857afc1d74f8a changed how the schematic tests are executed. Tests no longer use the schematic collection that is also used by the CLI `ng update` command and therefore the migration collection could technically be invalid. In order to ensure that the public migration collection is guaranteed to work and to avoid duplication within two schematic collections, the changes are partially reverted and only the disabled `injectable-pipe` schematic has its own collection. PR Close #30198
2019-04-29 15:17:03 -04:00
"//packages/core/schematics:migrations.json",
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
],
deps = [
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(ivy): introduce missing-injectable migration for google3 (#30956) Introduces a new migration schematic for adding the "@Injectable()" decorator to provider classes which are currently not migrated. Previously in ViewEngine, classes which are declared as providers sometimes don't require the "@Injectable()" decorator (e.g. https://stackblitz.com/edit/angular-hpo7gw) With Ivy, provider classes need to be explicitly decorated with the "@Injectable()" decorator if they are declared as providers of a given module. This commit introduces a migration schematic which automatically adds the explicit decorator to places where the decorator is currently missing. The migration logic is designed in a CLI devkit and TSlint agnostic way so that we can also have this migration run as part of a public CLI migration w/ `ng update`. This will be handled as part of a follow-up to reiterate on console output etc. Resolves FW-1371 PR Close #30956
2019-06-10 13:08:54 -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(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",
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
"//packages/core/schematics/migrations/static-queries",
feat(core): template-var-assignment update schematic (#29608) Introduces a new update schematic called "template-var-assignment" that is responsible for analyzing template files in order to warn developers if template variables are assigned to values. The schematic also comes with a driver for `tslint` so that the check can be used wtihin Google. PR Close #29608
2019-03-30 07:48:21 -04:00
"//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): 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
"//packages/core/schematics/utils",
build: update rules_nodejs and clean up bazel warnings (#30370) Preserve compatibility with rollup_bundle rule. Add missing npm dependencies, which are now enforced by the strict_deps plugin in tsc_wrapped PR Close #30370
2019-05-09 17:51:51 -04:00
"@npm//@angular-devkit/core",
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
"@npm//@angular-devkit/schematics",
"@npm//@types/shelljs",
refactor(core): add tslint rule entry-point for static-query migration (#29258) In order to be able to use the static-query migration logic within Google, we need to provide a TSLint rule entry-point that wires up the schematic logic and provides reporting and automatic fixes. PR Close #29258
2019-03-13 11:29:25 -04:00
"@npm//tslint",
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
],
)
jasmine_node_test(
test(core): cleanup bazel target names for schematic tests (#32318) Apparently the names of the bazel test targets in the schematics are incorrect. This commit updates the target names to match their bazel package name. PR Close #32318
2019-08-26 10:12:44 -04:00
name = "test",
build(bazel): fix deps of test (#29799) PR Close #29799
2019-04-10 00:13:14 -04:00
deps = [
":test_lib",
"@npm//shelljs",
],
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
)