- Fixed
swiftlint
warnings in generated color extensions.
Roman Laitarenko #32 - The storyboards macOS swift3 template was missing the "current target" module ignore code.
@djbe #27 - Fix the
images
templates so that they work on watchOS again.
David Jennes SwiftGen/SwiftGen#275 #30
- More variables have been deprecated, while new variables have been added. See SwiftGenKit#13 for more information.
David Jennes #28 #39 #43
- Switch from Travis CI to Circle CI, clean up the Rakefile in the process.
David Jennes #24 #40 - Disable SwiftLint
conditional_returns_on_newline
in the font template.
Tom Baranes #33 - Updated templates to use Stencil 0.9.0 features, such as for loops with a where condition.
David Jennes #42
The templates tagged with this version are the ones embedded in SwiftGen 4.2.
- Initial tagging of templates as part of being split in their own repository.
- Templates are now linted and unit-tested, to ensure the code generated compiles properly.
@djbe #5 #6 #15 #16
- Use
escapeReservedKeywords
in all templates — to ensure compilation even for scenes named with a reserved keyword.
@djbe #3 #14 - Storyboards templates don't
import
your app module anymore, removing that annoying warning.
@djbe #19- It works by checking the environment variable
PRODUCT_MODULE_NAME
, which is automatically injected by Xcode if you runswiftgen
as part of a Script Build Phase in your Xcode project. - If you don't use
swiftgen
in a Script Build Phase of your Xcode project but manually in the terminal, you can instead useswiftgen storyboards --param module=YourAppModuleName …
when invoking SwiftGen to inject it manually instead.
- It works by checking the environment variable
- Use an explicit bundle parameter to support frameworks for all templates.
@NachoSoto @djbe SwiftGen/SwiftGen#255 #17 - Use
enum
instead ofstruct
for namespacing in all templates.
@djbe #7 - Reworked templates to get rid of deprecated Stencil variables.
@djbe #8 #9
See SwitftGen's own CHANGELOG pre SwiftGen 4.2 version, before the refactoring that led us to split the code in frameworks
Note that in preparation for the upcoming SwiftGen 5.0, some variables available in the SwiftGen's Stencil templates have been deprecated and will be renamed. To prepare for SwiftGen 5.0, we strongly advise to migrate your custom templates so they use the new variables (already available in SwiftGen 4.2 / SwiftGenKit 1.0.1) instead of the old ones, so that they will continue to work in SwiftGen 5.0