{"id":4409,"date":"2021-08-28T15:40:56","date_gmt":"2021-08-28T20:40:56","guid":{"rendered":"https:\/\/dev.iachieved.it\/iachievedit\/?p=4409"},"modified":"2021-08-28T15:40:56","modified_gmt":"2021-08-28T20:40:56","slug":"swiftformat-decent-swift-syntax-and-sublime-text","status":"publish","type":"post","link":"https:\/\/dev.iachieved.it\/iachievedit\/swiftformat-decent-swift-syntax-and-sublime-text\/","title":{"rendered":"swiftformat, Decent Swift Syntax, and Sublime Text"},"content":{"rendered":"

If you’re writing Swift code for iOS you’re most likely going to be doing so in Xcode. If you’re coding Swift to run on the server<\/a>, you might want to check out an editor like Sublime Text<\/a>. In this post we’ll show you how to use Sublime, the Decent Swift Syntax<\/a> package and swiftformat<\/a> together to write some nicely formatted Swift code.<\/p>\n

Sublime Text<\/h2>\n

Installing Sublime is as easy as heading over to the Sublime Text<\/a> website and clicking the download button appropriate for your platform. In this post we’ll be using macOS.<\/p>\n

Once you’ve installed Sublime Text create a new file with File – New<\/strong> and then go to its Tools<\/strong> menu and select Command Palette<\/strong>. A search field will open. Start typing ‘package’ and select Package Control: Install Package<\/strong>.
\n\"\"<\/a><\/p>\n

The search field will change again to list available packages to install. Find and install Decent Swift Syntax<\/strong>. You’ll notice from here that files ending in .swift<\/code> will be inferred as containing the Swift language, and Decent Swift Syntax will go to work.<\/p>\n

swiftformat<\/h2>\n

The Decent Swift Syntax<\/a> package relies on swiftformat<\/a> to do the heavy lifting of reformatting your Swift code. To install it you will want to use brew<\/a>: brew install swiftformat<\/code><\/p>\n

Two Spaces and a Gotcha<\/h2>\n

With the end of the spaces vs. tabs war<\/a>, the new battlefront formed was whether to indent two spaces or four. Anyone with sense knows that the answer is two spaces, so at the top of your Swift file you can add \/\/ swiftformat:options --indent 2<\/code> in order to tell swiftformat<\/code> to format your code accordingly.<\/p>\n

Now here is an interesting gotcha we you may find when writing closures. Let’s say our closure function signature is something like:<\/p>\n

typealias ClosureSignature = (String, Int, Int) -> Void\n<\/pre>\n
And we’re writing some code that supplies the closure, like:<\/p>\n
getData { data, status, error in\n  print(data)\n}<\/pre>\n
If this is all you wrote and saved your code swiftformat<\/code> would happily replace status<\/code> and error<\/code> because they were unused arguments<\/i>.  Out of habit I save files often so it came as a bit of a surprise when my arguments started disappearing.  Although swiftformat<\/code> has an stripunusedargs<\/code> option, it doesn’t appear to permit you to turn it off.<\/p>\n
\nhttps:\/\/dev.iachieved.it\/iachievedit\/wp-content\/uploads\/2021\/08\/swiftformat_eating_arguments.mov<\/a><\/video><\/div>\n","protected":false},"excerpt":{"rendered":"
If you’re writing Swift code for iOS you’re most likely going to be doing so in Xcode. If you’re coding Swift to run on the server, you might want to check out an editor like Sublime Text. In this post we’ll show you how to use Sublime, the Decent Swift Syntax package and swiftformat together […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[],"class_list":["post-4409","post","type-post","status-publish","format-standard","hentry","category-swift"],"_links":{"self":[{"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/posts\/4409"}],"collection":[{"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/comments?post=4409"}],"version-history":[{"count":14,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/posts\/4409\/revisions"}],"predecessor-version":[{"id":4427,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/posts\/4409\/revisions\/4427"}],"wp:attachment":[{"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/media?parent=4409"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/categories?post=4409"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/tags?post=4409"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}