Skip to content

Conversation

paul-dingemans
Copy link
Collaborator

Description

Do not wrap an operation reference after an annotated expression to a separate new line

For most operation references this leads to code that cannot be compiled. For logical operators like && and || it does compile but leads to ugly formatting.

Closes #2955

Checklist

Before submitting the PR, please check following (checks which are not relevant may be ignored):

  • Commit message are well written. In addition to a short title, the commit message also explain why a change is made.
  • At least one commit message contains a reference Closes #<xxx> or Fixes #<xxx> (replace<xxx> with issue number)
  • Tests are added
  • KtLint format has been applied on source code itself and violations are fixed
  • PR title is short and clear (it is used as description in the release changelog)
  • PR description added (background information)

Documentation is updated. See difference between snapshot and release documentation

  • Snapshot documentation in case documentation is to be released together with a code change
  • Release documentation in case documentation is related to a released version of ktlint and has to be published as soon as the change is merged to master

… separate new line

For most operation references this leads to code that cannot be compiled. For logical operators like && and || it does compile but leads to ugly formatting.

Closes #2955
@paul-dingemans paul-dingemans added this to the 1.6 milestone May 11, 2025
@paul-dingemans paul-dingemans merged commit f2090c5 into master May 18, 2025
10 checks passed
@paul-dingemans paul-dingemans deleted the 2955 branch May 18, 2025 15:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Lint results in broken code for binary operation expression functions with an annotated expression
1 participant