Skip to content

Latest commit

 

History

History
69 lines (51 loc) · 2.09 KB

ISSUE_TEMPLATE.md

File metadata and controls

69 lines (51 loc) · 2.09 KB

This template is mostly a guideline, not a strict requirement, except the sections marked (required).

Please make sure that the issue is observable using the latest version of scalafmt and within the scalafmt CLI: https://scalameta.org/scalafmt/docs/installation.html#cli

Using the CLI is mandatory, in one of these configurations:

  • latest version of CLI and latest version in .scalafmt.conf
  • previous version of CLI and latest version in .scalafmt.conf
  • latest version of CLI and previous version in .scalafmt.conf

Configuration (required)

Please paste the smallest possible set of .scalafmt.conf configuration parameters that reproduces the problem:

version = <please enter the version here and make sure it's the latest>
...

NB: before submitting, please confirm that the problem is observed in the latest published version of the formatter! We don't publish hotfixes for older versions, and the problem you have observed in an older version may have already been fixed.

Command-line parameters (required)

When I run scalafmt via CLI like this: <command-line parameter>

If you were not using CLI initially:

  • please check using scalafmt CLI before submitting here (required)
  • if the problem does not present via CLI, DO NOT SUBMIT here: this is NOT a formatter issue
    • it could be an issue with your integration (sbt-scalafmt, metals, intellij etc.)
    • instead please submit the issue in the appropriate tool's repository
    • for instance, if the tool is sbt with the sbt-scalafmt plugin: please submit in sbt-scalafmt and include scalafmt parameters from build.sbt and the sbt command used
    • conversely, do not submit formatting issues into other tools; you must first verify using scalafmt CLI

Steps

Given code like this:

THE SMALLEST POSSIBLE SNIPPET OF ORIGINAL CODE

Problem

Scalafmt formats code like this:

OUTPUT FROM SCALAFMT

Expectation

I would like the formatted output to look like this:

EXPECTED FORMATTING OUTPUT

Workaround

I've found that by...

Notes

See also...