Closed satazor closed 11 years ago
for now object/merge could probably solve your problem, but I agree that in some cases fillIn
is better since it avoids cloning the child properties (which can be the desired effect).
True, I ended up using it at the cost of performance :S
I probably won't have time to work on it for the next few days (focusing on other tasks/projects) it shouldn't be hard to implement just need to compare object/fillIn
with object/mixIn
and use object/deepMixIn
as a reference. It just takes time to write tests and documentation.
PS: I made the tests work on node.js and integrated travis-ci so now it will be easier to contribute to the project and check if pull requests are OK to merge. running npm test
will update all packages and specs/runner.
We got deepMixin and is very useful. Could we have deepFillIn also?