-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-9093][SparkR] Fix single-quotes strings in SparkR #7439
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
Conversation
|
@shivaram Could you review it when you have time? Thanks! |
|
Test build #37486 has finished for PR 7439 at commit
|
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.
Should we insert a white space into both sides of = ?
Could you fix this as well?
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.
Maybe. But personally, I think fixing it would be better with another issue. Since we haven't discussed the validation rule for the spaces for parameters yet.
|
I've left minor comments. Otherwise, LGTM. |
|
@sarutak Thank you for reviewing it! |
|
@yu-iskw FWIW we already have an (admittedly unwritten) style rule of putting space around both sides of BTW does lintr catch these or not ? |
|
Actually it comes up in a few more places but mostly in example code I guess |
|
@shivaram I have just experimented the infix operator warnings at function's optional parameters. According to the result, it seems that lintr can't catch them which are optional parameters. |
|
After all, I think it would be better to deal with the spaces problems on another issue. Because there is no linter about that, it is not easy to validate them now. Plus, we should focus on getting rid of the warnings about single-quotes strings on this PR. |
|
Alright, let's focus on the single-quote string literals on this PR. |
|
Yeah backporting style improvements didn't seem very important to me. The only reason to backport them would be to avoid conflicts for other backport PRs -- Feel free to open a new JIRA / PRs if you think it'll make things easier in the future. |
[SPARK-9093] Fix single-quotes strings in SparkR - ASF JIRA
This is the result of lintr at the rivision:011551620faa87107a787530f074af3d9be7e695
[SPARK-9093] The result of lintr at 011551620faa87107a787530f074af3d9be7e695