Creates a separate bazel target for the google3 migration tests. The benefit is that it's faster to run tests for public migrations in development. Google3 lint rules are usually another story/implementation and the tests are quite slow due to how TSLint applies replacements. Additionally if something changes in the google3 tslint rules, the tests which aren't affected re-run unnecessarily. PR Close #31817
Renderer -> Renderer2 migration
Automatically migrates from Renderer
to Renderer2
by changing method calls, renaming imports
and renaming types. Tries to either map method calls directly from one renderer to the other, or
if that's not possible, inserts custom helper functions at the bottom of the file.
Before
import { Renderer, ElementRef } from '@angular/core';
@Component({})
export class MyComponent {
constructor(private _renderer: Renderer, private _elementRef: ElementRef) {}
changeColor() {
this._renderer.setElementStyle(this._element.nativeElement, 'color', 'purple');
}
}
After
import { Renderer2, ElementRef } from '@angular/core';
@Component({})
export class MyComponent {
constructor(private _renderer: Renderer2, private _elementRef: ElementRef) {}
changeColor() {
this._renderer.setStyle(this._element.nativeElement, 'color', 'purple');
}
}