angular-cn/packages/core/schematics/tsconfig.json

{
  "compilerOptions": {
    "noImplicitReturns": true,
    "noFallthroughCasesInSwitch": true,
    "strict": true,
    "lib": ["es2015"],
    "types": [],
    "baseUrl": ".",
    "paths": {
      "@angular/core": ["../"],
      "@angular/compiler": ["../../compiler"],
      "@angular/compiler/*": ["../../compiler/*"],
      "@angular/compiler-cli": ["../../compiler-cli"],
      "@angular/compiler-cli/*": ["../../compiler-cli/*"]
    }
  },
  "bazelOptions": {
    "suppressTsconfigOverrideWarnings": true
  }
}
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 20:30:38 +01:00			`{`
			`"compilerOptions": {`
			`"noImplicitReturns": true,`
fix(core): resolve ts compile issues due to lenient tsconfig (#29843) The code failed presubmit in google3 because the original ts config was not as strict as the one used elsewhere in angular/angular and google3. PR Close #29843 2019-04-11 10:46:21 -07:00			`"noFallthroughCasesInSwitch": true,`
build: ensure schematics are built with typescript strict flag (#31967) Follow-up to #30993 where we build all Angular packages with the TypeScript `--strict` flag. The flag improves overall code health and also helps us catch issues easier. PR Close #31967 2019-08-02 16:42:11 +02:00			`"strict": true,`
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 20:30:38 +01:00			`"lib": ["es2015"],`
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 12:48:21 +01:00			`"types": [],`
			`"baseUrl": ".",`
			`"paths": {`
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 12:07:07 +02:00			`"@angular/core": ["../"],`
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 12:48:21 +01:00			`"@angular/compiler": ["../../compiler"],`
refactor(core): add static-query template strategy (#29815) Introduces a new strategy for the `static-query` schematic that is enabled by default. In order to provide a migration that works for the most Angular applications and makes the upgrade as easy as possible, the template strategy leverages the view engine Angular compiler logic in order to determine the query timing that is currently used within applications using view engine. PR Close #29815 2019-04-12 17:55:51 +02:00			`"@angular/compiler/": ["../../compiler/"],`
			`"@angular/compiler-cli": ["../../compiler-cli"],`
			`"@angular/compiler-cli/": ["../../compiler-cli/"]`
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 12:48:21 +01:00			`}`
			`},`
			`"bazelOptions": {`
			`"suppressTsconfigOverrideWarnings": true`
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 20:30:38 +01:00			`}`
			`}`