-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
perf(material/core): tree shake sanity checks #23969
Conversation
Now that we don't need to think about ViewEngine, we can use `ngDevMode` to tree shake the sanity check messages.
fa63858
to
e787a62
Compare
@Optional() @Inject(MATERIAL_SANITY_CHECKS) sanityChecks: any, | ||
@Inject(DOCUMENT) document: any, | ||
@Optional() @Inject(MATERIAL_SANITY_CHECKS) private _sanityChecks: SanityChecks, | ||
@Inject(DOCUMENT) private _document: Document, |
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.
Does the new package format eliminate the problem with typing constructor params with browser global types like Document
?
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 think that it was more of a ViewEngine vs Ivy issue than with packaging. As long as we're using @Inject
we should be fine.
Now that we don't need to think about ViewEngine, we can use `ngDevMode` to tree shake the sanity check messages. (cherry picked from commit 738e514)
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. |
Now that we don't need to think about ViewEngine, we can use
ngDevMode
to tree shake the sanity check messages.