-
Notifications
You must be signed in to change notification settings - Fork 14.5k
MINOR; Update scalafmt to latest version #12475
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -12,7 +12,10 @@ | |
# 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. | ||
docstrings = JavaDoc | ||
version = 3.5.9 | ||
runner.dialect = scala213 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We still support scala 2.12 in this project. By specifying the dialect as 2.13, would we fail where syntax for 2.12 is used? If yes, are there any such cases in the project? (The build should tell us that after the existing spotless check passes). There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The Scala 2.13 dialect is backwards compatible with 2.12. I have applied the dialect when updating from scalafmt 2 to scalafmt 3 with various popular OSS Scala projects and there isn't any issues (in any case the Scala code that is used im Kafka is quite conservative)
Do you think it makes sense to format the docs or should I leave the PR as is?
In that case it's sensible to wait for your PR to land and then I can rebase. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
I think we should leave the PR as is. Converting the docs in the entire project will be cumbersome without any benefit.
Thanks, in that case, would you kindly review that PR please if you get some time? It's been pending for a while now waiting to get some attention. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
I just landed a review of the PR. |
||
docstrings.style = Asterisk | ||
docstrings.wrap = false | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This forces scalafmt to ignore docstrings when formatting code. The new version of scalafmt works on docstrings however it doesn't support manual html formatting which is done in kafka scala streams. |
||
maxColumn = 120 | ||
continuationIndent.defnSite = 2 | ||
assumeStandardLibraryStripMargin = true | ||
|
Uh oh!
There was an error while loading. Please reload this page.