Swiftpack.co is a collection of thousands of indexed Swift packages. Search packages.
macOS • CentOS • Ubuntu • Amazon Linux
Workspace automates management of Swift projects.
- Provides rigorous validation:
- Generates API documentation.
- Automates code maintenance:
- Automates open source details:
- Designed to interoperate with the Swift Package Manager.
- Manages projects for macOS, Windows, web, CentOS, Ubuntu, tvOS, iOS, Android, Amazon Linux and watchOS.
The Workspace Workflow
(The following demonstration package is a real repository. You can use it to follow along.)
When the Repository Is Cloned
The need to hunt down workflow tools can deter contributors. On the other hand, including them in the repository causes a lot of clutter. To reduce both, when a project using Workspace is pulled, pushed, or cloned...
git clone https://github.com/SDGGiesbrecht/SDGCornerstone
...only one small piece of Workspace comes with it: A short script called
Refresh that has several platform variants.
Hmm... I wish I had more tools at my disposal... Hey! What if I...
Refresh the Project
To refresh the project, double‐click the
Refresh script for your platform. (You can also execute the script from the command line if your system is set up not to execute scripts when they are double‐clicked.)
Refresh opens a terminal window, and in it Workspace reports its actions while it sets the project folder up for development. (This may take a while the first time, but subsequent runs are faster.)
This looks better. Let’s get coding!
[Add this... Remove that... Change something over here...]
...All done. I wonder if I broke anything while I was working? Hey! It looks like I can...
When the project seems ready for a push, merge, or pull request, validate the current state of the project by double‐clicking the
Validate opens a terminal window and in it Workspace runs the project through a series of checks.
When it finishes, it prints a summary of which tests passed and which tests failed.
Oops! I never realized that would happen...
Validatewhen it looks complete.
Wow! That was so much easier than doing it all manually!
While the above workflow is the simplest to learn, Workspace can also be installed as a command line tool that can be used in a wider variety of ways. Most notably, any individual task can be executed in isolation, which can speed things up considerably for users who become familiar with it.
Applying Workspace to a Project
To apply Workspace to a project, run the following command in the root of the project’s repository. (This requires a full install.)
$ workspace refresh
By default, Workspace refrains from tasks which would involve modifying project files. Such tasks must be activated with a configuration file.
optIntoAllTasks() can be used in the configuration file to easily activate everything at once, no matter how much it might end up overwriting.
Workspace provides command line tools.
They can be installed any way Swift packages can be installed. The most direct method is pasting the following into a terminal, which will either install or update them:
curl -sL https://gist.github.com/SDGGiesbrecht/4d76ad2f2b9c7bf9072ca1da9815d7e2/raw/update.sh | bash -s Workspace "https://github.com/SDGGiesbrecht/Workspace" 0.36.2 "workspace help" workspace arbeitsbereich
Workspace provides a library for use with the Swift Package Manager.
Simply add Workspace as a dependency in
let package = Package( name: "MyPackage", dependencies: [ .package( name: "Workspace", url: "https://github.com/SDGGiesbrecht/Workspace", .upToNextMinor(from: Version(0, 36, 2)) ), ], targets: [ .target( name: "MyTarget", dependencies: [ .product(name: "WorkspaceConfiguration", package: "Workspace"), ] ) ] )
The module can then be imported in source files:
The Workspace project is maintained by Jeremy David Giesbrecht.
If Workspace saves you money, consider giving some of it as a donation.
If Workspace saves you time, consider devoting some of it to contributing back to the project.
|Last commit: 18 hours ago|
You may find interesting
0.36.2 - 2021-02-27T23:35:04
- GitHub workflows have been split up so that they can be restarted individually.
- Continuous integration uses Xcode 12.4.
- GitHub‐Arbeitsabläufe wurden aufgeteilt, damit einzelne neugestartet werden können.
- Fortlaufende EInbindung verwendet Xcode 12.4.