Developing UI at scale can be challenging. At Schibsted, our large, distributed team of iOS developers collaborates on a single codebase. Our modular UI is shared by several apps, each of which applies a unique theme. Our requirements are effectively the worst case scenario for using Storyboards and Interface Builder.
In part 2 I discussed in detail how SwiftFormat’s parser and formatting rules are implemented. Swift is a very complex language, and although it’s syntax is fairly regular, there are a lot of edge cases. So how is it possible to write and maintain the rules that handle all of
In part 1 I talked about recursive descent parsers, and how they can be used to process complex structured text such as a programming language. Let’s now take a look at how SwiftFormat’s parser is implemented.
SwiftFormat solves the tabs vs spaces argument forever! OK, maybe not, but it might help Swift developers to get along. So what is SwiftFormat? Why did I make it? And how does it work?