-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
DynamicDialogRef - onClose Observable never completes #9732
Comments
I also observed the same issue. Will someone take care of that? |
same issue with this technology stack. |
I also encountered the same issue, found a work around to take(1) and then it completes:
|
Hi, So sorry for the delayed response! Improvements have been made to many components recently, both in terms of performance and enhancement. Therefore, this improvement may have been developed in another issue ticket without realizing it. You can check this in the documentation. If there is no improvement on this, can you reopen the issue so we can include it in our roadmap? Best Regards, |
Still broken: https://stackblitz.com/edit/dynamic-dialog-ref-onclose-not-completing-ntvgy9?file=src/app/app.component.ts CC @kali-dali |
Plunkr Case (Bug Reports)
The
onClose
Observable in theDynamicDialogRef
never completes. This is an issue, because other functionality, such as theforkJoin
operator of the rxjs library depends on Observables completing properly, not just emitting events.This issue applies to all dialog components / services which provide Observables to listen for events, e.g. ConfirmDialog, Dialog, ConfirmationService, etc.
Here is an example case:
https://stackblitz.com/edit/dynamic-dialog-ref-onclose-not-completing?file=src/app/app.component.html
Current behavior
onClose
Observable never completes when DynamicDialog closes.Expected behavior
onClose
Observable completes when DynamicDialog closes.What is the motivation / use case for changing the behavior?
Provide better integration into rxjs library.
Please tell us about your environment:
OS: Windows 10
Browser: Google Chrome
Angular version: 11.0.0
PrimeNG version: 11.0.0
The text was updated successfully, but these errors were encountered: