Layout Rules

The layout rules decide the shape a bracketed construct takes once it outgrows a single line, exploding a call, signature, collection, or from … import … to one entry per line so each binding reads on its own and a later edit touches a single row. The trigger is a width budget like code-line-length, a count cap like max-args, or both, so the inline shape gives way to the stacked one the moment it stops being legible.

🧺

call-layout

Layout

Explodes a keyword-expressible call carrying more than the inline-argument cap to one keyword argument per line.

🧺

chain-layout

Layout

Breaks a fluent method chain across lines once it overflows the width or carries more links than the cap, hanging each link beneath the head's dot.

🧺

collection-layout

Layout

Splits list, tuple, dict, and set literals into one-entry-per-line layout once they overflow their width, or a dict crosses an entry-count cap.

🧺

import-layout

Layout

Lays an import block out one module per line, gathering each module's members behind it and packing an over-budget roster to the import budget.

🧺

signature-layout

Layout

Normalizes function signatures to one line or one parameter per line, gated by line length and inline-parameter count.

🧺

stack-adjacent-strings

Layout

Stacks an implicitly concatenated string run one literal per line once its joined line overruns the budget.

For the per-rule facets, see the Configuration reference. For the order these rules fire in (layout settles the bracketed shape early, so the alignment rules measure their columns against the committed layout), see the Pipeline Order reference.