@vuejs/collaborators Anyone with any opinions why this._runtimeData is used...

@blake-newman
I think that this commit will probably be a good reference for that. 😺

@kazupon so i guess i can remove my test for the warnings... However tests pass fine if not using _runtimeData

Seems slightly flawed for recalling data function for warning on dev, as could incur different results in production/development. However, this no longer acts as so in current code, so it's a matter of what this._runtimeData achieves.

Hey, I have been asking about this question on various sites trying to find why my data() hook is being duplicated... so according to this it's a bug introduced starting at 1.0.18 and the newest commit is fixing? Is data() supposed to fire twice? Just checking for my own sanity :)

@dargue3 No, it's not. It should only be fired once 😄

@posva well at least I know I'm not crazy. Interesting how it has taken this long for anyone to notice... Or am I just the only one sending AJAX requests in my data() hook?

Like I said, through trial-and-error I found that this bug was introduced in v1.0.18

@dargue3 You might not be the only one but you shouldn't do that 😖
This may help you http://vuejs.org/guide/components.html#activate-Hook

Thanks for reporting that @dargue3

This was partially a dirty workaround to allow passing values for props in the data option. But now I think it was a bad idea to overload data for that purpose.

So now I've introduced a dedicated option propsData for passing props at instantiation calls.

I don't understand the purpose of the new propsData hook. The props can be defined with a default value, and data can be initialized in the data() hook right?

@YerkoPalma props are resolved async, as described here and I think propsData is sync, so it's ready in child component init. But let's wait until Evan updates docs about new propsData, he will make it clear.

@YerkoPalma default values are the same for every instance created. propsData is a way to provide different prop values at instance creation time without having to wrap it in a parent instance.

e.g. instead of first registering and rendering a parent instance with:

<test :data="123"></test>

You can just

new Test({
  propsData: {
    data: 123
  }
})

This is mostly about facilitating easier unit tests for components, not something you'd use very often in application code.

I see. Everything that help on tests is fine 😄 Thanks for the answer.

👍 makes sense

That was fast 👍