-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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(bazel): Handle comment and string parsing #8794
fix(bazel): Handle comment and string parsing #8794
Conversation
'http_file', | ||
'go_repository', | ||
'git_repository', | ||
].reduce( |
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.
This iteration caused so huge diff on rewritten snapshot (note other snapshot tests are same).
Can someone please point to good real use-case to test against? |
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.
Looks good if it works
…arinov/renovate into fix/bazel-parser-comments-and-strings
Example repo: https://github.com/renovate-testing/cockroach-gen/pulls Works similarly this branch and |
@zharinov I think this is the second time that this PR has failed tests with out of memory limits. Is there a chance it's caused by the code in this branch? |
I've noticed submodules test timeout for another branch. But for memory allocations, I'm not sure. |
I've seen this on my pr too. Maybe we should enable jest mem stats again. |
d36b490
to
2aeca0c
Compare
…el-parser-comments-and-strings
2aeca0c
to
0cd1ce7
Compare
This reverts commit 3208ac8.
This PR is cursed, I guess |
Changes:
Use
moo
lexer to handle sophisticated parsing edge-cases (comments and strings).Context:
Closes #8785
Documentation (please check one with an [x])
How I've tested my work (please tick one)
I have verified these changes via: