Skip to content
This repository has been archived by the owner on Oct 15, 2020. It is now read-only.

chakrashim: fix undefined values in inspector #284

Merged
merged 1 commit into from
Jun 2, 2017

Conversation

kfarnung
Copy link
Contributor

@kfarnung kfarnung commented Jun 2, 2017

When creating the wrapped objects we were copying the undefined
properties which were then being translated to null during
serialization.

Fixes #280

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • commit message follows commit guidelines
Affected core subsystem(s)

chakrashim

@kfarnung
Copy link
Contributor Author

kfarnung commented Jun 2, 2017

When creating the wrapped objects we were copying the `undefined`
properties which were then being translated to `null` during
serialization.

Fixes nodejs#280

PR-URL: nodejs#284
Reviewed-By: Hitesh Kanwathirtha <hiteshk@microsoft.com>
@kfarnung kfarnung merged commit dc9a360 into nodejs:xplat Jun 2, 2017
@kfarnung kfarnung deleted the undef branch June 2, 2017 01:29
kfarnung added a commit to kfarnung/node-chakracore that referenced this pull request Jun 5, 2017
When creating the wrapped objects we were copying the `undefined`
properties which were then being translated to `null` during
serialization.

Fixes nodejs#280

PR-URL: nodejs#284
Reviewed-By: Hitesh Kanwathirtha <hiteshk@microsoft.com>
kfarnung added a commit to kfarnung/node-chakracore that referenced this pull request Jun 5, 2017
When creating the wrapped objects we were copying the `undefined`
properties which were then being translated to `null` during
serialization.

Fixes nodejs#280

PR-URL: nodejs#284
Reviewed-By: Hitesh Kanwathirtha <hiteshk@microsoft.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants