SwiftGen VS Chronology

It is important to say that there is an elegant solution to the resource consistency problem that we haven’t adapted yet. Instead of testing raw values of UIStoryboard.Name cases, we could just generate the UIStoryboard.Name enum. Please refer to SwiftGen for the details.

Your strings should work as-is if you use a tool like SwiftGen (it generates compiler-enforced types for use in your app).

Tools like https://github.com/SwiftGen/SwiftGen can be used to ensure at compile time that all keys used in your app are actually defined. Having keys organized as hierarchical enums, with auto-completion in Xcode is also a nice plus.

Our project includes a Gemfile which we use to specify some external dependencies. I'm trying to add SwiftGen (https://github.com/SwiftGen/SwiftGen) to the project. We want to eventually deprecate Cocoapods so I can't use that installation method.

https://github.com/SwiftGen/SwiftGen/issues/627#issuecomment-715259788

Or you can use something like SwiftGen and have code generation for your localized strings and have it checked at compile time instead of getting those pesky typo errors at runtime that you never check ;)

You shoudl take a look at the libray Time. https://github.com/davedelong/time

In general you should let the user’s locale determine the specifics of formatting dates. But if you need a specific format you can use the formatting methods here, or use clock.thisMinute().firstInstant.date to drop down to a Date object and use your own DateFormatter instance. But if you use the latter, be sure you set up the date formatter with the same time zone as the Absolute instance that clock.thisMinute() returns.