explicit manual instance binding about discussion HOT 5 CLOSED

I'm not sure passing down an instance makes sense - you almost always want to pass down a subclass constructor.

Say you have

var Sub = Vue.extend({ /* options */ })

Once the subclass is created, its option object is available as Sub.options. So you can do

Sub.options.data.nextField = ...
Sub.options.methods.anotherMethod = function () {...}

from discussion.

@yyx990803 ,
"Sub.options.methods.anotherMethod = function () {...}, or Sub.options.data.nextField = ..." - I can not grok why we assign fields' values to class attributes rather to instance's one.

from discussion.

"create the subclass" means defining the subclass constructor with var Sub = Vue.extend(...). The constructor alone doesn't do anything, so you can modify its options across multiple steps. When you're done, you eventually create an instance with var sub = new Sub(...).

Personally for me I don't understand why you'd want to modify an instance's behavior when it's already created. The way Vue is meant to work is that you define everything you need before you create an instance.

Anyway, you can do vm.$data.$add('key', value) to add observable properties, but they will not be proxied on the vm object.

from discussion.

I don't mean adding data or methods after binding. I was saying about "working" [with instance] after binding, that is, say, change some fields, and so on.

I'll try to get a code experiment and to change the way my brain work :) Let's keep the discussion open during these upcoming days. OK?

from discussion.

OK, I guess current Vue state in the discussion context isn't a showstoper, and it keeps the Vue clean :) Closing.

from discussion.