-
Notifications
You must be signed in to change notification settings - Fork 463
Proof of concept to handle issue with JS not initialized on start to fix #107 #169
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
Conversation
Thanks @konradkierus I'll check it. Can you also update the documentation ? |
@manuquentin just did, feel free to modify if you think it needs more details |
@konradkierus I have some thoughts for open discussion. The principle is: event order is important. Based on your concept, how about:
We may need to give user the last event, just return the last event in should discuss:
|
I don't see issues with implementing Now, regarding your questions. When I've started thinking about solution for the #107 issue, I was asking myself very similar questions which you are now asking me. |
Agreed, it's hard to implement a solution suit well for all cases. And yes, if the js part called internally in js module side, the user won't bother much. That's my whole point try to avoid add additional handling. That's wait others thoughts and different use cars. Thanks for your elaboration. |
Hi @konradkierus, Can you give it a try ? Thanks! |
Hi @manuquentin |
Can we close it and continue the discussion on #205? |
Closed in favor of #205 |
Proof of concept to handle issue with JS not initialized on start to fix #107
Described in details here: #107 (comment)
Example usage: