Github user koeninger commented on a diff in the pull request:

    https://github.com/apache/spark/pull/23148#discussion_r236858392
  
    --- Diff: dev/.scalafmt.conf ---
    @@ -0,0 +1,24 @@
    +#
    +# Licensed to the Apache Software Foundation (ASF) under one or more
    +# contributor license agreements.  See the NOTICE file distributed with
    +# this work for additional information regarding copyright ownership.
    +# The ASF licenses this file to You under the Apache License, Version 2.0
    +# (the "License"); you may not use this file except in compliance with
    +# the License.  You may obtain a copy of the License at
    +#
    +#    http://www.apache.org/licenses/LICENSE-2.0
    +#
    +# Unless required by applicable law or agreed to in writing, software
    +# distributed under the License is distributed on an "AS IS" BASIS,
    +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    +# See the License for the specific language governing permissions and
    +# limitations under the License.
    +#
    +
    +align = none
    +align.openParenDefnSite = false
    +align.openParenCallSite = false
    +align.tokens = []
    +docstrings = JavaDoc
    +maxColumn = 98
    --- End diff --
    
    For now, this won't complain about any code, it just gives a way for 
contributors to format it.
    
    If we did turn on test as part of the build process, it would complain 
about any code that was different after formatting.  That could include code in 
that 99-101 column range, depending on whether it hit that corner case.  E.g.
    
    ```
        // this is 101 columns and will fail scalastyle, but will pass with 
scalafmt set to 99
        if 
(caseInsensitiveParams.contains(s"kafka.${ConsumerConfig.VALUE_DESERIALIZER_CLASS_CONFIG}"))
 {
    ```
    
    My thinking is that being slightly more strict than existing scalastyle is 
better than having automated formatting that won't pass other existing 
automated checks.  Trying to find and upstream fixes to off-by-one errors in 
scalastyle is another option, but that will take a while.


---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to