viewModel.set() and hierarchy

[estesbubba]

I have a LoginController that does a

            viewModel.set({
                username: data.session.user,
                database: data.session.dsn
            });

username and password aren't defined in LoginModel but in its parent MainModel. Doing the set() like above actually adds it to the LoginModel but I want it in the MainModel. Is there any way to have set() look up the parent chain and only set if defined on data{}? I can do a viewModel.getParent().set() but then I need to know how far up it is which could cause problems if hierarchy changes.

[LesJ]

I have a LoginController that does a

            viewModel.set({
                username: data.session.user,
                database: data.session.dsn
            });

username and password aren't defined in LoginModel but in its parent MainModel. Doing the set() like above actually adds it to the LoginModel but I want it in the MainModel. Is there any way to have set() look up the parent chain and only set if defined on data{}? I can do a viewModel.getParent().set() but then I need to know how far up it is which could cause problems if hierarchy changes.

I believe you need to know the model on which to set the value because JavaScript prototype chain is used to provide value inheritance.