Tuist

Log in
releases

Workspace improvements with Tuist 0.13.0

The just baked new version of Tuist, 0.13.0, is already with us. We added significant improvements to workspaces like being able to define additional files that are added to the project. We also aligned the structured of the generated workspaces to match the filesystem. This version also makes sure that for those test targets that depend on a host application are set up with the right settings.

Tuist 0.13.0 has been released! 🎉

We’re taking turns releasing and writing about what’s new in the world of Tuist. I’m Kas and will be your host through this post on the latest developments.

Contributors

In this release Tuist gained a new contributor! @BalestraPatrick fixed a warning in newly generated projects #291. Additionally, @pepicrft and @ollieatkinson have been hard at work blitzing through numerous bug fixes and improvements 👏.

Contributions also come in the form of valuable feedback, a huge shout out to @enhorn for actively reporting issues and suggestions to enhance Tuist.

We’re really grateful for all the community contributions to improving Tuist!

What’s new?

The latest update can be obtained via running:

tuist update

The full changelog can be viewed on the 0.13.0 release page. Here are some highlights.

Homebrew tap support

The Setup.swift manifest now supports brew tap!

import ProjectDescription let setup = Setup([ .homebrewTap(repositories: [“peripheryapp/periphery”]) ])

Calling tuist up will ensure the tap is added to Homebrew.

Workspace Improvements

By default, calling tuist generate will create an Xcode workspace containing the current project and all its dependencies.

New in 0.13.0, the generated Xcode workspace structure reflects the file system!

Additionally, the Workspace.swift manifest has been enhanced to allow the inclusion of files and folder references that don’t necessarily belong to a particular project - your Documentation files can now be included!

import ProjectDescription let workspace = Workspace( name: “Workspace”, projects: [ “App”, “Frameworks/**”, ], additionalFiles: [ “Documentation/**”, .folderReference(path: “Website”) ] )

<img class=”posts__post-screenshot”

alt=”Workspace with additional files and folder references” src=”/marketing/images/blog/2019/04/03/workspace-improvements.png” />

Host application for unit & ui tests

Tuist now automatically sets the host & target application for test targets that declare they depend on applications.

For example take the following Project.swift manifest:

import ProjectDescription let project = Project( name: “App”, targets: [ Target(name: “App”, platform: .iOS, product: .app, bundleId: “io.tuist.App”, infoPlist: “Info.plist”, sources: “Sources/**” ), Target( name: “AppTests”, platform: .iOS, product: .unitTests, bundleId: “io.tuist.AppTests”, infoPlist: “Tests.plist”, sources: “Tests/**”, dependencies: [ .target(name: “App”), ] ), Target( name: “AppUITests”, platform: .iOS, product: .uiTests, bundleId: “io.tuist.AppUITests”, infoPlist: “Tests.plist”, sources: “UITests/**”, dependencies: [ .target(name: “App”), ] ) ] )

The generated project will have the host and target application set to App for the unit and ui test targets.

<img class=”posts__post-screenshot”

alt=”Unit tests target with host application” src=”/marketing/images/blog/2019/04/03/unit-tests-host-application.png” />

<img class=”posts__post-screenshot”

alt=”UI tests target with target application” src=”/marketing/images/blog/2019/04/03/ui-tests-target-application.png” />

What’s next?

  • #265 Storyboard enhancements - adding the ability to automatically generate the appropriate storyboard files via tuist init as well as explicitly specifying them within the Project.swift manifest to include in the generated Xcode project.

  • #160 Multiple configurations - a few different options are being explored, such as environments or possibly even includes to help reduce repeated definitions.

  • #316 Xcode 10.2 & Swift 5 support.

If you have any ideas or feedback on these items or any others, please feel free to reach out on GitHub or Slack!

Happy Xcoding 🛠!

You might also like

releases
Tuist turns 1.0
Today we are pleased the first major release of Tuist, 1.0. We have achieved an important milestone in helping teams scale up their projects, making defining projects easy, and for that reason we are releasing this one as major. This blog post describes what that has been for the project, and what are our ambitions for Tuist 2.0.
product
Expanding the Apple Ecosystem: open and accessible developer tooling beyond official tools
We’re on a mission to make developer tooling outside of Apple’s official tools more open and accessible. Through fair pricing, community-driven features, and language support, Tuist empowers developers to enhance their workflows and build better apps without barriers. Join us in expanding the ecosystem with accessible, community-driven extensions for all.
releases
Releasing Tuist 2.0
In this post, we share more details about this new major version of the project, 2.0, and present the direction we are taking as we move towards 3.0.

Supercharge your app development

Get started