fix(fmt): keep struct field access on same line after named args call

[gakonst]

Motivation

Closes #12399

When accessing a struct field after a function call with named arguments (e.g., _lzSend({...}).guid), the formatter was incorrectly placing the .field on a new line with weird indentation.

Before:

bytes32 guid =
    _lzSend({
    _dstEid: dstEid,
    ...
})
.guid;  // <-- unwanted line break

After:

bytes32 guid =
    _lzSend({
    _dstEid: dstEid,
    ...
}).guid;  // field stays on same line

Solution

Added detection for calls with named arguments in the member expression handling. When the preceding expression is a call using named arguments (the {key: value} syntax), we skip the zerobreak() that was causing the unwanted line break.

This specifically targets the pattern from the issue report while preserving existing behavior for:

• Regular method chains (obj.method().anotherMethod())
• Calls with positional arguments

PR Checklist

• Added Tests (testdata/StructFieldAccess/)
• Added Documentation (inline comments)
• Breaking changes (none)

[grandizzy]

looks good, @0xrusowsky mind to have a quick look before merge? thanks!

[gakonst]

Hey @gakonst 👋

Could you add an extra test case for chained calls with named args to ensure the second chained call and final .guid are properly formatted?

Something like this in original.sol:

// Chained calls with named args
function e() external {
    bytes32 guid = firstCall({
        param1: value1,
        param2: value2
    }).secondCall({
        arg1: val1,
        arg2: val2
    }).guid;
}

And the corresponding expected output in fmt.sol:

// Chained calls with named args
function e() external {
    bytes32 guid = firstCall({
        param1: value1,
        param2: value2
    }).secondCall({
        arg1: val1,
        arg2: val2
    }).guid;
}

This would verify that when you have multiple chained calls each using named args, the fix works for all of them (not just the first call), and that the final .guid field access stays on the same line as the closing }).