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

[ACS-8959] Introduce new takeUntilDestroyed operator where possible #10388

Conversation

dominikiwanekhyland
Copy link
Contributor

Please check if the PR fulfills these requirements

  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x")

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Documentation
  • Other... Please describe:

What is the current behaviour? (You can also link to an open issue here)

What is the new behaviour?

Does this PR introduce a breaking change? (check one with "x")

  • Yes
  • No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...

Other information:

@dominikiwanekhyland dominikiwanekhyland force-pushed the ACS-8959-introduce-new-take-until-destroyed-operator-where-possible branch 3 times, most recently from d76c293 to 22a95ac Compare November 15, 2024 09:24
@AleksanderSklorz
Copy link
Contributor

In datatable.component.ts there is some unsubscribing on subscriptions array which we can replace with takeUntilDestroyed too probably:
image

@dominikiwanekhyland
Copy link
Contributor Author

@dominikiwanekhyland this comment seems not addressed: #10388 (comment)

@AleksanderSklorz hi, just to be sure, did you mean that one? Because that particular one was already resolved I think

@dominikiwanekhyland dominikiwanekhyland force-pushed the ACS-8959-introduce-new-take-until-destroyed-operator-where-possible branch from 971e451 to 203b9c4 Compare November 18, 2024 14:53
@dominikiwanekhyland dominikiwanekhyland force-pushed the ACS-8959-introduce-new-take-until-destroyed-operator-where-possible branch from 203b9c4 to cde9555 Compare November 18, 2024 16:21
@dominikiwanekhyland dominikiwanekhyland merged commit 3078387 into develop Nov 19, 2024
17 checks passed
@dominikiwanekhyland dominikiwanekhyland deleted the ACS-8959-introduce-new-take-until-destroyed-operator-where-possible branch November 19, 2024 10:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants