Correctly clone existing active context - #43
Open
ashleyw wants to merge 1 commit into
Open
Conversation
|
@ashleyw Object.create will set this.active as a prototype of a newly created object context. When a property is not found directly on context it will be searched on its prototype, in this case, this.active. const prot = { test: 5 };
const obj = Object.create(prot);
console.log(obj.test)
// 5 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi,
From what I understand, nested contexts are permitted and values will be inherited, however within
createContextit currently usesObject.create(), but that doesn't actually clone the active context (on Node v8.16.0 & v10.16.0):Where I believe it should be using
Object.assign()to clone the object:For example:
Whereas:
Am I missing something, or is this a bug?
Thanks!