It probably is a Grails thing at this point. The Groovy project does have some general formatting guidelines but currently hasn't tried to provide a fixed recommended coding style across all language constructs. It is actually one of the things one agent has suggested we adopt to make life easier for AI agents, but we haven't look at that yet.
On Tue, Jul 28, 2026 at 6:00 PM Gianluca Sartori <[email protected]> wrote: > > That's the idea, to use the multiline style only when there are longer > expressions like strings, method calls, etc. > > Anyway I just realized there is no `groovy-developer` skill in the groovy > project, maybe Grails is the right place to work on it? > > > Gianluca Sartori > -- > https://dueuno.com > > > On Mon, 27 Jul 2026 at 19:03, MG <[email protected]> wrote: >> >> Hi Gianluca, >> >> I might misuderstand what you propose here, but for me the whole idea behind >> cond ? trueBranch : falseBranch is that it is a one-liner. >> Otherwise it is better suited for if-else-... >> >> Having said that, I can see that this way of formatting might make sense, if >> trueBranch and falseBranch are long(ish) String/GString|s (which we in our >> code do not have) - but as a general formatting rule, I would be against >> this. >> >> Cheers, >> mg >> >> >> Am 27.07.2026 um 14:38 schrieb Gianluca Sartori: >> >> Hi people, >> >> I've proposed the following PR to the Grails project in a rush, but I guess >> its proper place is the Groovy project. >> >> https://github.com/apache/grails-core/pull/16055 >> >> We usually format ternary operators like this for readability: >> >> String message = condition >> ? "Value when true" >> : "Value when false" >> >> Would you accept such PR on the groovy-developer skill? >> >> Cheers, >> Gianluca >> >> Gianluca Sartori >> -- >> https://dueuno.com >> >>
