| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
Sorry, something went wrong.
|
CI failed but I think those errors are not related to this PR. not ok 712 parallel/test-http-pause --- duration_ms: 0.213 severity: fail stack: |- ... https://ci.nodejs.org/job/node-test-commit-linux/nodes=debian8-64/16655/console not ok 2002 sequential/test-fs-readfile-tostring-fail
---
duration_ms: 8.50
severity: crashed
stack: |-
oh no!
exit code: CRASHED (Signal: 9)
...
https://ci.nodejs.org/job/node-test-commit-linux/nodes=centos7-64/16655/console |
Sorry, something went wrong.
Sorry, something went wrong.
|
Is this the right place to add other syntax errors that the repl doesn't handle correctly? I can't find an issue for it. |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM. Just a nit and a question.
Sorry, something went wrong.
There was a problem hiding this comment.
Nit: please remove the else. This is a style that is normally not used here.
Sorry, something went wrong.
There was a problem hiding this comment.
rebasing and amending to same commit
Sorry, something went wrong.
There was a problem hiding this comment.
I guess recovering from e.g.
'`abc ${ test'is not possible anymore?
Sorry, something went wrong.
There was a problem hiding this comment.
Yes, only some forms are not possible. For instance, below one is possible.
`abc ${
test}`Its mostly consistent with chrome console behaviour except for couple of cases.
> (function() {
... x = { help: () => 'help received' };
... return x
... .help (); <-- no repl command parsing in multiline mode
.break Sometimes you get stuck, this gets you out
.clear Alias for .break
.editor Enter editor mode
.exit Exit the repl
.help Print this help message
.load Load JS from a file into the REPL session
.save Save all evaluated commands in this REPL session to a file
...
(I'll give PR over the weekend)
Sorry, something went wrong.
|
@0joshuaolson1 please open a new issue in case you think the repl should recover from errors that you ran into. |
Sorry, something went wrong.
Below syntax errors are handled without force .break/clear - Unexpected Token (prefix errors) - missing ) after argument list In the multiline expression, recoverable errors are truly recoverable, otherwise syntax error will be thrown.
Sorry, something went wrong.
|
Landed in ebfa8b1 🎉 |
Sorry, something went wrong.
Below syntax errors are handled without force .break/clear - Unexpected Token (prefix errors) - missing ) after argument list In the multiline expression, recoverable errors are truly recoverable, otherwise syntax error will be thrown. PR-URL: #18915 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Shingo Inoue <leko.noor@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Below syntax errors are handled without force .break/clear - Unexpected Token (prefix errors) - missing ) after argument list In the multiline expression, recoverable errors are truly recoverable, otherwise syntax error will be thrown. PR-URL: #18915 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Shingo Inoue <leko.noor@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Below syntax errors are handled without force .break/clear - Unexpected Token (prefix errors) - missing ) after argument list In the multiline expression, recoverable errors are truly recoverable, otherwise syntax error will be thrown. PR-URL: #18915 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Shingo Inoue <leko.noor@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Below syntax errors are handled without force .break/clear - Unexpected Token (prefix errors) - missing ) after argument list In the multiline expression, recoverable errors are truly recoverable, otherwise syntax error will be thrown. PR-URL: nodejs#18915 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Shingo Inoue <leko.noor@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Below syntax errors are handled without force .break/clear - Unexpected Token (prefix errors) - missing ) after argument list In the multiline expression, recoverable errors are truly recoverable, otherwise syntax error will be thrown. PR-URL: nodejs#18915 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Shingo Inoue <leko.noor@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Below syntax errors are handled without force .break/clear - Unexpected Token (prefix errors) - missing ) after argument list In the multiline expression, recoverable errors are truly recoverable, otherwise syntax error will be thrown. Backport-PR-URL: #22380 PR-URL: #18915 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Shingo Inoue <leko.noor@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
| Back | FazBrowse Home | New Git URL |
Better handling of recoverable errors in REPL module
Below syntax errors are handled without force .break/clear
In the multiline expression, recoverable errors are truly
recoverable, otherwise syntax error will be thrown.
Checklist
Affected core subsystem(s)
repl