+1 for me. I like this idea because most of the time when we look at this particular source code, it's because we're testing or debugging, and reasonable code formatting really improves this experience (especially because generated code can be a bit complicated). If I recall correctly there's some places where "unnecessary" class qualification prevents namespace collisions, so a bit of care might be necessary.
I wouldn't make it a hard requirement that it matches the Avro Spotless configuration. Best regards, Ryan On Tue, Sep 14, 2021 at 2:26 PM Thomas Becker <[email protected]> wrote: > > Although the generated SpecificRecord classes are pretty simple, I often > finding myself looking at them to get a feel for the shape of a record. > Unfortunately, the formatting of these classes is quite bad in a number of > ways: > > * Indentation > * Line breaks > * Unnecessary qualification of classes > > Would the community be open to accepting a patch to the Velocity template to > clean this up? >
