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
fix: don't treat \ as escape in standard strings, support E-strings, support vars after ->> operator, treat lowercase e as valid e-string prefix #15139
Conversation
We also support support vars after ->> operator now. Backport of #14700
…ize/sequelize into sdepold/fix-backslash-replacement
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.
It feels a bit stupid, but can you undo the various style changes? Makes it easier to review the changes, especially in the tests.
Apart from that it looks good to me
…ize/sequelize into sdepold/fix-backslash-replacement
to be completely honest with you, I think we should stop wasting time talking about formatting :D we have the linter in place to prevent syntax problems. it even auto-formats stuff as it see needs. it's all green. so why care about something that is legacy anyway. however, I've reverted the changes to best of my abilities, even preventing the auto-formatting of my editor to turn it all upside down again. |
🎉 This PR is included in version 6.25.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Backport of #14700 and #14733.