7

It seems that knockout is not mapping the properties of objects in an array correctly.

See this example from the chrome console:

> var viewmodel = ko.mapping.fromJS({list:[]});
undefined

> viewmodel.list().unshift({ name : ko.observable("Foo") });
1

> viewmodel.list()[0].name();
"Foo"

> var js = ko.mapping.toJS(viewmodel);
undefined

> js.list[0].name;
undefined

So the javascript object is being created, but the 'name' property does not get mapped.

Any ideas are very welcome!

2 Answers 2

11

From http://knockoutjs.com/documentation/plugins-mapping.html, about the toJS() function:

This will create an unmapped object containing only the properties of the mapped object that were part of your original JS object.

As "name" was not part of the original object you mapped, it does not get unmapped. You need to tell the mapping plugin to include this specific property:

var js = ko.mapping.toJS(viewmodel, { include: ['name'] });
Sign up to request clarification or add additional context in comments.

3 Comments

Thanks for the quick answer. Is there any way of modifying the behaviour to map every property? The documentation doesn't seem to mention this.
@RichardAstbury I don't think so. You will need to hard code this into a customized version of the mapping plugin.
I have since found ko.toJSON(viewModel) which seems to do the job.
3

Although Niko's answer is correct - there is a way to overcome this issue..

I have to say it's a bit of an ugly hack but it does the job and it's pretty easy to understand:

ko.mapping.toJS(ko.mapping.fromJSON(ko.toJSON(viewmodel)))

I map the view model from observable to json to observable (with all properties mapped) to object.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.