Skip to content

refactor(multiple): clean up explicit teardown flags #23814

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

Merged
merged 1 commit into from
Oct 24, 2021

Conversation

crisbeto
Copy link
Member

The new teardown behavior is enabled by default so we can drop the teardown flag usages.

The new teardown behavior is enabled by default so we can drop the `teardown` flag usages.
@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent merge safe target: rc This PR is targeted for the next release-candidate labels Oct 22, 2021
@crisbeto crisbeto requested a review from devversion October 22, 2021 06:17
@crisbeto crisbeto requested review from andrewseguin, jelbourn and a team as code owners October 22, 2021 06:17
@google-cla google-cla bot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Oct 22, 2021
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Oct 22, 2021
@wagnermaciel wagnermaciel merged commit 656320d into angular:master Oct 24, 2021
wagnermaciel pushed a commit that referenced this pull request Oct 24, 2021
The new teardown behavior is enabled by default so we can drop the `teardown` flag usages.

(cherry picked from commit 656320d)
@angular-automatic-lock-bot
Copy link

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 Nov 24, 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: rc This PR is targeted for the next release-candidate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants