You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, devalue will ignore non-enumerable properties. It could use Object.getOwnPropertyDescriptors instead and handle those, correctly setting writable, enumerable and configurable.
With that, { foo: 1 } would just be the (common) special case where writable, enumerable and configurable are all true.
At the same time, we would throw on getters and setters, since devalue doesn't serialize functions.
The text was updated successfully, but these errors were encountered:
Currently, devalue will ignore non-enumerable properties. It could use
Object.getOwnPropertyDescriptors
instead and handle those, correctly settingwritable
,enumerable
andconfigurable
.With that,
{ foo: 1 }
would just be the (common) special case wherewritable
,enumerable
andconfigurable
are alltrue
.At the same time, we would throw on getters and setters, since devalue doesn't serialize functions.
The text was updated successfully, but these errors were encountered: