Repository navigation
fix(formatter): preserve nested lambda body columns - #1803
Merged
Lorenzobattistela merged 2 commits intoOct 21, 2026
Merged
Conversation
toprameen
marked this pull request as ready for review
October 21, 2026 00:51
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
2 participants
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.
Formatting an inline lambda inside parentheses or a call argument can move its continued statements to different columns and make valid Bend source fail to parse. The formatter now pins nested lambda bodies and their semicolon continuations, and expires those pins at their enclosing delimiter or argument boundary. Generic commas and ordinary delimiter indentation retain their existing behavior.
Three regressions extend the existing formatting/idempotence and real-CLI preservation tests, with controls for following arguments and closing delimiters. Local npm tests pass 33/33, the repository gate passes 54/54, and actual LSP edits preserve the programs’ execution. The same regression tests fail against the unchanged formatter.