-
Notifications
You must be signed in to change notification settings - Fork 29.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 history broken #24781
Comments
Ping @antsmartian |
instead of revert, can we put it behind a flag? that would make it easier to do incremental improvements |
@BridgeAR I guess we have already an issue with multilines in the context of template string literals. (On mobile now, couldn't find that.) From the examples I see that's what it's getting affected. Did you see anything else broken apart from template string literals? |
There's also an issue when the code contains a comment: var obj = {
prop: 123, // comment
otherProp: 456
} becomes var obj = {prop: 123, // commentotherProp: 456} Basically, anything that relies on line breaks is broken. |
Is there no way for us to keep the line breaks? That's what |
#24231 - it reports the same as here, so I am going to close this as a duplicate. |
Version: latest master
The new multiline history does not fully work as it should. While trying to fix it I ran into further issues, so I decided to just open this issue about it for now.
Example 1:
Example 2:
I suggest to revert this feature for now and to reland with a very decent test coverage for lots of edge cases. What do others think?
The text was updated successfully, but these errors were encountered: