SwiftGen 6.6 Templates Migration Guide

There are no major changes in the templates, only a small edge case:

In the strings templates, if you were providing a custom lookupFunction, the signature of that function has changed. Previously, the function had to accept 2 parameters (table and key), now the function must accept 3 parameters: table, key and value.

Deprecation notices for users

There are a few deprecation notices:

• The xcassets templates' allValues parameter is now deprecated, and will be removed in the next version.

Deprecation notices for template writers

There are a few deprecation notices:

• Our workaround for spacing/trimming is deprecated, and will soon switch to Stencil's "smart" trimming behaviour.
• StencilSwiftKit's removeNewlines filter is deprecated (replaced by Stencil's new syntax).
• You can see a preview of all these changes by taking a look at our built-in templates, which have been updated to the new syntax. If you'd like to try it for your own templates, use the --experimental-modern-spacing CLI flag.

SwiftGen 6.3 Templates Migration Guide

There are no major changes in the templates, only a small deprecation notice:

In the fonts templates, we're deprecating the generated Font typealias. So if you were using it somewhere in your own code, you should instead create your own typealias, or use the platform-specific type such as UIFont/NSFont. The Font typealias will be removed in the next major release of SwiftGen.

SwiftGen 6.2 Templates Migration Guide

Removed Swift 3 templates

We've removed the bundled swift3 templates, as we added swift5 templates. We assume most of you are already developing in a newer version of Swift (4 or 5), as recent Xcode versions no longer provide support for Swift 3. If you're still using an old Swift version, you can copy the swift3 templates from older versions of SwiftGen into your project and point to them using templatePath.

CoreData: entityName is now a property

If you are using Core Data templates, entityName is now correctly a class var property instead of a class func. You will have to remplace calls to .entityName() by .entityName instead.

Strings: %@ now generates an Any instead of String

When generating constants for strings, if your string contains %@ placeholders, we previously generated a function with corresponding parameters of type String. We now correctly generate these parameters as being of type Any, since %@ corresponds to any class or NSObject, not just String.

This means that if you were previously explicitly calling obj.description or String(describing: obj) to be able to pass an object obj to one of the generated strings functions for localization, you can now replace your code to directly pass obj instead.

XCAsset templates typealiases deprecation

In the unlikely case that you used the colorAliasName and imageAliasName typealiases generated by the XCAsset templates, know that they are now deprecated and will be removed in SwiftGen 7.0. You should get a proper depreciation notice by Xcode if you use them anyway.

SwiftGen 6.0 Templates Migration Guide

If you're moving from SwiftGen 5.x to SwiftGen 6.0, you'll need to be aware that some templates have been renamed, removed or merged with others. Follow this Migration Guide to use the new name for SwiftGen 6.x of the templates you were previously using with SwiftGen 5.x.

Deprecated templates in SwiftGen 6.0

Colors

Fonts

Storyboards / IB

The templates have been split up into separate templates for each specific functionality, in preparation of future functionalities such as accessibility identifiers.

• One template to generate scene information.
• One template to generate segue information.

⚠️ The storybards parser command from SwiftGen 5.x has been renamed ib in SwiftGen 6.0, so be sure to put those templates in a ib subfolder and not an storyboards subfolder. Also be sure to read the paragraph in the general Migration Guide about how to generate multiple outputs (from multiple templates) for a single input (a single set of input IB files).

Strings

XCAssets

Functionality changes in SwiftGen 6.0

All templates now have swiftlint:disable all at the top, so swiftlint users no longer need to ignore the generated files, although this is still highly recommended.

SwiftGen 6.0 uses the latest Stencil and StencilSwiftKit libraries, so there are plenty of new features for template writers, such as variable subscripting, an indent filter, better error reporting, ...

Fonts

The template now provides a registerAllCustomFonts() function, which can be useful if you use custom fonts in your Interface Builder files. Just call it when your application starts. Otherwise, fonts will still auto-register when they're first used in code.

Note that if you call this method, you don't need to list the custom fonts under the UIAppFonts key of your Info.plist anymore. Calling this method instead of listing your custom fonts in your Info.plist thus has two advantages: you don't have to maintain the list up-to-date anymore when you add/remove a custom font, and it also works well with custom fonts you might embed in your frameworks (which don't have that UIAppFonts key in their own Info.plist).

Storyboards / IB

The segues template now generates a handy initializer on SegueType for use in prepareForSegue, for example:

override func prepare(for segue: UIStoryboardSegue, sender: Any?) {
  switch StoryboardSegue.Message(segue) {
  case .embed?:
    // Prepare for your custom segue transition, passing information to the destionation VC
  case .customBack?:
    // Prepare for your custom segue transition, passing information to the destionation VC
  default:
    // Other segues from other scenes, not handled by this VC
    break
  }
}

The templates now handle the "Inherit module from target" setting in Interface Builder, so you may no longer need to set the module: ... parameter anymore if you have multiple targets.

Strings

A thing of note for some users is that the SwiftGen parser no longer consolidates keys with different casing. This may affect you if you have strings files with inconsistent keys. See the contexts Migration Guide for more information.

XCAssets

All groups (folders) are no longer namespaced by default. A group will now only be namespaced if you've enabled the corresponding "provides namespace" for that group in Xcode. To enable the old behaviour again, use the forceProvidesNamespaces parameter in your config file.

The template now supports NSDataAsset sets, so you can now safely access items such as JSON files or any other data files from your asset catalog.

Some smaller changes:

• The template no longer generates allXXX constants by default. This can be turned on again with the allValues parameter in your config file.
• Together with the previous item, the noAllValues parameter has been removed in favour of the allValues parameter in your config file.
• The old allValues constant (which was an alias for allImages) has been removed, use allImages instead.
• The deprecated Image typealias (to UIImage/NSImage) has been renamed to AssetImageTypeAlias.

Templates 2.1 / SwiftGen 5.1 Migration Guide

Functionality changes in 2.1 (SwiftGen 5.1)

XCAssets

The static allValues constant has been deprecated in favor of the allImages and allColors constants. This is because we've added support for named colors in asset catalogs.

Templates 2.0 / SwiftGen 5.0 Migration Guide

If you're moving from SwiftGen 4.x to SwiftGen 5.0, you'll need to be aware that some templates have been renamed, removed or merged with others. Follow this Migration Guide to use the new name for SwiftGen 5.x of the templates you were previously using with SwiftGen 4.x.

Deprecated templates in 2.0 (SwiftGen 5.0)

The two general themes for this version are:

• Templates now reside in the subfolder corresponding to their parser (colors, fonts, ...) instead of the filename being prefixed with it.
• The default template doesn't exist anymore, templates now specify which swift version they support.

Below is a list of renamed ("➡️") and removed ("❌") templates, grouped by parser. If your template hasn't been renamed or removed, you don't need to do anything ("✅"). You still might want to review the documentation for that template, as there might be new features you may be interested in.

Colors

Fonts

Images / XCAssets

⚠️ The images parser command from SwiftGen 4.x has been renamed xcassets in SwiftGen 5.0, so be sure to put those templates in a xcassets subfolder and not an images subfolder.

Storyboards

Strings

Functionality changes in 2.0 (SwiftGen 5.0)

Storyboards

You'll probably notice that your old codebase won't work with the new generated code. This is because we use a new, swiftier way of generating types for storyboard scenes. What it boils down to is that, if you had the following line in your code base:

StoryboardScene.Message.instantiateMessageList()

It should now become:

StoryboardScene.Message.messageList.instantiate()

💡 Tip: to help you do this transition, you may be interested in using the "compatibility template" we suggest here. It will allow you to generate compatibility code for the old storyboard function calls, generating depreciation warnings + renaming fix-its for that SwiftGen 4.x API. This way you could then use Xcode's "Fix all in scope" feature to let Xcode do the renaming and migration for you!