[Repo Assist] Regression test for lambda with MultiLineLambdaClosingNewline (#2553)#3228
Merged
nojaf merged 1 commit intoFeb 27, 2026
Conversation
…sue 2553 Closes #2553 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
3 tasks
Contributor
|
/repo-assist add a changelog entry for this as well |
This was referenced Feb 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 This is an automated PR from Repo Assist.
Closes #2553
Summary
Adds a regression test for the formatting bug reported in #2553, where a lambda expression inside a chained method call (e.g.
.Setup(fun ... -> <@ ... @>)) was formatted with the closing)incorrectly placed on its own line in an awkward position whenMultiLineLambdaClosingNewline = trueandMaxLineLength = 100.Root Cause
When the lambda body (a quotation expression
<@ ... @>) caused the enclosing line to exceedMaxLineLength, the formatter was placing the closing)on a separate line rather than properly wrapping the lambda body to a new line under thefunarrow.Current Behaviour (Fixed)
The formatter now correctly wraps the lambda body to a new indented line:
Test Status
✅ New regression test passes:
closing parenthesis of lambda in chained call should not be placed on own line, 2553