-
Notifications
You must be signed in to change notification settings - Fork 6.8k
build: enable more strictness flags in non-library code #23077
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! Ideally in the long-term our nested tsconfig's would all inherit the strictness properties from our project bazel-tsconfig-build
file, but that is more complicated than it sounds.
@@ -23,23 +23,23 @@ export class AttributeSelectorsMigration extends Migration<UpgradeData> { | |||
data = getVersionUpgradeData(this, 'attributeSelectors'); | |||
|
|||
// Only enable the migration rule if there is upgrade data. | |||
enabled = this.data.length !== 0; | |||
enabled: boolean = this.data.length !== 0; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder why this is needed. Seems like something TS could infer quite easily?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a weird one, but for some reason TS was flagging the entire class if the type isn't specified explicitly. It was something about not being able to infer the type from the constructor.
Updates the compiler options for the schematics and other Node-based code, and resolves any compilation errors that showed up as a result. Also fixes a bunch of references to non-existent types from `parse5`.
d55cb63
to
f76ddaa
Compare
Updates the compiler options for the schematics and other Node-based code, and resolves any compilation errors that showed up as a result. Also fixes a bunch of references to non-existent types from `parse5`. (cherry picked from commit 7b3006f)
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Updates the compiler options for the schematics and other Node-based code, and resolves any compilation errors that showed up as a result. Also fixes a bunch of references to non-existent types from
parse5
.