Having more models in a viewmodel when using "factories" about knockback HOT 4 CLOSED

Glad to hear you've enjoying it.

Hmmmm. If there was a single model with both apples and a pear, and you configured the reverse relationships for each, and you could traverse the model relationships from apple to apples then to pear when passed in.

var ApplesModel = Backbone.RelationalModel.extend({
    relations: [{
            type: Backbone.HasMany,
            key: "apples",
            relatedModel: AppleModel
        }, 
        {
            type: Backbone.HasOne,
            key: "pear",
            relatedModel: PearModel
        }
    ]
});

// plus add the reverse relationships between Apple -> Apples, Pear -> Apples.

Would that work?

from knockback.

Thank you for your quick response. Yes that would work but it would create an unwanted relation between the models. Apple(s) and the Pear model I mean. They don't really relate to each other on the model level. What I'm search for is for the viewmodel (AppleViewModel) to have access to the PearModel. Can this be done?

from knockback.

Most of the time the combination of model relationships or traversing the $data stack in the view using Knockout cover most cases.

I'm trying to think if there is a work around to pass the data through and the best I can think of is using a constructor for the view models. See create API examples like this and this. If you need this also for the model (non-collection) case, you can also look at the view model tests for create examples.

Basically, you have the option to use a create function install of passing a reference to the view model constructor in the factory. Then you can create an instance of your view model and pass whatever parameters you want to the constructor.

Would this work for you?

from knockback.

Yes that is exactly what I was looking for! Thank you.

from knockback.