swift-format VS swift-vapor-demo

I actually don't see anything worth changing. It looks good to me. I think the most important thing is just to maintain the constructive attitude you already have about future-you dealing with the code, because only future-you will really know where you could have done better. One personal-preference thing I carried over from working on Go code is to look for a tool like gofmt [1,2] for Swift. I've been using swift-format [3] for about 2 years and haven't been dissatisfied enough to reach for something more fully featured like SwiftLint [4]. I didn't like the idea at first of delegating most formatting control over to a tool designed with someone else's subjective idea of formatting. But my feeling afterward was that it was freeing: it was no longer (completely) my job/burden/responsibility. An "assistant" would clean up the formatting of my code every time I saved the file. That's a nightmare if you can't configure the tool as much as you need, but if you're lucky and find a configuration you can live with, it lets you focus more on naming and other conventions that aren't so easily automated (yet). [1] https://go.dev/blog/gofmt [2] https://twitter.com/bitfield/status/953395343353315329 [3] https://github.com/apple/swift-format [4] https://github.com/realm/SwiftLint

if you want your code to be formatted with a specific set of rules in mind, you can forward the generated code to a formatting utility, e.g. swift-format

VERSION=0.50500.0 # replace this with the version you need git clone https://github.com/apple/swift-format.git cd swift-format git checkout "tags/$VERSION" swift build -c release ln -s /usr/local/bin/swift-format .build/release/swift-format

Apple literally provides a version that you can integrate into Xcode should you wish to.

swift-format works across different platforms and does a pretty good job with minimal configuration fuss.

You can find the source code here: Swift API Demo on GitHub. If you have any questions or comments, please reach out on Twitter or start a discussion on GitHub.