-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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: Adding code for handling multiline history #22153
Conversation
Ok looks interesting, test on my mac works perfectly fine. Not sure why CI build is failing though 😕 |
cc @nodejs/repl |
It would be great to get multi line support in the repl. I guess the approach itself is fine for as a first start. Looping in @jdalton. You seemed to have interest in the repl as well. |
8093905
to
80084b4
Compare
80084b4
to
53c5a8b
Compare
lib/readline.js
Outdated
@@ -216,6 +217,7 @@ function Interface(input, output, completer, terminal) { | |||
|
|||
this.history = []; | |||
this.historyIndex = -1; | |||
console.log('Yes initialized....\n\n\n', this.history); |
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.
☝️ is that debug?
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.
My bad, yes did for debugging. Will remove them and update the PR with test cases :)
53c5a8b
to
29b5c6e
Compare
@jdalton Have removed the console statement also added the test. Can you please have a look at it? |
@jdalton Can you kindly loop in other folks who also needs to approve this PR before it will get merged? Thanks! |
Friendly re-ping of @nodejs/repl 🔊 |
{ // Tests multiline history | ||
env: {}, | ||
test: ['{', '}', UP, CLEAR], | ||
expected: [prompt, '{', '... ', '}', '{}\n', prompt, `${prompt}{}`, prompt], // eslint-disable-line max-len |
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.
nit: this really shouldn't need the exclusion... just go ahead and wrap.
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.
@jasnell Sure, will take care and push the change. Thanks!
29b5c6e
to
ee6cce4
Compare
@jasnell : Addressed your review comments. |
ee6cce4
to
097a770
Compare
There shouldn't be anything else. A lot of us have been tied up this week with a conference. Hopefully this will be landed here soon |
Friendly ping @nodejs/repl if anyone wants to take another look as quite some time has passed. |
097a770
to
f69c51a
Compare
f69c51a
to
ce91b4d
Compare
This looks more like a bug fix to me. |
PR-URL: nodejs#22153 Reviewed-By: John-David Dalton <[email protected]> Reviewed-By: James M Snell <[email protected]>
Landed in dd7a3d2 |
Thanks everyone! |
PR-URL: #22153 Reviewed-By: John-David Dalton <[email protected]> Reviewed-By: James M Snell <[email protected]>
@targos I think this can be backported to |
If this is backported to v10.x, it should be done with #24389 |
I guess we are good here, I couldn't see the code in |
This seems like it should perhaps have been Semver-Minor... is that a correct assumption? |
I always wanted to handle multiline history separately. For example, if I enter a multiline statement and then navigate between the history(s), its very annoying as it shows each line, but I expect it to show the executed line.
This is work in progress, but yeah its working and all test cases are passing. I need to handle fewmore cases and write a unit test case. But thought, what others think over this? May be there is alsoa better way to do it.Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes