anonymous objects problem with pg

[hwangar]

Hi there!

Starting with node8, anonymous decorations are showing in pg responses (you can check it at vitaly-t/pg-promise#165), the problem is you're using a strong check using lodash.isPlainObject, which identifies them as NOT plain objects

Could it be a good idea to replace it with lodash.isObject? It looks correct enough to me and won't force postgres users to do a shallow copy before using NestHydrationJS

Greetings!
Juan Arias

[dvalentiate]

thanks for raising the issue, I'll look into this. I definitely want to support node 8 and haven't yet tested the library in it yet.

[MitMaro]

If this is what I think it is, it's not a Node 8 problem.

I hit this problem a while back, and iirc, node-postgres creates an object with a prototype for performance and other reasons. The solution in userland is to remove the prototype from these objects before passing them into the library. Though I agree with the change to lodash.isObject to fix the problem.

const nest = nestHydration().nest;
// data is a response from pg-promise
Reflect.setPrototypeOf(data, null);
return nest(data, definition);