-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
InViewportDirective should emit when the host element is destroyed #1418
Comments
Happy to hear nice words. Could you provide example scenario in https://stackblitz.com/ ?? |
Sure! well deserved!
https://ng-in-viewport-gb-ex-1-vsec6f.stackblitz.io It was derived from the one from the docs. |
chore: extend peer deps to include angular v17 Refs: #1418 Release-As: 16.1.0
@all-contributors |
I've put up a pull request to add @tinesoft! 🎉 |
chore: extend peer deps to include angular v17 Refs: #1418 Release-As: 16.1.0
chore: extend peer deps to include angular v17 Refs: #1418 Release-As: 16.1.0
chore: extend peer deps to include angular v17 Refs: #1418 Release-As: 16.1.0
chore: extend peer deps to include angular v17 Refs: #1418 Release-As: 16.1.0
Thanks for the very fast ⚡ reply/action @k3nsei ! As a fellow OSS maintainer , I appreciate and value this ^^ |
Hi,
First of all, thanks for this useful library.
We came across an edge case with
inViewportAction
event from theinViewportDirective
: It will NOT be emitted when the hosting component is destroyed.... thus failing to notify the "listeners" of that event, that the element is no longer visible, because destroyed/removed from the DOM...We think, this line:
should be called, after this line:
ng-in-viewport/projects/ng-in-viewport/src/lib/directives/in-viewport.directive.ts
Line 83 in 1565794
I can provide a PR with the fix if you agree
The text was updated successfully, but these errors were encountered: