Resource clobbering moment objects

[gingermusketeer]

For the project I am working we are making use of a custom $httpProvider.defaults.transformResponse handler. It is doing things like converting to camel case and turning dates strings into momentjs objects.

This approach has mostly been working except I have run into an issue where the moment objects are being turned into normal objects. Looking at the source it appears that the issue is to do with angular.copy not preserving the object state/behavior. I tried to get around this by using setters and getters but these are also lost in translation. It would be great if there was some way to customise/configure the resource constructor or perhaps the copy function to prevent this.

angular -v => 1.0.7

[jankuca]

Got a demo?

[petebacondarwin]

@gingermusketeer - So when angular.copy does its thing, it should also copy over the prototype of the object?

[gingermusketeer]

I think so. Looks like angular.copy takes all the properties from the prototype and includes them in the new object directly rather then linking with the prototype. To me it would make sense if the new object behaved exactly like the one it was created from. e.g changing original objects prototype would alter it for the new object as well.

[gingermusketeer]

@jankuca something like what is below should be enough to show what happens

function Test(){}

a = new Test()
// Test {}

b = angular.copy(a)
// Object {}

Test.prototype.aprop = 3

a.aprop
// 3

b.aprop
// undefined