-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
lib: avoid REPL exit on completion error #3358
Conversation
Fixed borkage. CI take two: https://ci.nodejs.org/job/node-test-commit/836/ |
Removed a line, so one more CI: https://ci.nodejs.org/job/node-test-commit/837/ |
More tweaks! I should go to sleep. Last CI for a while I hope: https://ci.nodejs.org/job/node-test-commit/838/ |
LGTM. The addition of the |
@bnoordhuis Since it's intended for internal use only, perhaps I can hide it a bit by making the property key a |
I'd go with a symbol. |
@bnoordhuis I did a |
Bump. I think this is good for a merge... /cc @bnoordhuis |
LGTM... err. I mean, WTIC /cc @Trott |
@Trott ... can I ask you to squash the commits and I'll get it landed. |
If a tab completion is attempted on an undefined reference inside of a function, the REPL was exiting without reporting an error or anything else. This change results in the REPL reporting the ReferenceError and continuing. Fixes: nodejs#3346 PR-URL: nodejs#3358 Reviewed-By: James M Snell <jasnell@gmail.com>
f8e494b
to
b354be7
Compare
Rebased to master, squashed, running one last CI before landing on master: https://ci.nodejs.org/job/node-test-commit/909/ |
Landed in b354be7 |
Landed in v4.x-staging in 1888f84 |
@Trott just noticing this, could you please make sure to be more specific for the subsystem? i.e. |
👍 |
If a tab completion is attempted on an undefined reference inside of a
function, the REPL was exiting without reporting an error or anything
else. This change results in the REPL reporting the ReferenceError and
continuing.
Fixes: #3346