Fix line continuations in spec examples #8448
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When describing the code that should be detected / auto-corrected, some specs do not escape line continuations properly.
For example:
results in the string
"something continues\n"
instead of the desired"something \\\n continues\n"
Correct specs escape the backslash or use single quoted heredocs to keep the line continuation in the source under test, like:
In correcting the specs, it became apparent that
Style/NestedParenthesizedCalls
cop did not behave as intended.RangeHelp
mixin has been adapted to optionally include line continuations (backslash newline sequence).Feedback is welcome on whether this behaviour on replacing whitespace with parentheses matches with your expectations.
Before submitting the PR make sure the following are checked:
[Fix #issue-number]
(if the related issue exists).master
(if not - rebase it).bundle exec rake default
. It executes all tests and RuboCop for itself, and generates the documentation.