wait-for not rendering child components even if they emit the correct event

[dhruvio]

I've created a fiddle illustrating my experience with wait-for in v0.12.1.

http://jsfiddle.net/xqncyyeh/1/

ideally, if app.activeView = "a" or "b", their templates should be rendered into the <component> block. However, nothing happens.

Any advice?

[dhruvio]

Also, the rendering works if you take of the wait-for="loaded" attribute from the <component> block.

[dhruvio]

So, I played around with this a little, and it seems like if the event is run in the current tick, it's not picked up by wait-for .

I updated the previous fiddle to illustrate this: http://jsfiddle.net/xqncyyeh/2/.

Seems like a bug, do you think you will support synchronous event-firing for wait-for ?

[dhruvio]

I read this link: http://vuejs.org/guide/best-practices.html#Understanding_Async_Updates

Seems like this.$nextTick(callback) will solve the problem. I'm going to close this issue. Apologies for the spam! Hope this helps someone else.

[TylerBre]

@dhruvio can you provide an example of your code working with this.$nextTick?

Struggling over here, and that article is not that helpful

EDIT: Not 2 minutes passed until I realized I wasn't using .$set...

[dhruvio]

Hey Breland, wait-for listens to events after the end of the current event loop iteration. So, if wait-for="event", you should run your logic inside your Vue instance as follows:

this.$nextTick(function() {
  this.$emit("event");
});

If you just say this.$emit("event") in the current event loop, the listener won't pick up the event as wait-for won't be listening yet.

I wrote this on my phone, so apologies if the formatting is weird. I hope this answers your question. If you don't understand any of this, I recommend googling how process.nextTick works. Vue's $nextTick method is analogous to that.

Cheers

On Aug 9, 2015, at 00:24, Tyler Breland notifications@github.com wrote:

@dhruvio can you provide an example of your code working with this.$nextTick?

Struggling over here, and that article is not that helpful

—
Reply to this email directly or view it on GitHub.