[
https://issues.apache.org/jira/browse/SPARK-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14380573#comment-14380573
]
Nicholas Chammas commented on SPARK-3849:
-----------------------------------------
Yeah, I suggest reading through this JIRA and the [related dev list
discussion](http://apache-spark-developers-list.1001551.n3.nabble.com/Scalastyle-improvements-large-code-reformatting-td8755.html)
carefully.
If you decide to take this on, I suggest putting together a brief outline of
what solution you're thinking of implementing and sharing it on the dev list.
People will likely have opinions on the matter. Better to hear them upfront
than build something that the committers won't want to merge in.
> Automate remaining Spark Code Style Guide rules
> -----------------------------------------------
>
> Key: SPARK-3849
> URL: https://issues.apache.org/jira/browse/SPARK-3849
> Project: Spark
> Issue Type: Improvement
> Components: Project Infra
> Reporter: Nicholas Chammas
>
> Style problems continue to take up a large amount of review time, mostly
> because there are many [Spark Code Style
> Guide|https://cwiki.apache.org/confluence/display/SPARK/Spark+Code+Style+Guide]
> rules that have not been automated.
> This issue tracks the remaining rules that have not automated.
> To minimize the impact of introducing new rules that would otherwise require
> sweeping changes across the code base, we should look to *have new rules
> apply only to new code where possible*. See [this dev list
> discussion|http://apache-spark-developers-list.1001551.n3.nabble.com/Scalastyle-improvements-large-code-reformatting-td8755.html]
> for more background on this topic.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
