Skip to content

perf(material/core): tree shake sanity checks#23969

Merged
zarend merged 1 commit intoangular:masterfrom
crisbeto:core-sanity-checks-dev-mode
Nov 19, 2021
Merged

perf(material/core): tree shake sanity checks#23969
zarend merged 1 commit intoangular:masterfrom
crisbeto:core-sanity-checks-dev-mode

Conversation

@crisbeto
Copy link
Copy Markdown
Member

Now that we don't need to think about ViewEngine, we can use ngDevMode to tree shake the sanity check messages.

@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release labels Nov 16, 2021
@crisbeto crisbeto requested a review from jelbourn November 16, 2021 07:20
@crisbeto crisbeto requested a review from devversion as a code owner November 16, 2021 07:20
@google-cla google-cla bot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Nov 16, 2021
Now that we don't need to think about ViewEngine, we can use `ngDevMode` to tree shake the sanity check messages.
@crisbeto crisbeto force-pushed the core-sanity-checks-dev-mode branch from fa63858 to e787a62 Compare November 16, 2021 08:05
@crisbeto crisbeto requested a review from a team November 16, 2021 08:05
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Nov 16, 2021
@Optional() @Inject(MATERIAL_SANITY_CHECKS) sanityChecks: any,
@Inject(DOCUMENT) document: any,
@Optional() @Inject(MATERIAL_SANITY_CHECKS) private _sanityChecks: SanityChecks,
@Inject(DOCUMENT) private _document: Document,
Copy link
Copy Markdown
Contributor

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?

Copy link
Copy Markdown
Member Author

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.

@zarend zarend merged commit 738e514 into angular:master Nov 19, 2021
zarend pushed a commit that referenced this pull request Nov 19, 2021
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)
@angular-automatic-lock-bot
Copy link
Copy Markdown

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Dec 20, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants