-
Notifications
You must be signed in to change notification settings - Fork 26.4k
Closed
Labels
P3An issue that is relevant to core functions, but does not impede progress. Important, but not urgentAn issue that is relevant to core functions, but does not impede progress. Important, but not urgentarea: bazelIssues related to the published `@angular/bazel` build rulesIssues related to the published `@angular/bazel` build rulesarea: compilerIssues related to `ngc`, Angular's template compilerIssues related to `ngc`, Angular's template compilerfreq3: highhotlist: components teamRelated to Angular CDK or Angular MaterialRelated to Angular CDK or Angular Materialstate: confirmedtype: bug/fix
Milestone
Description
🐞 bug report
Affected Package
@angular/bazel
Is this a regression?
No
Description
Type checking performed by ngtsc is currently matching as much as possible with what NGC did. Since ngtsc type checking can be more advanced, there are flags to enable more advanced checking of templates.
These flags cannot be set from within the ng_module
Bazel rule unfortunately. The issue is that ngc-wrapped
does not redirect the new strictness flags. It will be cumbersome to redirect all individual strictness flags, so we need to think about the ideal API for these type checking flags
Splaktar
Metadata
Metadata
Assignees
Labels
P3An issue that is relevant to core functions, but does not impede progress. Important, but not urgentAn issue that is relevant to core functions, but does not impede progress. Important, but not urgentarea: bazelIssues related to the published `@angular/bazel` build rulesIssues related to the published `@angular/bazel` build rulesarea: compilerIssues related to `ngc`, Angular's template compilerIssues related to `ngc`, Angular's template compilerfreq3: highhotlist: components teamRelated to Angular CDK or Angular MaterialRelated to Angular CDK or Angular Materialstate: confirmedtype: bug/fix