Skip to content

[WIP] Bump ruby_parser to 3.14.1 #353

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

Closed
wants to merge 1 commit into from
Closed

Conversation

larkinscott
Copy link
Contributor

@larkinscott larkinscott commented Jan 8, 2020

This should remain WIP for now. We discovered that this would introduce a few regressions re: line numbering after bumping ruby_parser.

@@ -140,6 +141,19 @@ def self.from_remediation_amount(amount)
expect(issues.length).to eq(3)
end

it "parses modern (>2.6) Ruby syntax" do
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This fails to parse before the parser version bump.

@larkinscott larkinscott requested a review from wfleming January 8, 2020 14:54
@larkinscott larkinscott changed the title Bump ruby_parser to 3.14.1 Bump ruby_parser to 3.14.1 [WIP] Jan 8, 2020
This bumps `ruby_parser` to resolve an escalation with regards to how
the duplication engine handled some more modern Ruby
syntax: https://github.com/codeclimate-support/quality/issues/12.

This bump also exposes a bug that was introduced into how the parser
handles heredocs, so marking a test that has become less-than-helpful
due to that as pending.
@larkinscott larkinscott changed the title Bump ruby_parser to 3.14.1 [WIP] [WIP] Bump ruby_parser to 3.14.1 Jan 8, 2020
@wfleming wfleming removed their request for review January 8, 2020 17:51
@larkinscott
Copy link
Contributor Author

Closing this PR for now. Would like to get this updated to the latest version of ruby_parser and will track internally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant