-
Notifications
You must be signed in to change notification settings - Fork 17
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
Add a Listener to refresh component with pusher events (websockets) #12
Comments
Hey, this is definitely on my radar for something to add. I considered it a "nice to have" rather than "need" for the first release. Fear not, it will be coming soon though. |
Great, waiting for it, also i would like to thanks for this component is really useful. |
Would |
Yeah, so a wire:poll would be a quick win but not keen on doing that for this package. |
Hi Mike, While I completely understand your perspective on this matter, I believe it is an essential feature that many users would greatly benefit from. Without this feature, users would need to modify the source code itself, which could be inconvenient and time-consuming. I would like to propose a solution that involves adding just two lines of code to implement the If you are open to this suggestion, I would be more than happy to create a pull request to incorporate the Thank you for your time and consideration. Best regards, |
Hey, apologies have been wanting to look at this, but having a 1-year-old child is time-consuming! Thinking about it, I'd definitely consider a PR for this if we can make the That feels like a good compromise for now to me. And it should still be pretty easy to remove when I have a chance to look at a better alternative. |
@mikebarlow Rather than a |
Yeah, that would also work for me. |
It would be great if we can call a listener or method using pusher events to show real-time notifications without reloading the page
The text was updated successfully, but these errors were encountered: