DzenisevichK
DzenisevichK
I would prefer the syntax to match the object structure as closely as possible - agree... but how to map { a: { create: true } } ?
This variant will fix this case: { <paths to properties>: copy|include|ignore, <paths to properties>: { key|create|update: <callbacks> } } Common rule: property name - path(s) definition, property value - options...
It seems that copy|include|ignore and key|create|update cannot be used together or? If yes then variant: { id: "copy" } is more shorter...
This is not correct to merge options from different levels...
Ok, but at weekends. Also I will try to reduce ko.mapping (at least for own use) to have logically correct/workable functional.
I refused to use `ko.mapping`. I implemented `ko.updateableArray` and use it with manually wrapping/unwrapping observables and don't have any problems...
Unit test for it: http://jsfiddle.net/DzenisevichK/tYuxA/