Prevent possible conflict between multiline-expression-wrapping and function-signature body wrapping
#2650
Milestone
Comments
paul-dingemans
added a commit
that referenced
this issue
Aug 20, 2024
…n-signature` When `function-signature` rule is configured with `ktlint_function_signature_body_expression_wrapping` set to `default` then the first line of a multiline expression body should be kept on the same line as the end of function signature, as long as max line length is not exceeded. In this case the `multiline-expression-wrapping` rule has to ignore the multiline function expression body. Closes #2650
8 tasks
paul-dingemans
added a commit
that referenced
this issue
Aug 28, 2024
…n-signature` (#2775) When `function-signature` rule is configured with `ktlint_function_signature_body_expression_wrapping` set to `default` then the first line of a multiline expression body should be kept on the same line as the end of function signature, as long as max line length is not exceeded. In this case the `multiline-expression-wrapping` rule has to ignore the multiline function expression body. Closes #2650
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In case the
multiline-expression-wrappingandfunction-signaturerules are enabled, and settingfunction_signature_body_expression_wrappingis set todefault, it may result in conflicts between the rule regarding whether a multiline body expression is to be wrapped or not.Options:
multiline-expression-wrappingin casefunction-signaturerule is enabled, and settingfunction_signature_body_expression_wrappingis set todefaultfunction-signaturerule and let this be handled bymultiline-expression-wrappingonlyThe text was updated successfully, but these errors were encountered: