-
Notifications
You must be signed in to change notification settings - Fork 31.1k
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
repl: accept no arguments to start() #5388
Conversation
LGTM |
What is the game plan for landing code changes while Jenkins is offline? Should we just wait until it's back to use the normal CI flow? |
I think that would be best. |
LGTM, we should be holding for CI I think. |
LGTM with a minor nit, doc should be updated to specify |
Currently, there is a check to ensure that the user either provides an object or a string to repl.start(). The string case is used to set a REPL prompt. However, a default of '> ' already exists, so forcing the user to specify a prompt is a bit redundant. This commit removes this restriction. Fixes: nodejs#5385 PR-URL: nodejs#5388 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Jeremiah Senkpiel <[email protected]> Reviewed-By: Julian Duque <[email protected]>
Addressed @julianduque comment. CI is green - https://ci.nodejs.org/job/node-test-pull-request/1748/. Landing. Thanks for the reviews. |
Currently, there is a check to ensure that the user either provides an object or a string to
repl.start()
. The string case is used to set a REPL prompt. However, a default of'> '
already exists, so forcing the user to specify a prompt is a bit redundant. This commit removes this restriction.Closes #5385