-
Notifications
You must be signed in to change notification settings - Fork 30k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doc: fix misleading language in vm docs #10708
Conversation
altering objects from the calling thread's context in unwanted ways. | ||
*Note*: The `require()` in the above case shares the state with the context it | ||
is passed from. This may introduce risks when untrusted code is executed, e.g. | ||
altering objects from the context in unwanted ways. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps s/from/in/ ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't change this sentence (except the addition of an article), but I think the author meant that require
had been passed from the other context. However, it would be nice to reword the whole sentence, since there are some other quirks; e.g., why "shares the state with the context" if it just shares the same context.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mscdex ah, sorry, we are talking about different lines.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, "in" should be used here.
@mscdex I've pushed a new commit. What about the line I've confused one you were talking about with, I think it's pretty okay though not perfect and I don't see a better way to reword it now. |
LGTM. @aqrln The rest is fine I think for now. |
The note following the http.Server example in the vm documentation contains misleading language. This commit removes the incorrect reference to threads. Fixes: nodejs#10697
Landed in 8781e61. Thanks! |
The note following the http.Server example in the vm documentation contains misleading language. This commit removes the incorrect reference to threads. Fixes: nodejs#10697 PR-URL: nodejs#10708 Reviewed-By: Brian White <mscdex@mscdex.net> Reviewed-By: James M Snell <jasnell@gmail.com>
The note following the http.Server example in the vm documentation contains misleading language. This commit removes the incorrect reference to threads. Fixes: nodejs#10697 PR-URL: nodejs#10708 Reviewed-By: Brian White <mscdex@mscdex.net> Reviewed-By: James M Snell <jasnell@gmail.com>
The note following the http.Server example in the vm documentation contains misleading language. This commit removes the incorrect reference to threads. Fixes: nodejs#10697 PR-URL: nodejs#10708 Reviewed-By: Brian White <mscdex@mscdex.net> Reviewed-By: James M Snell <jasnell@gmail.com>
The note following the http.Server example in the vm documentation contains misleading language. This commit removes the incorrect reference to threads. Fixes: nodejs#10697 PR-URL: nodejs#10708 Reviewed-By: Brian White <mscdex@mscdex.net> Reviewed-By: James M Snell <jasnell@gmail.com>
As @mscdex noted, the note following the http.Server example in the vm documentation contains misleading language. This commit removes the incorrect reference to threads.
Fixes: #10697
Checklist
Affected core subsystem(s)
doc