Skip to content
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

fix(angular): ngOnDestroy runs inside angular zone #24949

Merged
merged 3 commits into from
Mar 22, 2022
Merged

fix(angular): ngOnDestroy runs inside angular zone #24949

merged 3 commits into from
Mar 22, 2022

Conversation

sean-perkins
Copy link
Contributor

Pull request checklist

Please check if your PR fulfills the following requirements:

  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been reviewed and added / updated if needed (for bug fixes / features)
  • Build (npm run build) was run locally and any changes were pushed
  • Lint (npm run lint) has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

  • Bugfix
  • Feature
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Documentation content changes
  • Other (please describe):

What is the current behavior?

When using ion-router-outlet, the page components will execute ngOnDestroy life cycle hooks outside of the Angular zone.

Issue URL: #22571

What is the new behavior?

  • ngOnDestroy will execute inside of Angular zones when pages are unmounted inside ion-router-outlet

Does this introduce a breaking change?

  • Yes
  • No

Other information

@sean-perkins sean-perkins requested a review from a team as a code owner March 16, 2022 19:56
@github-actions github-actions bot added the package: angular @ionic/angular package label Mar 16, 2022
Copy link
Contributor

@liamdebeasi liamdebeasi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! ionViewWillLeave and ionViewDidLeave still fire inside of NgZone, correct?

@sean-perkins
Copy link
Contributor Author

Looks good! ionViewWillLeave and ionViewDidLeave still fire inside of NgZone, correct?

Correct! This change only effects the internal life cycle methods handled by Angular when a component is destroyed (ngOnDestroy). All life cycle methods (Angular & Ionic's custom) should run inside of an NgZone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
package: angular @ionic/angular package
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants