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
DOM lifecycle events selection #877
Comments
Have you looked into snabbom hooks? They allow you to do this |
That's what I want to select. |
Hooks just do something, there is nothing you could select, what exactly do you mean? |
Create a bunch of streams for each node, and once a hook is run produce event for that stream? An update hook is arguably an event.
|
yeah, an update is an event, but you already get updates with |
The imperative dom libraries usually emit events with callbacks themselves. While its simply matters of hoisting to convert them into streams and use them in main, but it's uglier. Is it really difficult to plumb through the hooks to dom driver? |
When I was referring to using global events above, I was referring to chaining onto widget events rather than the hooks. |
Honestly I still have problems understanding what you want to do in the end |
You make an instance of widget for example, and that widget emits events for when it does something. What I'm complaining about is that your view function that will contain a bunch of event handlers, as opposed to them being in intents function. |
@janat08 Could you try |
If that updates a couple of times, it will instantiate several widgets. |
Is #807 related to your question ? |
No, I want the hooks in dom driver. |
Would be cool of if you could select lifecycle hooks for DOM driver, for if you're using jquery plugins. My solution to this was basically creating global events.
The text was updated successfully, but these errors were encountered: