You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2016/01/20 16:57:40 UTC

[jira] [Resolved] (SPARK-3849) Automate remaining Spark Code Style Guide rules

     [ https://issues.apache.org/jira/browse/SPARK-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Owen resolved SPARK-3849.
------------------------------
    Resolution: Done

I broke out the one remaining task as a stand-alone and am closing this.

> 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-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org