Closed fvpDev closed 8 years ago
How can I reproduce it?
It's in the link I sent you yesterday... Is it working for you? I'll make a new repro that's simpler and send you the link, however it seems to have happened for each template that is rendered
I don't remember, did you send me a private message? If you can, just copy /paste it here or send it again. On Feb 2, 2016 5:58 PM, "Fedor Parfenov" notifications@github.com wrote:
It's in the link I sent you yesterday... Is it working for you? I'll make a new repro that's simpler and send you the link, however it seems to have happened for each template that is rendered
— Reply to this email directly or view it on GitHub https://github.com/ManuelDeLeon/viewmodel/issues/176#issuecomment-178929289 .
Here's a much simpler example: vmRepros.zip
View at http://fvptests.meteor.com
I have uploaded to github now: https://github.com/fvpDev/_vmTestRepros
Sorry bout the above .zip having wrong code and the /.meteor/local
folder included, here's an update which also includes v3.1.1:
Thanks for the help Pick up v3.1.2
You're awesome! Next time I get paid I'm buying you a beer
I noticed in History.md for v3.1.2 you put "Fix onCreated/onRendered/onDestroyed/autorun when using an array of functions"... I remember in the docs that you mention multiple functions only within the section for autoruns. I was wondering: so does this mean we can now have multiple functions (array of funcs) for onCreated/onRendered/onDestroyed as well?
Yes, you can now use an array of functions to run on onCreated/onRendered/onDestroyed
Getting this with viewmodel-react
Heh, I'll fix it... =)
On Aug 20, 2016 4:10 PM, "Fedor Parfenov" notifications@github.com wrote:
Getting this with viewmodel-react
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/ManuelDeLeon/viewmodel/issues/176#issuecomment-241226915, or mute the thread https://github.com/notifications/unsubscribe-auth/AED31hRp6OR-2ay3psUt8dboWKDGYa-5ks5qh3tVgaJpZM4HR5uk .
Moving this over to there
Receiving the following in the browser console log, v3.0.0 update: