dnrops
/
tuist
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
tuist/CHANGELOG.md

446 lines
22 KiB
Markdown
Raw Normal View History

Create project
2018-04-16 17:01:02 +08:00
# Changelog
Add more documentation and Equatable conformance
2018-04-21 18:37:33 +08:00
[version/0.26.0] Update CHANGELOG
2018-04-17 21:08:28 +08:00
Please, check out guidelines: https://keepachangelog.com/en/1.0.0/
Create project
2018-04-16 17:01:02 +08:00
Ensuring the correct platform SDK dependencies path is set (#419) Resolves https://github.com/tuist/tuist/issues/417 - Updating SDK dependency paths to be based on the developer directory and the platform SDK root path Test Plan: - generate the fixture `fixtures/ios_app_with_sdk` via `tuist generate` - Verify the linked system frameworks and libraries have the correct path set based on the platform
2019-06-26 15:44:44 +08:00
## Next
Add related test targets as testables (#818) Resolves https://github.com/tuist/tuist/issues/569 ### Short description 📝 It should be possible to run tests if target has any test targets. ### Solution 📦 This PR finds all related test targets to the test scheme. It was already done for test targets themselves, but the functionality was extended to include all other targets. ### Implementation 👩‍💻👨‍💻 - [x] Added implementation - [x] Added tests ### Test Plan 🛠 Run with `app_with_framework_and_tests` fixture and check that in generated schemes: #### Previous behaviour didn't break 1. `AppTests` scheme has `AppTests` as a testable target. 1. `FrameworkTests` scheme has `FrameworkTests` as a testable target. #### New behaviour works as expected 1. `App` scheme has `AppTests` as a testable target. 1. `Framework` scheme has `FrameworkTests` as a testable target.
2019-12-24 01:18:25 +08:00
- Support ignoring specific source file pattern when adding them to the target https://github.com/tuist/tuist/pull/811 by @vytis.
- Made targets testable if there is a corresponding test target https://github.com/tuist/tuist/pull/818 by @vytis.
Updated changelog
2019-12-18 20:41:38 +08:00
Update CHANGELOG
2019-12-19 23:07:10 +08:00
### Added
- `TuistGalaxy` & `TuistAutomation` targets https://github.com/tuist/tuist/pull/817 by @pepibumur.
Update CHANGELOG and Constants.swift for 1.0.1
2019-12-17 19:12:42 +08:00
## 1.0.1
### Fixed
- Pass through `DEVELOPER_DIR` when set by the environment when determining the path to the currently selected Xcode. @ollieatkinson
Version 1.0.0
2019-12-17 17:30:59 +08:00
## 1.0.0
Update CHANGELOG
2019-12-05 22:12:14 +08:00
### Changed
Update CHANGELOG
2019-12-11 19:14:42 +08:00
Update CHANGELOG
2019-12-05 22:12:14 +08:00
- Run pipelines with Xcode 11.2.1 on CI @pepibumur.
Delete manifests target generation
2019-11-26 22:49:32 +08:00
### Removed
Update CHANGELOG
2019-11-28 22:22:51 +08:00
Mark change as breaking
2019-11-26 23:02:48 +08:00
- **Breaking** Generate manifests target as part of the generated project https://github.com/tuist/tuist/pull/724 by @pepibumur.
Remove the installer check that verifies whether the Swift version is compatible.
2019-11-28 21:10:01 +08:00
- The installation no longer checks if the Swift version is compatible https://github.com/tuist/tuist/pull/727 by @pepibumur.
Update CHANGELOG
2019-12-07 01:13:51 +08:00
- Don't include the manifests in the generated workspace https://github.com/tuist/tuist/pull/754 by @pepibumur.
Delete manifests target generation
2019-11-26 22:49:32 +08:00
Update CHANGELOG
2019-11-22 17:05:12 +08:00
### Added
- Add `ProjectDescription.Settings.defaultSettings` none case that don't override any `Project` or `Target` settings. https://github.com/tuist/tuist/pull/698 by @rowwingman.
- `ProjectEditor` utility https://github.com/tuist/tuist/pull/702 by @pepibumur.
Update change log
2019-11-24 06:21:19 +08:00
- Fix warnings in the project, refactor SHA256 diegest code https://github.com/tuist/tuist/pull/704 by @rowwingman.
Added support for custom Archive Action when defining scheme
2019-10-03 18:39:44 +08:00
- Define `ArchiveAction` on `Scheme` https://github.com/tuist/tuist/pull/697 by @grsouza.
Update CHANGELOG
2019-11-26 01:17:29 +08:00
- `tuist edit` command https://github.com/tuist/tuist/pull/703 by @pepibumur.
Update CHANGELOG
2019-11-27 01:36:56 +08:00
- Support interpolating formatted strings in the printer https://github.com/tuist/tuist/pull/726 by @pepibumur.
Update CHANGELOG
2019-11-28 01:54:31 +08:00
- Support for paths relative to root https://github.com/tuist/tuist/pull/727 by @pepibumur.
[changelog] Update changelog
2019-11-28 07:10:24 +08:00
- Replace `Sheme.testAction.targets` type from `String` to `TestableTarget` is a description of target that adds to the `TestAction`, you can specify execution tests parallelizable, random execution order or skip tests https://github.com/tuist/tuist/pull/728 by @rowwingman.
Update CHANGELOG
2019-11-28 22:22:51 +08:00
- Galaxy manifest model https://github.com/tuist/tuist/pull/729 by @pepibumur.
Update CHANGELOG
2019-12-07 01:13:51 +08:00
- Make scheme generation methods more generic https://github.com/tuist/tuist/pull/730 by @adamkhazi @kwridan.
Workspace Schemes (#752) Resolves https://github.com/tuist/tuist/issues/667 ### Short description 📝 A follow up to https://github.com/tuist/tuist/pull/730 where workspace schemes are exposed in the `ProjectDescription`. This is the final step of the steps included in the issue. ### Solution 📦 Expose `TargetReference` for both project and workspace schemes. Users can use `.project(path: "sometime/somepath", name: "targetname")` to reference targets within custom workspace schemes. Due to how the generation process works (especially how `generatedProjects` are populated in the `ProjectGenerator`), `.project(path: .., name: ..)` we cannot reference remote targets in project schemes yet without some changes in the `ProjectGenerator`. This is not a problem for workspace schemes. Since the `ProjectDescription` `Scheme` is shared by both workspaces and projects, I've added a scheme linting rule to check that targets defined in custom project schemes are within the current project i.e., not referencing remote targets in other projects. ### Implementation 👩‍💻👨‍💻 - [X] Update `ProjectDescription` to support `TargetReference` - [X] Add Project scheme linter for the referencing remote targets invalid case - [X] Update fixture `ios_app_with_custom_scheme` to add workspace scheme
2019-12-11 00:05:52 +08:00
- Workspace Schemes https://github.com/tuist/tuist/pull/752 by @adamkhazi @kwridan.
Update CHANGELOG
2019-12-03 15:07:22 +08:00
- `SimulatorController` with method to fetch the runtimes https://github.com/tuist/tuist/pull/746 by @pepibumur.
Update CHANGELOG
2019-12-07 20:57:43 +08:00
- Add RxSwift as a dependency of `TuistKit` https://github.com/tuist/tuist/pull/760 by @pepibumur.
Update CHANGELOG
2019-12-07 22:01:34 +08:00
- Add cache command https://github.com/tuist/tuist/pull/762 by @pepibumur.
Add utility to compile xcframeworks
2019-12-07 20:45:39 +08:00
- Utility to build xcframeworks https://github.com/tuist/tuist/pull/759 by @pepibumur.
Update CHANGELOG
2019-12-08 00:13:15 +08:00
- Add `CacheStoraging` protocol and a implementation for a local cache https://github.com/tuist/tuist/pull/763 by @pepibumur.
Update CHANGELOG
2019-12-08 01:32:45 +08:00
- Add support for changing the cache and versions directory using environment variables https://github.com/tuist/tuist/pull/765 by @pepibumur.
Update CHANGELOG
2019-12-09 09:50:21 +08:00
- Reactive interface to the System utility https://github.com/tuist/tuist/pull/770 by @pepibumur
Update CHANGELOG
2019-12-11 19:14:42 +08:00
- Workflow to make sure that documentation and website build https://github.com/tuist/tuist/pull/783 by @pepibumur.
Version 1.0.0
2019-12-17 17:30:59 +08:00
- Support for `xcframework` https://github.com/tuist/tuist/pull/769 by @lakpa
Support generating info.plist for Watch Apps & Extensions (#756) Part of: https://github.com/tuist/tuist/issues/628 - Added watchOS App / Extension defaults to the info plist content provider - Watch apps reference their host applications bundle identifier in the info plist `WKCompanionAppBundleIdentifier` key - Watch app extensions reference their host watch apps bundle identifier in the info plist `NSExtension.NSExtensionAttributes.WKAppBundleIdentifier` - As such the parent project is now used to perform lookups for those hosts to extract their bundle identifiers - Updated fixture to leverage generated info.plist files Test Plan: - run `tuist generate` within `fixtures/ios_app_with_watchapp2` - Verify the info.plist files generated in `Derrived/InfoPlists` matche the ones created by Xcode (They were previously checked in under `Support`)
2019-12-16 04:40:12 +08:00
- Support generating info.plist for Watch Apps & Extensions https://github.com/tuist/tuist/pull/756 by @kwridan
ProjectDescription.Settings provide none case for default settings
2019-11-20 07:31:01 +08:00
Ensure custom search path settings are included in generated projects (#751) Resolves https://github.com/tuist/tuist/issues/750 - The previous logic was setting the `$(inherited)` and the derived search paths seperately - This caused the derrived search paths to replace any existing custom settings - To solve this, we can set the derived search paths and the `$(inherited)` setting as one setting - This allows the extend helper method to extend existing settings Test Plan: - Run `tuist generate` within `fixtures/ios_app_with_static_libraries` - Inspect the generated workspace, Module A should have a `$(SRCROOT/CustomHeader` header search path
2019-12-05 21:53:14 +08:00
### Fixed
- Ensure custom search path settings are included in generated projects https://github.com/tuist/tuist/pull/751 by @kwridan
Remove duplicate HEADER_SEARCH_PATHS (#787) - In the even two library dependencies shared the same `publicHeaders` path (e.g. `libcrypto.a` and `libssl.a` in OpenSSL) duplicate entries were added to the `HEADER_SEARCH_PATHS` build setting - This was regressed due to an earlier change https://github.com/tuist/tuist/pull/751 - previously the uniquing was happening in the settings helper when build settings were extended multiple times - To resolve this, we now ensure we unique paths being added - Additionally a test is included to ensure this doesn't regress in the future Test Plan: - Verify the unit tests pass A bit of a contrived manual test case update the fixture in `fixtures/ios_app_with_static_libraries/Modules/A/Project.swift` ```swift let project = Project(name: "A", targets: [ Target(name: "A", platform: .iOS, product: .staticLibrary, bundleId: "io.tuist.A", infoPlist: "Info.plist", sources: "Sources/**", dependencies: [ .project(target: "B", path: "../B"), .library(path: "../C/prebuilt/C/libC.a", publicHeaders: "../C/prebuilt/C", swiftModuleMap: "../C/prebuilt/C/C.swiftmodule"), // Add a duplicate .library(path: "../C/prebuilt/C/libC.a", publicHeaders: "../C/prebuilt/C", swiftModuleMap: "../C/prebuilt/C/C.swiftmodule") ]) ]) ``` This of course causes a duplicate binary (hence why it wasn't included) but can help illustrate a situation where two `.library` dependencies point to the same `publicHeaders` path.
2019-12-13 01:33:41 +08:00
- Remove duplicate HEADER_SEARCH_PATHS https://github.com/tuist/tuist/pull/787 by @kwridan
Update CHANGELOG
2019-12-16 03:06:11 +08:00
- Fix unstable scheme generation https://github.com/tuist/tuist/pull/790 by @marciniwanicki
Update changelog
2019-12-16 05:12:24 +08:00
- Add defaultConfigurationName to generated projects https://github.com/tuist/tuist/pull/793 by @kwridan
Add knownRegions to generated projects (#792) - Generated projects were missing an exhaustive list of known regions. - This causes Xcode to immediately modify generated projects on launch to fix this. - Based on localizable resources we can infer the knownRegions of the project - While adding localizable resource file elements we can keep track of the languages encountered - This can then be used to set a complete set of knownRegions Test Plan: - Run `tuist generate` within `fixtures/ios_app_with_framework_and_resources` - Verify the generated project MainApp has both "English" and "French" in the list of localizations in the project's info tab
2019-12-17 00:21:42 +08:00
- Add knownRegions to generated projects https://github.com/tuist/tuist/pull/792 by @kwridan
Ensure custom search path settings are included in generated projects (#751) Resolves https://github.com/tuist/tuist/issues/750 - The previous logic was setting the `$(inherited)` and the derived search paths seperately - This caused the derrived search paths to replace any existing custom settings - To solve this, we can set the derived search paths and the `$(inherited)` setting as one setting - This allows the extend helper method to extend existing settings Test Plan: - Run `tuist generate` within `fixtures/ios_app_with_static_libraries` - Inspect the generated workspace, Module A should have a `$(SRCROOT/CustomHeader` header search path
2019-12-05 21:53:14 +08:00
Version 0.19.0
2019-11-15 01:17:07 +08:00
## 0.19.0
Add HTTPClient utility (#508) * Remove old Ruby installation scripts and update the installation command to point to the install.tuist.io domain * Create a version file in the latest directory * Add HTTPClient with a read method to download Data from a URL * Some style fixes * Address Marcin's comments on the PR * Update CHANGELOG * Style fix * Address Kas's comments * Fix tests
2019-10-08 21:14:31 +08:00
### Added
Add XCTAssertThrowsSpecific (#535) * Add XCTAssertThrowsSpecific and add its usage. * Print expected error. * Replace more instances with XCTAssertThrowsSpecific. * Run swiftformat. * Fix tests compiler error. * Updated Changelog. * Run swiftormat. * Remove redundant swiftlint disable rule. * Fix swiftlint violation of line length.
2019-10-10 22:53:46 +08:00
- XCTAssertThrowsSpecific convenient function to test for specific errors https://github.com/tuist/tuist/pull/535 by @fortmarek
Add HTTPClient utility (#508) * Remove old Ruby installation scripts and update the installation command to point to the install.tuist.io domain * Create a version file in the latest directory * Add HTTPClient with a read method to download Data from a URL * Some style fixes * Address Marcin's comments on the PR * Update CHANGELOG * Style fix * Address Kas's comments * Fix tests
2019-10-08 21:14:31 +08:00
- `HTTPClient` utility class to `TuistEnvKit` https://github.com/tuist/tuist/pull/508 by @pepibumur.
Add support for sticker pack extension & app extension products (#489) * Add support for sticker pack product * Add support for extensions & rename sticker product * Update documentation * Add package type for app extensions * Add tests for app extension integration * Update product tests * swiftformat * Add fixture & acceptance tests * update change log
2019-10-30 02:42:21 +08:00
- **Breaking** Allow specifying a deployment target within project manifests https://github.com/tuist/tuist/pull/541 by @mollyIV
- Add support for sticker pack extension & app extension products https://github.com/tuist/tuist/pull/489 by @Rag0n
Add support for watchOS apps (#623) ### Short description Adds support for watchOS apps. ### Solution Add support for watchOS / watchOS Extension products as well as the appropriate dependency rules. ### Implementation - [x] Add product types - [x] Add fixture & acceptance test - [x] Update graph / link rules - [x] Add embed watch build phase - [x] Add watch build settings - [x] Add linter rules for bundle IDs - [x] Add linter rules for valid product types - [x] Update changelog - [x] Update documentation ### Test Plan - Run `tuist generate` within `fixtures/ios_app_with_watchapp2` - Verify the generated project contains a Watch App & Watch App Extension - Compare against a manually created project with a Watch App
2019-11-06 21:36:43 +08:00
- Utility to locate the root directory of a project https://github.com/tuist/tuist/pull/622 by @pepibumur.
- Adds `codeCoverageTargets` to `TestAction` to make XCode gather coverage info only for that targets https://github.com/tuist/tuist/pull/619 by @abbasmousavi
Enable the library evolution for the ProjectDescription framework (#625) * Enable the library evololution for the ProjectDescription framework * Update CHANGELOG * Update installer to pass the argument too * Gitignore .github files * Fix tests * Fix tests
2019-11-04 20:49:36 +08:00
- Enable the library evololution for the ProjectDescription framework https://github.com/tuist/tuist/pull/625 by @pepibumur.
Add support for watchOS apps (#623) ### Short description Adds support for watchOS apps. ### Solution Add support for watchOS / watchOS Extension products as well as the appropriate dependency rules. ### Implementation - [x] Add product types - [x] Add fixture & acceptance test - [x] Update graph / link rules - [x] Add embed watch build phase - [x] Add watch build settings - [x] Add linter rules for bundle IDs - [x] Add linter rules for valid product types - [x] Update changelog - [x] Update documentation ### Test Plan - Run `tuist generate` within `fixtures/ios_app_with_watchapp2` - Verify the generated project contains a Watch App & Watch App Extension - Compare against a manually created project with a Watch App
2019-11-06 21:36:43 +08:00
- Add support for watchOS apps https://github.com/tuist/tuist/pull/623 by @kwridan
Lint that duplicate dependencies doesn't exist (#629) * Lint that duplicate dependencies doesn't exist * Update change log
2019-11-11 18:37:50 +08:00
- Add linting for duplicate dependencies https://github.com/tuist/tuist/pull/629 by @lakpa
Add HTTPClient utility (#508) * Remove old Ruby installation scripts and update the installation command to point to the install.tuist.io domain * Create a version file in the latest directory * Add HTTPClient with a read method to download Data from a URL * Some style fixes * Address Marcin's comments on the PR * Update CHANGELOG * Style fix * Address Kas's comments * Fix tests
2019-10-08 21:14:31 +08:00
Shared system instance (#519) * Add System.shared * Implement TuistTestCase, TusitUnitTestCase, and refactor all the tests to use those classes instead. Make some progress Refactor tests to use TuistUnitTestCase Create TuistTestCase * Fix some tests * Update the documentation to indicate that there is more than one integration tests target * Update the CHANGELOG * Indicate the product that we build for release * Remove unnecessary methods
2019-10-10 17:28:51 +08:00
### Changed
Switch dependencies from branch to version. (#631) * Switch dependencies from branch to version. * Update CHANGELOG.
2019-11-11 18:33:17 +08:00
- Change dependencies in `Package.resolved` to version from branch https://github.com/tuist/tuist/pull/631 by @fortmarek
Rename Core to Support (#621) * Rename Core to Support * Fix acceptance tests
2019-11-01 15:35:06 +08:00
- Rename `TuistCore` to `TuistSupport` https://github.com/tuist/tuist/pull/621 by @pepibumur.
Shared system instance (#519) * Add System.shared * Implement TuistTestCase, TusitUnitTestCase, and refactor all the tests to use those classes instead. Make some progress Refactor tests to use TuistUnitTestCase Create TuistTestCase * Fix some tests * Update the documentation to indicate that there is more than one integration tests target * Update the CHANGELOG * Indicate the product that we build for release * Remove unnecessary methods
2019-10-10 17:28:51 +08:00
- Introduce `Systems.shared`, `TuistTestCase`, and `TuistUnitTestCase` https://github.com/tuist/tuist/pull/519 by @pepibumur.
Change Object Version Behaviour to Mimic Xcode 11 (#615) * object version 52 only when spm included * swiftformat * changelog
2019-10-29 16:16:47 +08:00
- Change generated object version behaviour to mimic Xcode 11 by @adamkhazi
[package-api] Refine API for Swift Packages (#578) * [package-api] Update package API to better handle multiple dependecies per package * swiftformat . * resolve unit test querying wrong lint issue * [package-api] update ios_app_with_static_library_and_package * swiftformat . * swiftformat . * Rename PackageDependencyNode, refactor LinkGenerator, add comment for Package * wording * Remove redundant method parameters * Update documentation & changelog * Fix tests
2019-10-30 00:13:00 +08:00
- **Breaking** Refine API for Swift Packages https://github.com/tuist/tuist/pull/578 by @ollieatkinson
Support ability to locate multiple Tuist directories (#630) * Support ability to locate multiple Tuist directories - The logic has been modified to consult the file system and the cache when traversing the hierarchy Test Plan: - Verify unit tests continue to pass * Update changelog * Correct test to ensure multiple directories are supported
2019-11-11 22:22:07 +08:00
- Support ability to locate multiple Tuist directories https://github.com/tuist/tuist/pull/630 by @kwridan
Shared system instance (#519) * Add System.shared * Implement TuistTestCase, TusitUnitTestCase, and refactor all the tests to use those classes instead. Make some progress Refactor tests to use TuistUnitTestCase Create TuistTestCase * Fix some tests * Update the documentation to indicate that there is more than one integration tests target * Update the CHANGELOG * Indicate the product that we build for release * Remove unnecessary methods
2019-10-10 17:28:51 +08:00
Fix false positive cycle detection (#546) Resolves: https://github.com/tuist/tuist/issues/460 - Implemented depth first search to check for cycles once the graph is fully constructed - Changed the order in which target nodes are added to the cache to prevent infinite loops in the event of cycles being present Test Plan: - Run `tuist generate` within `fixtures/ios_workspace_with_dependency_cycle` - Verify a cycle error is displayed
2019-10-15 21:26:07 +08:00
### Fixed
- Fix false positive cycle detection https://github.com/tuist/tuist/pull/546 by @kwridan
Fix test target build settings (#661) Resolves: https://github.com/tuist/tuist/issues/660 - Ensure the `LD_RUNPATH_SEARCH_PATHS` build setting is set for test targets Test Plan: - Generate `fixtures/ios_app_with_tests` - Verify the generated project's test target contains a valid `LD_RUNPATH_SEARCH_PATHS` build setting
2019-11-13 22:06:30 +08:00
- Fix test target build settings https://github.com/tuist/tuist/pull/661 by @kwridan
Fix hosted unit test dependencies (#664) Resolves: https://github.com/tuist/tuist/issues/658 - Unit test targets that were hosted in an application were including redundant (transitive) dependencies - This in some cases caused duplicate symbols errors during runtime when the dependencies were static products - The link and embed graph methods now exclude transitive dependencies that are already linked - Additionally, for hosted unit test targets, all static products also included by host apps are also excluded (even if they have a direct dependency on it, this is to avoid duplicate symbols) Test Plan: - Run `tuist generate` within `fixtures/ios_app_with_static_frameworks` - Verify the unit test target doesn't link any products - Run `tuist generate` within `fixtures/ios_app_with_frameworks` - Verify the unit test target doesn't transitively link/embed its host application's dependencies
2019-11-14 19:24:09 +08:00
- Fix hosted unit test dependencies https://github.com/tuist/tuist/pull/664/ by @kwridan
Fix false positive cycle detection (#546) Resolves: https://github.com/tuist/tuist/issues/460 - Implemented depth first search to check for cycles once the graph is fully constructed - Changed the order in which target nodes are added to the cache to prevent infinite loops in the event of cycles being present Test Plan: - Run `tuist generate` within `fixtures/ios_workspace_with_dependency_cycle` - Verify a cycle error is displayed
2019-10-15 21:26:07 +08:00
Version 0.18.1
2019-09-30 16:35:07 +08:00
## 0.18.1
Product name variables don't evaluate in all usage points (#518) - Variables support in product names was first introduced in https://github.com/tuist/tuist/pull/494 - For now to mitigate the bug this causes we are reverting the change - Another solution will need to be devised to support this feature to ensure variables can be evaluated in all usage points
2019-09-30 16:30:29 +08:00
### Removed
Version 0.18.1
2019-09-30 16:35:07 +08:00
- Reverting https://github.com/tuist/tuist/pull/494 using variables in `productName` doesn't evaluate in all usage points within the generated project
Product name variables don't evaluate in all usage points (#518) - Variables support in product names was first introduced in https://github.com/tuist/tuist/pull/494 - For now to mitigate the bug this causes we are reverting the change - Another solution will need to be devised to support this feature to ensure variables can be evaluated in all usage points
2019-09-30 16:30:29 +08:00
Version 0.18.0
2019-09-29 03:12:09 +08:00
## 0.18.0
Add new InfoPlist.extendingDefault case (#448) * Add .extendingDefault option to the InfoPlist model * Use the InfoPlistContentProvider to generate the Info.plist content when it's a .extendingDefault Info.plist. * Implement the InfoPlistContentProvider * Test InfoPlistContentProvider * Add acceptance tests * Add documentation * Update CHANGELOG * Address comments on the PR * Fix linting issues
2019-09-03 23:50:26 +08:00
### Added
- New InfoPlist type, `.extendingDefault([:])` https://github.com/tuist/tuist/pull/448 by @pepibumur
Print the codesign output (#492) * Print the codesign output * Update CHANGELOG
2019-09-10 17:41:39 +08:00
- Forward the output of the `codesign` command to make debugging easier when the copy frameworks command fails https://github.com/tuist/tuist/pull/492 by @pepibumur.
Multiline settings (#464) Partially resolves https://github.com/tuist/tuist/issues/425 ### Short description All individual settings are currently represented by strings. Xcode can read and interpret the values correctly but once the project is modified, it serializes multi-value settings as arrays what can result in an unexpected diff. ### Solution By using an enum, we can control how settings will be serialized. ``` public enum SettingValue { case string(String) case array([String]) // ... } ```
2019-09-11 19:13:18 +08:00
- Support for multi-line settings (see [how to migrate](https://github.com/tuist/tuist/pull/464#issuecomment-529673717)) https://github.com/tuist/tuist/pull/464 by @marciniwanicki
Updated changelog.
2019-09-23 01:32:34 +08:00
- Support for SPM https://github.com/tuist/tuist/pull/394 by @pepibumur & @fortmarek & @kwridan & @ollieatkinson
Code review
2019-09-24 16:28:58 +08:00
- Xcode 11 Support by @ollieatkinson
Add new InfoPlist.extendingDefault case (#448) * Add .extendingDefault option to the InfoPlist model * Use the InfoPlistContentProvider to generate the Info.plist content when it's a .extendingDefault Info.plist. * Implement the InfoPlistContentProvider * Test InfoPlistContentProvider * Add acceptance tests * Add documentation * Update CHANGELOG * Address comments on the PR * Fix linting issues
2019-09-03 23:50:26 +08:00
Transitively Link Static Dependency's Dynamic Dependencies Correctly (#484) Resolves https://github.com/tuist/tuist/issues/455 ### Short description 📝 > When a static dependency has a dynamic dependencies, those dynamic dependencies need to be linked at the point the static dependency is linked. This PR fixes the issue where a static dependency's dynamic libraries were linking incorrectly. ### Solution 📦 As we already traverse the graph for static dependencies, we can add a step to this process to check each static dependency's `targetDependencies` for dynamic libraries and add them as a reference adjacent to where the original static dependency is referenced. ### Implementation 👩‍💻👨‍💻 - [X] Update `linkableDependencies` in `Graph.swift` to reference a static dependency's dynamic libraries - [X] Update `GraphTests` to check the test case: - A (App) -> B (Static) -> C (Dynamic) - Expected: A -> C - [X] Update `GraphTests` to check the test case: - A (App) -> B (Dynamic) -> C (Static) -> D (Static) -> E (Dynamic) - Expected: A -> B - Expected: B -> (C, D, E) - [X] Update `GraphTests` to check the test case: - A (App) -> B (Dynamic) -> C (Dynamic) -> D (Static) -> E (Static) -> F (Dynamic) - Expected: B -> C ### Test Plan - Run `tuist generate` inside `fixtures/ios_app_with_static_frameworks` - Check that the `App` target has `D` inside `Build Phases -> Link Binary With Libraries`
2019-08-21 18:29:23 +08:00
### Fixed
Add new InfoPlist.extendingDefault case (#448) * Add .extendingDefault option to the InfoPlist model * Use the InfoPlistContentProvider to generate the Info.plist content when it's a .extendingDefault Info.plist. * Implement the InfoPlistContentProvider * Test InfoPlistContentProvider * Add acceptance tests * Add documentation * Update CHANGELOG * Address comments on the PR * Fix linting issues
2019-09-03 23:50:26 +08:00
Transitively Link Static Dependency's Dynamic Dependencies Correctly (#484) Resolves https://github.com/tuist/tuist/issues/455 ### Short description 📝 > When a static dependency has a dynamic dependencies, those dynamic dependencies need to be linked at the point the static dependency is linked. This PR fixes the issue where a static dependency's dynamic libraries were linking incorrectly. ### Solution 📦 As we already traverse the graph for static dependencies, we can add a step to this process to check each static dependency's `targetDependencies` for dynamic libraries and add them as a reference adjacent to where the original static dependency is referenced. ### Implementation 👩‍💻👨‍💻 - [X] Update `linkableDependencies` in `Graph.swift` to reference a static dependency's dynamic libraries - [X] Update `GraphTests` to check the test case: - A (App) -> B (Static) -> C (Dynamic) - Expected: A -> C - [X] Update `GraphTests` to check the test case: - A (App) -> B (Dynamic) -> C (Static) -> D (Static) -> E (Dynamic) - Expected: A -> B - Expected: B -> (C, D, E) - [X] Update `GraphTests` to check the test case: - A (App) -> B (Dynamic) -> C (Dynamic) -> D (Static) -> E (Static) -> F (Dynamic) - Expected: B -> C ### Test Plan - Run `tuist generate` inside `fixtures/ios_app_with_static_frameworks` - Check that the `App` target has `D` inside `Build Phases -> Link Binary With Libraries`
2019-08-21 18:29:23 +08:00
- Transitively link static dependency's dynamic dependencies correctly https://github.com/tuist/tuist/pull/484 by @adamkhazi
Prevent embedding static frameworks (#490) Resolves https://github.com/tuist/tuist/issues/454 - All `FrameworkNodes` (i.e. prebuilt frameworks) were being embedded regardless of their linkage - This check was redundant as there was a more general check for `PrecompiledNode` which happens to be the super class of `FrameworkNode` which took into account the framework linkage - To resolve this issue it was suffice to remove the redundant check Test Plan: - Generate `fixtures/ios_app_with_static_frameworks` via running `tuist generate` - Verify the generated project doesn't embed `PrebuiltStaticFramework` - Verify the generated project builds successfully
2019-08-30 18:11:19 +08:00
- Prevent embedding static frameworks https://github.com/tuist/tuist/pull/490 by @kwridan
Fix non-coloured tuistenv output (#493) * Rename EnvironmentController to Environment * Add the Environment.shouldOutputBeColoured variable * Color the output if it's a interactive terminal or there's a environment variable to force so * Add CHANGELOG entry and fix swiftlint issue * Address comments * Fix the logic that determines if the output should be coloured
2019-09-19 03:34:03 +08:00
- Output losing its format when tuist is run through `tuistenv` https://github.com/tuist/tuist/pull/493 by @pepibumur
Support variables in product name (#494) * Support variables in the product name * Update tests * Update CHANGELOG.md * Fix variable names * Fix linting issues * Update variable used in test
2019-09-19 21:31:10 +08:00
- Product name linting failing when it contains variables https://github.com/tuist/tuist/pull/494 by @dcvz
Fix build phases not being generated in the right positions (#506) * Fix build phases not being generated in the right positions * Remove extra space * Add CHANGELOG entry * Fix step * Fix tests * Address comments * Add missing line
2019-09-20 14:48:09 +08:00
- Build phases not generated in the right position https://github.com/tuist/tuist/pull/506 by @pepibumur
Update CHANGELOG
2019-09-25 05:41:05 +08:00
- Remove \$(SRCROOT) from being included in `Info.plist` path https://github.com/tuist/tuist/pull/511 by @dcvz
Prevent generation of redundant file elements (#515) - File elements for all dependencies are products within a graph were always generated and included in projects without applying any filtering - This led to the inclusion of redundant file elements in top level projects (for products & dependencies that they didn't require) - The graph helper methods are now consulted to obtain a list of dependency references that are known to be required by the project - Additional helpers methods on graph were add to help unify / share some of the business logic regarding which dependencies are needed Test Plan: - Generate the fixture `fixtures/ios_app_with_frameworks` via `tuist generate` - Open the generated Workspace - Verify the `Framework3` project doesn't contain file references for `Framework5` - Verify the `Framework3` project doesn't contain file references for `ARKit.framework` - Verify the `Framework4` project doesn't contain file references for `ARKit.framework`
2019-10-04 04:51:09 +08:00
- Prevent generation of redundant file elements https://github.com/tuist/tuist/pull/515 by @kwridan
Transitively Link Static Dependency's Dynamic Dependencies Correctly (#484) Resolves https://github.com/tuist/tuist/issues/455 ### Short description 📝 > When a static dependency has a dynamic dependencies, those dynamic dependencies need to be linked at the point the static dependency is linked. This PR fixes the issue where a static dependency's dynamic libraries were linking incorrectly. ### Solution 📦 As we already traverse the graph for static dependencies, we can add a step to this process to check each static dependency's `targetDependencies` for dynamic libraries and add them as a reference adjacent to where the original static dependency is referenced. ### Implementation 👩‍💻👨‍💻 - [X] Update `linkableDependencies` in `Graph.swift` to reference a static dependency's dynamic libraries - [X] Update `GraphTests` to check the test case: - A (App) -> B (Static) -> C (Dynamic) - Expected: A -> C - [X] Update `GraphTests` to check the test case: - A (App) -> B (Dynamic) -> C (Static) -> D (Static) -> E (Dynamic) - Expected: A -> B - Expected: B -> (C, D, E) - [X] Update `GraphTests` to check the test case: - A (App) -> B (Dynamic) -> C (Dynamic) -> D (Static) -> E (Static) -> F (Dynamic) - Expected: B -> C ### Test Plan - Run `tuist generate` inside `fixtures/ios_app_with_static_frameworks` - Check that the `App` target has `D` inside `Build Phases -> Link Binary With Libraries`
2019-08-21 18:29:23 +08:00
Version 0.17.0
2019-08-14 23:25:38 +08:00
## 0.17.0
Add "tuist graph" command (#427) * Implement class to generate the dotgraph as a string * Add GraphCommand * Register command * Add command to export the graph * Fix graph syntax error * Don't generate manifest targets when printing the graph * Add tests * Update CHANGELOG * Add documentation * Add the graph.dot file to the gitignore * Address comments * Don't lint when generating the graph
2019-07-02 22:13:27 +08:00
### Added
Create a symlink, swift-project pointing to /usr/local/bin/tuist (#447) * Create a symlink swift-project that targets tuist * Update CHANGELOG
2019-07-18 21:48:45 +08:00
Add "tuist graph" command (#427) * Implement class to generate the dotgraph as a string * Add GraphCommand * Register command * Add command to export the graph * Fix graph syntax error * Don't generate manifest targets when printing the graph * Add tests * Update CHANGELOG * Add documentation * Add the graph.dot file to the gitignore * Address comments * Don't lint when generating the graph
2019-07-02 22:13:27 +08:00
- `tuist graph` command https://github.com/tuist/tuist/pull/427 by @pepibumur.
Update CHANGELOG and docs
2019-07-04 20:47:11 +08:00
- Allow customisation of `productName` in the project Manifest https://github.com/tuist/tuist/pull/435 by @ollieatkinson
Adding support for static products depending on dynamic frameworks (#439) - Updating lint rules to allow static products to depend on dynamic frameworks - Updating fixture to include scenario where a static framework depends on a dynamic framework Test Plan: - Verify unit tests pass via `swift tests` - Verify acceptance tests pass via `bundle exec rake tests` Manually: - Run `tuist generate` within `fixtures/ios_app_with_static_frameworks` - Verify the generation is successful - Open the generated workspace - Verify D is embedded in App and CTests - Verify the app compiles runs
2019-07-10 17:58:00 +08:00
- Adding support for static products depending on dynamic frameworks https://github.com/tuist/tuist/pull/439 by @kwridan
Create a symlink, swift-project pointing to /usr/local/bin/tuist (#447) * Create a symlink swift-project that targets tuist * Update CHANGELOG
2019-07-18 21:48:45 +08:00
- Support for executing Tuist by running `swift project ...` https://github.com/tuist/tuist/pull/447 by @pepibumur.
Add new manifest file, TuistConfig.swift (#446) * Add TuistConfig manifest model * Add TuistConfig to the TuistGenerator * Use the TuistConfig generationOptions to determine whether the manifest elements should be generated * Generate a TuistConfig.swift when initialing a project using 'tuist init' * Add documentation * Add documentation * Update CHANGELOG * Fix tests
2019-07-22 15:05:23 +08:00
- New manifest model, `TuistConfig`, to easily configure Tuist's functionalities https://github.com/tuist/tuist/pull/446 by @pepibumur.
Adding ability to re-generate individual projects (#457) Resolves https://github.com/tuist/tuist/issues/452 ### Short description To support workflows where only the local project needs to be re-generated without re-generating all its dependencies a new generation option is needed (see https://github.com/tuist/tuist/issues/452 for full rationale) ### Solution Add a new option to generate the local project only. usage: ```bash tuist generate --project-only ``` ### Implementation - [x] Expose new generator method that generates a single project - [x] Expose new option via command line argument `--project-only` - [x] Update documentation - [x] Update changelog ### Test Plan - Run `tuist generate` within `fixtures/ios_app_with_custom_workspace` - Verify the workspace is still generated with all the dependencies as before - Run `tuist generate` within `fixtures/ios_app_with_custom_workspace/App` - Verify the project workspace is still generated with all the dependencies as before - Run `tuist generate --project-only` within `fixtures/ios_app_with_custom_workspace/App` - Verify only the `App`'s project re-generated (this can be done by either doing a git clean before running the command and then verifying that the only Xcode project is for `App` or by manually modifying any of the projects and verifying they don't update)
2019-07-24 18:39:04 +08:00
- Adding ability to re-generate individual projects https://github.com/tuist/tuist/pull/457 by @kwridan
Support Multiple Header Paths (#459) Resolves https://github.com/tuist/tuist/issues/354 ### Short description 📝 Add support to specify array of paths / glob patterns for headers such as the case below: ``` Headers(public: ["Sources/A/**/*.h", "Sources/B/**/*.h"], private: ["Sources/C/**/*.h", "Sources/D/**/*.h"], project: "Sources/E/**/*.h") ``` ### Solution 📦 Similar to the way multiple source file paths/glob patterns were implemented (https://github.com/tuist/tuist/pull/266). We can use `FileList` and `ExpressibleByStringLiteral` to expose public, private and project headers as either a String or Array of Strings. The original `FileList` used for sources was not reused as it contained `compilerFlags` which is specific to source files. A new `FileList` containing only paths/glob patterns was created for use with headers. This way `FileList` can be potentially reused elsewhere. ### Implementation 👩‍💻👨‍💻 - [X] Remove `FileList` type alias from `SourceFilesList` and references to it - [X] Create new `FileList` without `compilerFlags` - [X] Modify `Headers` to use the new `FileList` for public, private and project headers - [X] Add tests to `GeneratorModelLoaderTests` to verify newly supported cases work - [X] Create `ios_app_with_headers` fixture to support new array of strings case for headers - [X] Write test that verifies `ios_app_with_headers` fixture targets build ### Test Plan - Run `tuist generate` inside the `ios_app_with_headers` fixture - Verify that the Framework1 target has the correct header files specified in the manifest
2019-07-25 20:56:40 +08:00
- Support multiple header paths https://github.com/tuist/tuist/pull/459 by @adamkhazi
Allow specifying multiple configurations within project manifests (#451) - Exposing a new `CustomConfiguration` type to allow specifying named configurations with a variant (debug or release) to inner the default settings. - Adding fixture `fixtures/ios_app_with_multi_configs` with acceptance tests - Adding additional linting to ensure scheme specified configurations exist - Updating scheme API to use configuration name strings instead of `BuildConfiguration` enum - Renamed the `BuildConfiguration` enum to `PresetBuildConfiguration` enum to ensure schemes are backwards compatible - Updating how default build configurations for scheme targets are selected - 'Debug' configuration is used for Run, Test and Analyze actions - 'Release' configuration is used for the Profile & Archive actions. - If those aren't found, the first alphabetically ordered configuration with the corresponding variant is used - Adding manifest linter to help flag manifest issues such as duplicate custom configuration names - Updating documentation to include information on multiple configurations and some of the gotchas to watch out for Test Plan: - Run `tuist generate` within `fixtures/ios_app_with_multi_configs` - Verify the generated project contains the build configurations "Debug", "Beta" and "Release" - Verify the generated project `Framework2` has a target xcconfig override for the Beta configuration that points to `Target.Beta.xcconfig` - Verify the generated project has a scheme "App-Beta" which uses the "Beta" configuration when performing the run action - Verify that referencing a configuration within the scheme that isn't defined in the project flags a listing error
2019-08-01 03:44:11 +08:00
- Allow specifying multiple configurations within project manifests https://github.com/tuist/tuist/pull/451 by @kwridan
Add linting for mismatching build configurations in a workspace (#474) Resolves https://github.com/tuist/tuist/issues/467 - All projects' build configurations are now validated against the top level projects - In the event any are missing or are mismatching (e.g. have a mismatching variant) the linter will now flag them Example: ``` $ tuist generate The following issues have been found: - The project 'Framework2' has missing or mismatching configurations. It has [Debug (debug), Release (release)], other projects have [Beta (release), Debug (debug), Release (release)]. ``` Test Plan: - Run `tuist generate` within `fixtures/ios_app_with_multi_configs` - Comment out any of the build configurations defined in `App`, `Framework1` or `Framework2` - Re-run `tuist generate` - Verify a lint warning is displayed
2019-08-04 17:01:57 +08:00
- Add linting for mismatching build configurations in a workspace https://github.com/tuist/tuist/pull/474 by @kwridan
Add support for CocoaPods dependencies (#465) * Add TargetDependency.cocoapods * Add Dependency.cocoapods * Add CocoaPodsNode model and support for caching it to the GraphLoaderCache * Add tests to CocoaPodsNode * Support loading a CocoaPods target dependency * Test TargetNode changes * Lint that the directories referenced by CocoaPods dependencies contain a Podfile * Run 'pod install' after the workspace generation * Add documentation * Update Pod specs repository automtically * Update CHANGELOG * Add acceptance tests * Remove empty code block and fix acceptance test
2019-08-04 19:22:49 +08:00
- Support for CocoaPods dependencies https://github.com/tuist/tuist/pull/465 by @pepibumur
Use Custom File Name for `.xcodeproj` at Model Level (#462) * using custom file name * swiftformat * use file name from model * changelog * fix test * enum suffix, prefix, test, and new fixture * acceptance test * swiftformat * new api * docs and clean ups * swiftformat and clean up * expose less at generator level, tuist config tests for code coverage * more code coverage? * clean ups * clean ups * pr suggestions * swift format * fixes tests from changes in master
2019-08-07 19:48:29 +08:00
- Support custom .xcodeproj name at the model level https://github.com/tuist/tuist/pull/462 by @adamkhazi
Add compatible Xcodes option to the TuistConfig (#476) * Add model changes to ProjectDescription * Add models to the TuistGenerator target * Create Xcode & XcodeController to interact with local Xcode installations * Implement TuistConfigLinter * Add acceptance test * Support initializing CompatibleXcodeVersions with a string literal * Add documentation * Update CHANGELOG * Address comments * Fix imports * Rename TuistConfigLinter to EnvironmentLinter * Some style fixes
2019-08-08 01:44:44 +08:00
- `TuistConfig.compatibleXcodeVersions` support https://github.com/tuist/tuist/pull/476 by @pepibumur.
Expose the `.bundle` product type (#479) Part of https://github.com/tuist/tuist/issues/290 - Tuist support iOS resouce bundles - This can now be leveraged via specifying `.bundle` product types - Fixture has been updated to show case how this can be used Test Plan: - Run `tuist generate` within `fixtures/ios_app_with_framework_and_resources` - Verify the project `StaticFramework` has a bundle target called `StaticFrameworkResources` which includes resources - Verify the `StaticFrameworkResources` bundle is copied as a resouce in the App - Verify running the app prints out descriptions for images within `StaticFrameworkResources`
2019-08-14 14:03:40 +08:00
- Expose the `.bundle` product type https://github.com/tuist/tuist/pull/479 by @kwridan
Add "tuist graph" command (#427) * Implement class to generate the dotgraph as a string * Add GraphCommand * Register command * Add command to export the graph * Fix graph syntax error * Don't generate manifest targets when printing the graph * Add tests * Update CHANGELOG * Add documentation * Add the graph.dot file to the gitignore * Address comments * Don't lint when generating the graph
2019-07-02 22:13:27 +08:00
Ensuring the correct platform SDK dependencies path is set (#419) Resolves https://github.com/tuist/tuist/issues/417 - Updating SDK dependency paths to be based on the developer directory and the platform SDK root path Test Plan: - generate the fixture `fixtures/ios_app_with_sdk` via `tuist generate` - Verify the linked system frameworks and libraries have the correct path set based on the platform
2019-06-26 15:44:44 +08:00
### Fixed
Transitive SDK Dependencies (#441) * adds transitive sdk deps * transitive dependencies are unique * use sets, duplication test, immediate child test * remove comments * integration test * integration test, remove throws * minor fixes to naming etc * swiftformat * unneeded throws * changelog entry and adds private to struct
2019-07-13 02:27:10 +08:00
- Ensuring transitive SDK dependencies are added correctly https://github.com/tuist/tuist/pull/441 by @adamkhazi
Ensuring the correct platform SDK dependencies path is set (#419) Resolves https://github.com/tuist/tuist/issues/417 - Updating SDK dependency paths to be based on the developer directory and the platform SDK root path Test Plan: - generate the fixture `fixtures/ios_app_with_sdk` via `tuist generate` - Verify the linked system frameworks and libraries have the correct path set based on the platform
2019-06-26 15:44:44 +08:00
- Ensuring the correct platform SDK dependencies path is set https://github.com/tuist/tuist/pull/419 by @kwridan
Update manifest target name such that its product has a valid name (#426) Part of https://github.com/tuist/tuist/issues/425 - Renaming the generated manifest target to include an `_` separator instead `-` which produces an invalid product name. - This was causing Xcode to automatically re-name it when opening the project Test Plan: - Generate `fixtures/ios_app_with_tests` via `tuist generate` - Run `git add . -f` to stage the generated project - Open the project in Xcode - Verify the manifest target `App_manifest` doesn't get renamed by Xcode within the Scheme and project - Verify the manifest target can still build successfully
2019-07-04 06:09:57 +08:00
- Update manifest target name such that its product has a valid name https://github.com/tuist/tuist/pull/426 by @kwridan
Do Not Create `Derived/InfoPlists` Folder When No InfoPlist Dictionary Specified (#456) * fix and test case * make info plist inclusion explicit * swiftformat and changelog
2019-07-24 15:58:37 +08:00
- Do not create `Derived/InfoPlists` folder when no InfoPlist dictionary is specified https://github.com/tuist/tuist/pull/456 by @adamkhazi
Set the correct lastKnownFileType for localized files (#478) Resolves https://github.com/tuist/tuist/issues/424 - Localized file extensions are used to determine the `lastKnownFileType` Test Plan: - Run `tuist generate` within `fixtures/ios_app_with_framework_and_resources` - Verify the `lastKnownFileType` of the strings files are set (inspect `App/MainApp.xcodeproj/project.pbxproj`)
2019-08-14 14:03:15 +08:00
- Set the correct lastKnownFileType for localized files https://github.com/tuist/tuist/pull/478 by @kwridan
Ensuring the correct platform SDK dependencies path is set (#419) Resolves https://github.com/tuist/tuist/issues/417 - Updating SDK dependency paths to be based on the developer directory and the platform SDK root path Test Plan: - generate the fixture `fixtures/ios_app_with_sdk` via `tuist generate` - Verify the linked system frameworks and libraries have the correct path set based on the platform
2019-06-26 15:44:44 +08:00
Upgrade XcodeProj to 7.0.0 (#421) * Upgrade XcodeProj to 7.0.0 * Update CHANGELOG
2019-06-26 17:41:28 +08:00
### Changed
Create a symlink, swift-project pointing to /usr/local/bin/tuist (#447) * Create a symlink swift-project that targets tuist * Update CHANGELOG
2019-07-18 21:48:45 +08:00
Upgrade XcodeProj to 7.0.0 (#421) * Upgrade XcodeProj to 7.0.0 * Update CHANGELOG
2019-06-26 17:41:28 +08:00
- Update XcodeProj to 7.0.0 https://github.com/tuist/tuist/pull/421 by @pepibumur.
release/v0.16.0
2019-06-21 15:50:31 +08:00
## 0.16.0
Add install command to tuistenv (#83) * wip * Add install command * Update CHANGELOG
2018-08-01 05:13:38 +08:00
Support none defaultSettings (#395) * Support none defaultSettings * Update changelog * Document .none default setting * Use simple quotes
2019-06-08 10:52:45 +08:00
### Added
Create a symlink, swift-project pointing to /usr/local/bin/tuist (#447) * Create a symlink swift-project that targets tuist * Update CHANGELOG
2019-07-18 21:48:45 +08:00
Support none defaultSettings (#395) * Support none defaultSettings * Update changelog * Document .none default setting * Use simple quotes
2019-06-08 10:52:45 +08:00
- `DefaultSettings.none` to disable the generation of default build settings https://github.com/tuist/tuist/pull/395 by @pepibumur.
[env-version] Update CHANGELOG.md
2019-06-08 04:44:36 +08:00
- Version information for tuistenv https://github.com/tuist/tuist/pull/399 by @ollieatkinson
[target_action] update CHANGELOG.md
2019-06-10 04:03:30 +08:00
- Add input & output paths for target action https://github.com/tuist/tuist/pull/353 by Rag0n
Adding support for linking system libraries and frameworks (#406) Resolves https://github.com/tuist/tuist/issues/174 Continuation of https://github.com/tuist/tuist/pull/272 by @steprescott ### Short description In some cases specifying the status of the frameworks or libraries to link against is needed (e.g. weakly linking frameworks). ### Solution - A new `.sdk` dependency type is being introduced usage: ```swift Target(name: "App", platform: .iOS, product: .app, bundleId: "io.tuist.App", infoPlist: "Info.plist", sources: "Sources/**", dependencies: [ .sdk(name: "CloudKit.framework", status: .required), .sdk(name: "StoreKit.framework", status: .optional), .sdk(name: "libc++.tbd"), ]) ``` ### Test Plan - Verify unit tests pass via `swift test` - Verify acceptance tests pass via `bundle rake exec features` - Manually generate `fixtures/ios_app_with_sdk` via `tuist generate` - Verify the appropriate libraries are included in the generated project ### Notes Credit goes to @steprescott and [`XcodeGen`](https://github.com/yonaskolb/XcodeGen) - this PR is based on their work!
2019-06-19 20:25:46 +08:00
- Adding support for linking system libraries and frameworks https://github.com/tuist/tuist/pull/353 by @steprescott
Pass Info.plist as dictionary (#380) * Add a new case to Info.plist, dictionary * Add .dictionary to the model in TuistGenerator * Add DerivedFile model * Add documentation * Create a custom type for the InfoPlist dictionary * Fix tests * Update CHANGELOG * Add logic to write Info.plist content * Test DerivedFileGenerator * Generate the file elements and the right configuration path * Add tests * Include Minitest::Assertions namespace * Fix acceptance tests * Fix tests * Add test that asserts that a codable & equatable object can be encoded and decoded, resulting in the same object * Remove not used decoding logic from the InfoPlist.Value enum. Moreover, update its tests to use the new XCTAssertCodable helper. * Simplify the generation logic by setting the target.infoplist attribute pointing to the Info.plist generated in the Derived folder
2019-07-16 00:05:52 +08:00
- Support passing the `Info.plist` as a dictionary https://github.com/tuist/tuist/pull/380 by @pepibumur.
Support none defaultSettings (#395) * Support none defaultSettings * Update changelog * Document .none default setting * Use simple quotes
2019-06-08 10:52:45 +08:00
Ensuring the correct default settings provider dependency is used (#389) - The `defaultSettingsProvider` passed to the `WorkspaceGenerator` wasn't being passed along to the `TargetGenerator` - This led to having 2 different implementations running side by side - The target generator is now created and injected to the project generator Test Plan: - Verify unit tests pass via `swift tests` - Verify acceptance tests pass via `bundle exec rake features`
2019-06-04 22:41:19 +08:00
### Fixed
- Ensuring the correct default settings provider dependency is used https://github.com/tuist/tuist/pull/389 by @kwridan
Don't generate settings attribute when compiler flags are not specified (#415) Resolves https://github.com/tuist/tuist/issues/414 `BuildPhaseGenerator` will not generate empty `settings` attribute for source `PBXBuildFile` elements when compiler flags are not specified. Test Plan: - Close Xcode - Generate `fixtures/ios_app_with_frameworks` fixture - Open generated .xcodeproj in a non-Xcode editor (i.e vim), ensure empty `settings ={}` attributes have not been generated
2019-06-19 03:50:19 +08:00
- Fixing build settings repeated same value https://github.com/tuist/tuist/pull/391 by @platonsi
Handle the scenario where several sources glob patterns match the same paths (#388) * Handle the scenario where several sources glob patterns match the same paths * Update changelog * Reduce verbosity of the tests using sets
2019-06-06 00:01:03 +08:00
- Duplicated files in the sources build phase when different glob patterns match the same files https://github.com/tuist/tuist/pull/388 by @pepibumur.
Add .d as a valid source extension (#396) * Add .d as a valid source extension * Update CHANGELOG
2019-06-07 22:21:02 +08:00
- Support `.d` source files https://github.com/tuist/tuist/pull/396 by @pepibumur.
Update CHANGELOG.md
2019-06-08 04:45:29 +08:00
- Codesign frameworks when copying during the embed phase https://github.com/tuist/tuist/pull/398 by @ollieatkinson
[tuist-local] update CHANGELOG.md
2019-06-10 04:37:41 +08:00
- 'tuist local' failed when trying to install from source https://github.com/tuist/tuist/pull/402 by @ollieatkinson
Omitting unzip logs during installation (#404) Resolves https://github.com/tuist/tuist/issues/387 - We now pass the `-q` (quiet) option to `unzip` to suppress the verbose output Test Plan: - build this version locally - run `swift run tuistenv update` - Verify the logs don't display the unzipped files
2019-06-11 03:53:10 +08:00
- Omitting unzip logs during installation https://github.com/tuist/tuist/pull/404 by @kwridan
Don't generate settings attribute when compiler flags are not specified (#415) Resolves https://github.com/tuist/tuist/issues/414 `BuildPhaseGenerator` will not generate empty `settings` attribute for source `PBXBuildFile` elements when compiler flags are not specified. Test Plan: - Close Xcode - Generate `fixtures/ios_app_with_frameworks` fixture - Open generated .xcodeproj in a non-Xcode editor (i.e vim), ensure empty `settings ={}` attributes have not been generated
2019-06-19 03:50:19 +08:00
- Fix "The file couldn’t be saved." error https://github.com/tuist/tuist/pull/408 by @marciniwanicki
Ensure generated projects are stable (#410) Resolves https://github.com/tuist/tuist/issues/409 ### Short description Calling `tuist generate` on the same project multiple times can yield a different `.xcodeproj` file each time. ### Solution Sort elements ahead of adding them to their corresponding xcodeproj container. ### Implementation - Update generator integration tests to shuffle sources / headers - Sort files added within `BuildPhaseGenerator` - Update generator integration tests to shuffle additional files - Update `ProjectFilesSortener` to be stable - Update `LinkGenerator` to sort dependencies ### Test Plan - Ensure unit tests pass via `swift test` - Ensure acceptance tests pass via `bundle exec rake features` Generate the fixture `fixtures/ios_app_with_tests/` and verify the generated project is identical each time ``` $ cd fixtures/ios_app_with_tests/ $ touch Sources/Source{A..Z}.swift $ for i in {1..5}; do tuist generate > /dev/null && md5 App.xcodeproj/project.pbxproj; done ```
2019-06-17 03:37:15 +08:00
- Ensure generated projects are stable https://github.com/tuist/tuist/pull/410 by @kwridan
Don't generate settings attribute when compiler flags are not specified (#415) Resolves https://github.com/tuist/tuist/issues/414 `BuildPhaseGenerator` will not generate empty `settings` attribute for source `PBXBuildFile` elements when compiler flags are not specified. Test Plan: - Close Xcode - Generate `fixtures/ios_app_with_frameworks` fixture - Open generated .xcodeproj in a non-Xcode editor (i.e vim), ensure empty `settings ={}` attributes have not been generated
2019-06-19 03:50:19 +08:00
- Stop generating empty `PBXBuildFile` settings https://github.com/tuist/tuist/pull/415 by @marciniwanicki
Ensuring the correct default settings provider dependency is used (#389) - The `defaultSettingsProvider` passed to the `WorkspaceGenerator` wasn't being passed along to the `TargetGenerator` - This led to having 2 different implementations running side by side - The target generator is now created and injected to the project generator Test Plan: - Verify unit tests pass via `swift tests` - Verify acceptance tests pass via `bundle exec rake features`
2019-06-04 22:41:19 +08:00
Version 0.15.0
2019-06-02 23:35:46 +08:00
## 0.15.0
Add InfoPlist type (#373) * Define Info.plist in the ProjectDescription target * Update infoPlist attribute type * Update models to use the new type, InfoPlist * Update changelog
2019-05-27 14:29:57 +08:00
### Changed
Create a symlink, swift-project pointing to /usr/local/bin/tuist (#447) * Create a symlink swift-project that targets tuist * Update CHANGELOG
2019-07-18 21:48:45 +08:00
Add InfoPlist type (#373) * Define Info.plist in the ProjectDescription target * Update infoPlist attribute type * Update models to use the new type, InfoPlist * Update changelog
2019-05-27 14:29:57 +08:00
- Introduce the `InfoPlist` file https://github.com/tuist/tuist/pull/373 by @pepibumur.
Essential and recommended default settings (#378) Resolves https://github.com/tuist/tuist/issues/350 - Added a new protocol `DefaultSettingsProviding` that allows to control default settings at project and target level with a default implementation. `.recommended` set of settings is exactly the same as what Tuist currently generates so this it's not a breaking change. - Moved some of the settings helpers to a separated class `SettingsHelper`. - Extended `Settings` manifest so the users can control the default set of settings.
2019-05-31 16:30:38 +08:00
- Add `defaultSettings` option to `Settings` definition to control default settings generation https://github.com/tuist/tuist/pull/378 by @marciniwanicki
Add InfoPlist type (#373) * Define Info.plist in the ProjectDescription target * Update infoPlist attribute type * Update models to use the new type, InfoPlist * Update changelog
2019-05-27 14:29:57 +08:00
[RELEASE] 0.13.0
2019-03-30 20:22:47 +08:00
### Added
Adding support for project additional files (#314) Part of https://github.com/tuist/tuist/issues/202 ### Short description Often projects may include additional files or folder references that don't need to be part of any build phase (e.g. design references, documentation etc...) ### Solution `Workspace.swift` manifest now supports `additionalFiles`, the same concept can be added to the `Project.swift` manifest with the same rules. - `.glob(pattern: "Documentation/**")`: glob pattern to one or more files - `.folderReference(path: "Designs")`: single path to a directory that is added as a folder reference Example: ```swift let project = Project(name: "App", targets: [ // ... ], additionalFiles: [ "Dangerfile.swift" "Documentation/**", .folderReference(path: "Designs") ]) ``` ### Implementation - [x] Update `Project` manifest to include `additionalFiles` - [x] Update models to translate globs to paths - [x] Update `ProjectFileElements` to include `additionalFiles` - [x] Include fixture - [x] Update documentation - [x] Update changelog ### Test Plan - Run `tuist generate` within `fixtures/ios_app_with_custom_workspace/App` - Open the generated workspace - Verify `Dangerfile.swift` is included in the project but isn't part of the resource phase - Verify `Documentation` files are included (with the appropriate group structure that reflects the file system) and that the files aren't copied to resources - Verify `Server` folder reference is included
2019-04-03 16:43:23 +08:00
Adding generate command timer (#335) Resolves https://github.com/tuist/tuist/issues/329 ### Short description 📝 To keep an eye on how long the generation process takes as users add more dependencies to their projects and as Tuist developers add more features to Tuist itself, it would be useful to print out the total generation time. ### Solution Print out the total time taken to generate a project within the generate command. ### Implementation - Introduce `Clock` and `ClockTimers` to allow obtaining current date and time differences - Time the generate process within the generate command ### Test Plan - Verify unit tests and acceptance tests pass - Run `tuist generate` within any of the fixtures in `fixtures` - Verify the generation time is displayed in the console output
2019-05-05 16:59:27 +08:00
- Adding generate command timer https://github.com/tuist/tuist/pull/335 by @kwridan
Update TestAction lauch arguments environments settings
2019-05-07 01:38:39 +08:00
- Support Scheme manifest with pre/post action https://github.com/tuist/tuist/pull/336 by @dangthaison91
Support Scheme `shared` flag (#341) * Support Scheme `shared` flag * Fix Project generator tests * Correct scheme write path * Update tests and change log
2019-05-17 02:55:54 +08:00
- Support local Scheme (not shared) flag https://github.com/tuist/tuist/pull/341 by @dangthaison91
Add support for compiler flags (#386) * Add support for compiler flags * Add missing content * Update changelog
2019-06-02 23:33:16 +08:00
- Support for compiler flags https://github.com/tuist/tuist/pull/386 by @pepibumur.
Adding generate command timer (#335) Resolves https://github.com/tuist/tuist/issues/329 ### Short description 📝 To keep an eye on how long the generation process takes as users add more dependencies to their projects and as Tuist developers add more features to Tuist itself, it would be useful to print out the total generation time. ### Solution Print out the total time taken to generate a project within the generate command. ### Implementation - Introduce `Clock` and `ClockTimers` to allow obtaining current date and time differences - Time the generate process within the generate command ### Test Plan - Verify unit tests and acceptance tests pass - Run `tuist generate` within any of the fixtures in `fixtures` - Verify the generation time is displayed in the console output
2019-05-05 16:59:27 +08:00
Set Code Sign On Copy to true for Embed Frameworks (#333) * Headers build phase should be put on top of Compile build phase * Add test * Add changelog * Set Code Sign On Copy to true for Embbed Frameworks * Add changelog * Update CHANGELOG
2019-05-03 00:16:16 +08:00
### Fixed
Fix changelog structure
2019-05-31 16:10:52 +08:00
- Fixing unstable diff (products and embedded frameworks) https://github.com/tuist/tuist/pull/357 by @marciniwanicki
Set Code Sign On Copy to true for Embed Frameworks (#333) * Headers build phase should be put on top of Compile build phase * Add test * Add changelog * Set Code Sign On Copy to true for Embbed Frameworks * Add changelog * Update CHANGELOG
2019-05-03 00:16:16 +08:00
- Set Code Sign On Copy to true for Embed Frameworks https://github.com/tuist/tuist/pull/333 by @dangthaison91
Fixing files getting mistaken for folders (#338) Resolves https://github.com/tuist/tuist/issues/330 and https://github.com/tuist/tuist/issues/322 ### Short description: - This issue can occur when files like `README` without extensions exist within the project - Additionally another issue can be encountered in the event folders contain a `.` in their name - To solve this we now only create groups if the file element component being added is a leaf (i.e. `/path/to/a` when `path` and `to` are added, they will be added as groups, and `a` will be added as a file element) ## Test Plan: - Verify unit tests pass `swift test` - Verify acceptance tests pass `bundle rake features` - Manually generate `fixtures/ios_app_with_framework_and_resources` via `tuist generate` - Verify `resource_without_extension` and `resource.txt` are included as resources within the project - Manually generate `fixtures/ios_app_with_custom_workspace` via `tuist generate` - Verify the `CHANGELOG` file appears as a file and not a group
2019-05-04 18:32:49 +08:00
- Fixing files getting mistaken for folders https://github.com/tuist/tuist/pull/338 by @kwridan
Create a symlink, swift-project pointing to /usr/local/bin/tuist (#447) * Create a symlink swift-project that targets tuist * Update CHANGELOG
2019-07-18 21:48:45 +08:00
- Updating init template to avoid warnings https://github.com/tuist/tuist/pull/339 by @kwridan
- Fixing generation failures due to asset catalog & `**/*.png` glob patterns handling https://github.com/tuist/tuist/pull/346 by @kwridan
- Supporting bundle target dependencies that reside in different projects (in `TuistGenerator`) https://github.com/tuist/tuist/pull/348 by @kwridan
Fixing header paths including folders and non-header files (#356) Resolves https://github.com/tuist/tuist/issues/352 - Specifying a permissive glob pattern (e.g. `Headers/**`) for headers would incorrectly include all files and folders as headers - Limiting the paths to header files resolves this issue - Adding Objective-C classes to test out headers within the fixtures Test Plan: - Verify unit tests pass via `swift build` - Verify acceptance tests pass via `bundle exec rake features` - Manually generate `fixtures/ios_app_with_frameworks` via `tuist generate` - Verify `Framework2` has the appropriate public, private & project headers set
2019-05-18 04:24:29 +08:00
- Fixing header paths including folders and non-header files https://github.com/tuist/tuist/pull/356 by @kwridan
Fix duplicate localized resource files (#363) Resolves https://github.com/tuist/tuist/issues/361 ### Short description Localized resources can up getting duplicated within the resources build phase and the project files elements. The reason this was occurring: - Give a path to a resource e.g. `/resources/en.lproj/foo.png` - `/resources/en.lproj/` is used detected - All files within `/resources/en.lproj/` are enumerated and added - When another path to a resource is encountered e.g. `/resources/en.lproj/bar.png` - The same process is repeated, resulting in duplicate file elements! ### Solution - Update project files element logic to better accommodate multiple localized files - Add a cache to keep track of which build files were added the resources build phase to prevent adding duplicates. - Improved file element missing file warnings for directories e.g. `resources: ["Resources/en.lproj"]` would yield the following warnings: ``` Warning: 'Resources/en.lproj' is a directory, try using: 'Resources/en.lproj/**' to list its files ``` ### Test Plan - Verify unit tests pass via `swift tests` - Verify acceptance tests pass via `bundle rake exec features` - Manually generate `fixtures/ios_app_with_framework_and_resources` via `tuist generate` - Verify the generated project includes the localized string files without any duplicates
2019-05-21 04:42:37 +08:00
- Fix duplicate localized resource files https://github.com/tuist/tuist/pull/363 by @kwridan
Update static dependency lint rule (#360) Resolves https://github.com/tuist/tuist/issues/337 - The graph linter didn't account for which targets could link static products - This led to raising an incorrect lint warning - A `canLinkStaticProducts` method has been added to share rules between the linter and graph during link generation - `GraphLinter` has been updated to no longer keep state internally Test Plan: - Run unit tests via `swift lint` - Run acceptance tests via `bundle exec rake features` - Manually generate `fixtures/ios_app_with_static_frameworks` via `tuist generate` - Verify no lint warnings are displayed
2019-05-22 05:14:21 +08:00
- Update static dependency lint rule https://github.com/tuist/tuist/pull/360 by @kwridan
Create a symlink, swift-project pointing to /usr/local/bin/tuist (#447) * Create a symlink swift-project that targets tuist * Update CHANGELOG
2019-07-18 21:48:45 +08:00
- Ensure resource bundles in other projects get built https://github.com/tuist/tuist/pull/374 by @kwridan
Set Code Sign On Copy to true for Embed Frameworks (#333) * Headers build phase should be put on top of Compile build phase * Add test * Add changelog * Set Code Sign On Copy to true for Embbed Frameworks * Add changelog * Update CHANGELOG
2019-05-03 00:16:16 +08:00
## 0.14.0
### Changed
### Added
Adding support for project additional files (#314) Part of https://github.com/tuist/tuist/issues/202 ### Short description Often projects may include additional files or folder references that don't need to be part of any build phase (e.g. design references, documentation etc...) ### Solution `Workspace.swift` manifest now supports `additionalFiles`, the same concept can be added to the `Project.swift` manifest with the same rules. - `.glob(pattern: "Documentation/**")`: glob pattern to one or more files - `.folderReference(path: "Designs")`: single path to a directory that is added as a folder reference Example: ```swift let project = Project(name: "App", targets: [ // ... ], additionalFiles: [ "Dangerfile.swift" "Documentation/**", .folderReference(path: "Designs") ]) ``` ### Implementation - [x] Update `Project` manifest to include `additionalFiles` - [x] Update models to translate globs to paths - [x] Update `ProjectFileElements` to include `additionalFiles` - [x] Include fixture - [x] Update documentation - [x] Update changelog ### Test Plan - Run `tuist generate` within `fixtures/ios_app_with_custom_workspace/App` - Open the generated workspace - Verify `Dangerfile.swift` is included in the project but isn't part of the resource phase - Verify `Documentation` files are included (with the appropriate group structure that reflects the file system) and that the files aren't copied to resources - Verify `Server` folder reference is included
2019-04-03 16:43:23 +08:00
- Adding support for project additional files https://github.com/tuist/tuist/pull/314 by @kwridan
Adding support for resource folder references (#318) Resolves https://github.com/tuist/tuist/issues/202 ### Short description Resources to include in an application can be in the form of files as well as folder references. ### Solution Add support for folder references within target resources. For consistency, we can use `FileElement` which has already been used in `Project` and `Workspace` to define additional files. e.g. ```swift import ProjectDescription let project = Project( name: "MainApp", targets: [ Target( name: "App", platform: .iOS, product: .app, bundleId: "io.tuist.App", infoPlist: "Config/App-Info.plist", sources: "Sources/**", resources: [ "Resources/*.png", .folderReference(path: "Examples") ]) ] ) ``` ### Test Plan - Verify unit tests pass via `swift test` - Verify acceptance tests pass via `bundle exec rake features` - Run `tuist generate` within `fixtures/ios_app_with_framework_and_resources` - Inspect the generated workspace - Verify `MainApp` has a folder reference to `Examples` which is also included in the **Copy Bundle Resources** phase
2019-04-08 17:29:26 +08:00
- Adding support for resource folder references https://github.com/tuist/tuist/pull/318 by @kwridan
Swift 5 support (#317) * Support Swift 5 * Fix test * Don't check if the versions match when both local and remote versions are greater or equal than 5 * Updating fixtures for Swift 5 support - Included a build script to allow re-creating the pre-built `Framework2` framework - Updated build script for pre-built static library to require less manual steps * Updates for Swift 5 - `swift package tools-version --set-current` * Relaxed error output checks in acceptance tests * Adding trace for acceptance test (to aid troubleshooting) * skipping build during error message acceptance test - Adding a step to build tuist separately ahead of calling run - When running tuist via `swift run` we now skip the build * Disable Swiftformat
2019-04-10 14:18:52 +08:00
- **Breaking** Swift 5 support https://github.com/tuist/tuist/pull/317 by @pepibumur.
Adding support for project additional files (#314) Part of https://github.com/tuist/tuist/issues/202 ### Short description Often projects may include additional files or folder references that don't need to be part of any build phase (e.g. design references, documentation etc...) ### Solution `Workspace.swift` manifest now supports `additionalFiles`, the same concept can be added to the `Project.swift` manifest with the same rules. - `.glob(pattern: "Documentation/**")`: glob pattern to one or more files - `.folderReference(path: "Designs")`: single path to a directory that is added as a folder reference Example: ```swift let project = Project(name: "App", targets: [ // ... ], additionalFiles: [ "Dangerfile.swift" "Documentation/**", .folderReference(path: "Designs") ]) ``` ### Implementation - [x] Update `Project` manifest to include `additionalFiles` - [x] Update models to translate globs to paths - [x] Update `ProjectFileElements` to include `additionalFiles` - [x] Include fixture - [x] Update documentation - [x] Update changelog ### Test Plan - Run `tuist generate` within `fixtures/ios_app_with_custom_workspace/App` - Open the generated workspace - Verify `Dangerfile.swift` is included in the project but isn't part of the resource phase - Verify `Documentation` files are included (with the appropriate group structure that reflects the file system) and that the files aren't copied to resources - Verify `Server` folder reference is included
2019-04-03 16:43:23 +08:00
[RELEASE] 0.13.0
2019-03-30 20:22:47 +08:00
### Fixed
Ensuring target product names are consistent with Xcode (#323) Resolves https://github.com/tuist/tuist/issues/254 - When creating new Xcode projects manually from the UI, the product names do not include the extension - Renaming existing `productName` references to `productNameWithExtension` Test Plan: - Ensure unit tests pass via `swift test` - Ensure acceptance tests pass via `bundle exec rake features`
2019-04-13 02:39:31 +08:00
- Ensuring target product names are consistent with Xcode https://github.com/tuist/tuist/pull/323 by @kwridan
Ensure generate works on additional disk volumes (#327) Resolves https://github.com/tuist/tuist/issues/324 - Using `replaceItemAt` has a caveat where it requires the item and its replacement to be on the same volume (see https://developer.apple.com/documentation/foundation/filemanager/2293212-replaceitemat) - To mitigate this, the documentation suggests creating a temporary file within that volume - The item can be moved there first - Then a `replaceItemAt` can be performed Test Plan: - Manually create a RAM disk e.g. `diskutil erasevolume HFS+ “RAMDisk” `hdiutil attach -nomount ram://524288`` (this creates a 250MB RAM disk) - Create a new folder within that disk - run `tuist --init` - run `tuist generate` - Verify the generation succeeds
2019-04-18 14:09:57 +08:00
- Ensuring generate works on additional disk volumes https://github.com/tuist/tuist/pull/327 by @kwridan
Headers build phase should be put on top of Compile build phase (#332) * Headers build phase should be put on top of Compile build phase * Add test * Add changelog
2019-04-28 17:17:09 +08:00
- Headers build phase should be put on top of Compile build phase https://github.com/tuist/tuist/pull/332 by @dangthaison91
Ensuring target product names are consistent with Xcode (#323) Resolves https://github.com/tuist/tuist/issues/254 - When creating new Xcode projects manually from the UI, the product names do not include the extension - Renaming existing `productName` references to `productNameWithExtension` Test Plan: - Ensure unit tests pass via `swift test` - Ensure acceptance tests pass via `bundle exec rake features`
2019-04-13 02:39:31 +08:00
[RELEASE] 0.13.0
2019-03-30 20:22:47 +08:00
## 0.13.0
Fix duplicated embedded frameworks (#280) * Fix duplicated embedded frameworks * Update changelog
2019-03-13 01:48:37 +08:00
[RELEASE] 0.12.0
2019-03-11 21:33:00 +08:00
### Added
Fix duplicated embedded frameworks (#280) * Fix duplicated embedded frameworks * Update changelog
2019-03-13 01:48:37 +08:00
Add Homebrew tap up (#281) * Add Homebrew tap up * update changelog * Address comments * Add documentation
2019-03-13 16:56:52 +08:00
- Add Homebrew tap up https://github.com/tuist/tuist/pull/281 by @pepibumur
Create a Setup.swift file when running the init command (#283) * Create a Setup.swift file * Update changelog * Add more examples
2019-03-13 17:39:46 +08:00
- Create a Setup.swift file when running the init command https://github.com/tuist/tuist/pull/283 by @pepibumur
Update tuistenv when running tuist update (#288) * Update tuistenv when running tuist update * update changelog
2019-03-19 16:40:58 +08:00
- Update `tuistenv` when running `tuist update` https://github.com/tuist/tuist/pull/288 by @pepibumur.
update readme, changelog and fixture test
2019-03-22 22:40:08 +08:00
- Allow linking of static products into dynamic frameworks https://github.com/tuist/tuist/pull/299 by @ollieatkinson
Workspace Improvements (#298) Resolves https://github.com/tuist/tuist/issues/258 ### Short description Workspace manifests allow users to customize which project are included in their workspace however doesn't yet offer the ability to add arbitrary files and folder references (to support included things like Documentation and README files). ### Solution Extend the workspace manifest to allow specifying `additionalFiles` e.g. ```swift import ProjectDescription let workspace = Workspace(name: "Workspace", projects: [ "App", "Frameworks/FrameworkA", "Frameworks/FrameworkB", ], additionalFiles: [ "Documentation/**", .folderReference(path: "Website") ]) ``` As an added bonus of these changes, we can add the ability to specify glob patterns for `projects` to make it easier to include new projects without needing to constantly update the workspace manifest. e.g. ```swift import ProjectDescription let workspace = Workspace(name: "Workspace", projects: [ "App", "Frameworks/**", ], additionalFiles: [ "Documentation/**", .folderReference(path: "Website") ]) ``` ### Implementation - [x] Update workspace manifests - [x] Parse workspace manifests > models - [x] Add workspace structure generator - [x] Integrate workspace structure - [x] Include fixture - [x] Update documentation ### Test Plan - Run `tuist generate` on the following fixtures: - `fixture/ios_app_with_custom_workspace` <img width="254" alt="custom-workspace" src="https://user-images.githubusercontent.com/11914919/54780257-36db2f80-4c11-11e9-8fda-5f59554533c0.png"> - `fixture/ios_app_with_custom_workspace/App` <img width="161" alt="custom-workspace-app" src="https://user-images.githubusercontent.com/11914919/54780299-4a869600-4c11-11e9-9637-cdfaa20bb8c8.png"> - `fixture/ios_app_with_setup` <img width="175" alt="setup" src="https://user-images.githubusercontent.com/11914919/54780315-540ffe00-4c11-11e9-99fd-e9175ee4de27.png"> - `fixture/ios_app_with_frameworks` <img width="184" alt="frameworks" src="https://user-images.githubusercontent.com/11914919/54780335-5d00cf80-4c11-11e9-906c-b53f26c36007.png"> Verify the generated workspace structure ### Notes All this work is based on group effort and iteration from #262 - thanks @ollieatkinson, @pepibumur! 👍
2019-03-23 17:00:17 +08:00
- Workspace improvements https://github.com/tuist/tuist/pull/298 by @ollieatkinson & @kwridan.
Add Homebrew tap up (#281) * Add Homebrew tap up * update changelog * Address comments * Add documentation
2019-03-13 16:56:52 +08:00
[RELEASE] 0.12.0
2019-03-11 21:33:00 +08:00
### Removed
Fix duplicated embedded frameworks (#280) * Fix duplicated embedded frameworks * Update changelog
2019-03-13 01:48:37 +08:00
Update CHANGELOG.md
2019-03-24 21:13:58 +08:00
- **Breaking** Removed "-Project" shared scheme from being generated https://github.com/tuist/tuist/pull/303 by @ollieatkinson
Update CHANGELOG.md
2019-03-24 04:57:25 +08:00
[RELEASE] 0.12.0
2019-03-11 21:33:00 +08:00
### Fixed
Fix duplicated embedded frameworks (#280) * Fix duplicated embedded frameworks * Update changelog
2019-03-13 01:48:37 +08:00
- Fix duplicated embedded frameworks https://github.com/tuist/tuist/pull/280 by @pepibumur
Manifest targets are now static frameworks (to avoid link errors) (#287) * Manifest targets are now static frameworks to prevent link errors - The manifest target can be built to ensure there are no syntax errors in the project manifests - This target doesn't need to be linked, a compilation step is sufficient to serve its purpose - By converting the manifest target to a static framework, the link step is skipped and the errors that were obtained during that step can be avoided all together Test Plan: - Run `tuist generate` on any fixture within `fixtures` - Open the generated workspace (you can use `tuist focus` as a shortcut to those steps) - Build the `<Project>-Manifest` scheme in Xcode - Verify no link errors appear * Updated changelog
2019-03-14 14:49:59 +08:00
- Fix manifest target linker errors https://github.com/tuist/tuist/pull/287 by @kwridan
Fix build settings not being generated properly (#282) * Fix build settings not being generated properly * update changelog * Adding unit test for debug/release target settings * Fix tests * Solve some issues after rebasing
2019-03-14 15:40:23 +08:00
- Build settings not being generated properly https://github.com/tuist/tuist/pull/282 by @pepibumur
Remove App Delegate Warning (#291) * Update UIKit `didFinishLaunchingWithOptions` method to remove warning * Update UIKit `didFinishLaunchingWithOptions` method in fixtures * Exclude fixtures from SwiftFormat * Fix line too long lint error * Update CHANGELOG.md
2019-03-17 19:50:56 +08:00
- Fix `instance method nearly matches optional requirements` warning in generated `AppDelegate.swift` in iOS projects https://github.com/tuist/tuist/pull/291 by @BalestraPatrick
swiftformat .
2019-03-23 05:10:11 +08:00
- Fix Header & Framework search paths override project or xcconfig settings https://github.com/tuist/tuist/pull/301 by @ollieatkinson
Update CHANGELOG.md
2019-03-23 04:37:31 +08:00
- Unit tests bundle for an app target compile & run https://github.com/tuist/tuist/pull/300 by @ollieatkinson
Ensuring Library search paths and Swift import paths are set (#308) - A few additional build settings are needed when linking against pre-built static libraries - `LIBRARY_SEARCH_PATHS` needs to point to the directory containing the `.a` file - `SWIFT_INCLUDE_PATHS` need to point to the directory containing the `.swiftmodule` file Test Plan: - Generate `fixtures/ios_app_with_static_libraries` - Verify the application builds - Verify the `LIBRARY_SEARCH_PATHS` and `SWIFT_INCLUDE_PATHS` settings are set on target `A`
2019-03-28 05:32:08 +08:00
- `LIBRARY_SEARCH_PATHS` and `SWIFT_INCLUDE_PATHS` are now set https://github.com/tuist/tuist/pull/308 by @kwridan
Update CHANGELOG.md
2019-03-30 19:32:27 +08:00
- Fix Generation fails in the event an empty .xcworkspace directory exists https://github.com/tuist/tuist/pull/312 by @ollieatkinson
Fix duplicated embedded frameworks (#280) * Fix duplicated embedded frameworks * Update changelog
2019-03-13 01:48:37 +08:00
[RELEASE] 0.12.0
2019-03-11 21:33:00 +08:00
## 0.12.0
Rename manifest group and target (#227) * Rename the group and the target that includes the manifest file * Name the group Manifest * Update changelog * Fix tests
2019-02-18 18:54:18 +08:00
### Changed
- Rename manifest group to `Manifest` https://github.com/tuist/tuist/pull/227 by @pepibumur.
- Rename manifest target to `Project-Manifest` https://github.com/tuist/tuist/pull/227 by @pepibumur.
Replace swiftlint with swiftformat (#239) * Replace swiftlint with swiftformat * Update CHANGELOG * Add missing require * Fix require * include .swiftformat file * Remove require * Fix Dangerfile * Run Swiftformat after rebase * Upgrade swiftformat * Revert upgrade * Use the right configuration
2019-02-27 10:17:26 +08:00
- Replace swiftlint with swiftformat https://github.com/tuist/tuist/pull/239 by @pepibumur.
Bump xcodeproj version to 6.6.0 (#248) * Bump xcodeproj version to 6.6.0 * update changelog
2019-03-02 10:48:52 +08:00
- Bump xcodeproj version to 6.6.0 https://github.com/tuist/tuist/pull/248 by @pepibumur.
Improve the Xcode project reload when the project is regenrated (#247) * Improve writing logic * update changelog * update changelog * Sort workspace elements * Extract sortening logic into ProjectFilesSortener * Fix tests
2019-03-08 01:22:00 +08:00
- Fix an issue with Xcode not being able to reload the projects when they are open https://github.com/tuist/tuist/pull/247
Support resources as array Support source files as Array Added FileList to maintain source compatibility Fixed CI build failed Fixed tests failed Update document
2019-01-17 23:28:11 +08:00
- Support array for `sources` and `resources` paths https://github.com/tuist/tuist/pull/201 by @dangthaison91
Rename manifest group and target (#227) * Rename the group and the target that includes the manifest file * Name the group Manifest * Update changelog * Fix tests
2019-02-18 18:54:18 +08:00
Add acceptance tests for generate command (#208) * Add integration tests for an app with 2 dynamic frameworks * Add acceptance test for missing manifest case * Bring back all tests for generate command * Fix validation of the missing manifest error message * Use meaningful folder names in fixtures * Fix integration issues * Update CHANGELOG.md * Add ios_ prefix to fixtures folders * Remove tuist.rb.orig * Fix issues found by Robocop
2019-02-16 15:31:55 +08:00
### Added
- Integration tests for `generate` command https://github.com/tuist/tuist/pull/208 by @marciniwanicki & @kwridan
Add FAQ document (#223) * Add frequently asked questions document * Addres comments * Update CHANGELOG
2019-02-16 15:47:25 +08:00
- Frequently asked questions to the documentation https://github.com/tuist/tuist/pull/223/ by @pepibumur.
Generate a scheme with all the project targets (#226) * Generate project scheme * Test the generation of the project scheme * Sort the targets based on the dependencies between them * Add acceptance tests * Address comments * Update changelog and fix Dangerfile
2019-02-18 21:52:07 +08:00
- Generate a scheme with all the project targets https://github.com/tuist/tuist/pull/226 by @pepibumur
Merge contribution documents into the repository (#229) * Merge contribution documents into the repository * Add missing sentence * Update changelog
2019-02-19 19:43:28 +08:00
- Documentation for contributors https://github.com/tuist/tuist/pull/229 by @pepibumur
Update CHANGELOG.md
2019-02-21 23:42:18 +08:00
- Support for Static Frameworks https://github.com/tuist/tuist/pull/194 @ollieatkinson
Add acceptance tests for generate command (#208) * Add integration tests for an app with 2 dynamic frameworks * Add acceptance test for missing manifest case * Bring back all tests for generate command * Fix validation of the missing manifest error message * Use meaningful folder names in fixtures * Fix integration issues * Update CHANGELOG.md * Add ios_ prefix to fixtures folders * Remove tuist.rb.orig * Fix issues found by Robocop
2019-02-16 15:31:55 +08:00
Remove up attribute from the Project model (#228) * Remove up attribute from the Project model * Don't include the up attribute in the manifest generated by the init command * Update changelog
2019-02-18 18:44:28 +08:00
### Removed
- Up attribute from the `Project` model https://github.com/tuist/tuist/pull/228 by @pepibumur.
Update CHANGELOG.md
2019-02-19 21:50:02 +08:00
- Support for YAML and JSON formats as Project specifications https://github.com/tuist/tuist/pull/230 by @ollieatkinson
Remove up attribute from the Project model (#228) * Remove up attribute from the Project model * Don't include the up attribute in the manifest generated by the init command * Update changelog
2019-02-18 18:44:28 +08:00
Update CHANGELOG.md
2019-02-18 21:59:05 +08:00
### Fixed
- Changed default value of SWIFT_VERSION to 4.2 @ollieatkinson
Update CHANGELOG.md
2019-02-21 22:45:19 +08:00
- Added fixture tests for ios app with static libraries @ollieatkinson
Support variables in the bundle id (#252) * Support variables in the bundle id * Update changelog * re-enable tests
2019-03-05 17:10:54 +08:00
- Bundle id linting failing when the bundle id contains variables https://github.com/tuist/tuist/pull/252 by @pepibumur
Fix #253 - Include linked library and embed in any top level executable bundle (#259) * Fix #253 - Include linked library and embed in any top level executable bundle * Fix fixture test, removed explicit link inside of main app and compiled Framework2 as a fat binary * swiftformat . * Update CHANGELOG.md * Add acceptance tests * Delete copying the working directory * Store DerivedData in the working directory
2019-03-08 07:31:43 +08:00
- Include linked library and embed in any top level executable bundle https://github.com/tuist/tuist/pull/259 by @ollieatkinson
Update CHANGELOG.md
2019-02-18 21:59:05 +08:00
Version 0.11.0
2019-02-15 03:17:17 +08:00
## 0.11.0
Schemes generation (#188) * Return GeneratedProject from ProjectGenerator * Add Launch, Profile, Analyze and Archive actions * Add BuildAction generation * Generate TestsAction * Add some tests * Add Cucumber test * Remove byebug line * Update CHANGELOG * Fix test
2018-12-26 17:19:09 +08:00
### Added
Extract up command from the project graph (#207) * Adding integration tests for up - Introduced new up cucumber test - Fixed an issue with `System.run` where valid commands that returned non-zero exit codes were not throwing (e.g. `ls some_file_that_does_not_exist`) - Updated README with additional instructions on how to run unit and acceptance tests Test Plan Verify unit tests pass - `swift test` Verify acceptance tests pass - `rake features` * Extract Up command from the project graph * Update CHANELOG.md * Update documentation * Lint all up actions before running isMet and meet * Fix up.rb formatting * empty commit to trigger CI
2019-02-06 16:08:21 +08:00
- **Breaking** Up can now be specified via `Setup.swift` https://github.com/tuist/tuist/issues/203 by @marciniwanicki & @kwridan
Schemes generation (#188) * Return GeneratedProject from ProjectGenerator * Add Launch, Profile, Analyze and Archive actions * Add BuildAction generation * Generate TestsAction * Add some tests * Add Cucumber test * Remove byebug line * Update CHANGELOG * Fix test
2018-12-26 17:19:09 +08:00
- Schemes generation https://github.com/tuist/tuist/pull/188 by @pepibumur.
Support for scheme environment variables (#189) * Add environment attribute to the Target manifest * Add environment attribute to the Target model * Set environment variables when generating the scheme and add some tests * Update CHANGELOG
2018-12-29 15:32:42 +08:00
- Environment variables per target https://github.com/tuist/tuist/pull/189 by @pepibumur.
Danger warn that reminds contributors to update the docuementation (#214) * Warn if sources have been modified letting developers know that they need to update the documentation * Add CHANGELOG entry
2019-02-07 02:40:05 +08:00
- Danger warn that reminds contributors to update the docuementation https://github.com/tuist/tuist/pull/214 by @pepibumur
Add Rubocop (#216) * Add Rubocop * Add Danger check * Update CHANGELOG
2019-02-07 03:04:17 +08:00
- Rubocop https://github.com/tuist/tuist/pull/216 by @pepibumur.
Fail init command right away if the directory is not empty (#218) * Fail init commanad right away if the directory is not empty * update changelog
2019-02-07 18:42:59 +08:00
- Fail init command if the directory is not empty https://github.com/tuist/tuist/pull/218 by @pepibumur.
Lint that the bundle identifier has the right format (#219) * Lint that the bundle identifier has the right format * Narrow down the set of characters * Bump Danger version The version that we were using threw an error that ended up being reported to the PR. * Update CHANGELOG
2019-02-15 01:57:14 +08:00
- Verify that the bundle identifier has only valid characters https://github.com/tuist/tuist/pull/219 by @pepibumur.
Merge documentation (#222) * Dete the documentation that was generated by jazzy We don't see value in generating documentation for internal interfaces so we decided to remove the Jazzy auto-generated documentation and bring the documentation from the tuist/documentation repository into this one. * Delete references to Open Collective and include a documentation section that lets user know about the documentation folder. * Remove the step to generate the documentation from the release steps * Merge documentation from the documentation repository * Update CHANGELOG * Address comments
2019-02-15 03:09:02 +08:00
- Merge documentation from the documentation repository https://github.com/tuist/tuist/pull/222 by @pepibumur.
Fix most recent changelog entry
2019-02-15 03:19:52 +08:00
- Danger https://github.com/tuist/tuist/pull/186 by @pepibumur.
Schemes generation (#188) * Return GeneratedProject from ProjectGenerator * Add Launch, Profile, Analyze and Archive actions * Add BuildAction generation * Generate TestsAction * Add some tests * Add Cucumber test * Remove byebug line * Update CHANGELOG * Fix test
2018-12-26 17:19:09 +08:00
Use binary name instead of absolute path in the embed frameworks build phase (#185) * Use binary name instead of absolute path * Update CHANGELOG * Remove unused resourceLocator argument
2018-12-22 01:46:42 +08:00
### Fixed
Fix swiftlint issues and make sure it runs on CI (#213) * Add rake task to run swiftlint and correct some issues * Fix all linting issues * Add changelog entry * Run swiftlint with the --strict argument
2019-02-07 01:40:40 +08:00
- Swiftlint style issues https://github.com/tuist/tuist/pull/213 by @pepibumur.
Use binary name instead of absolute path in the embed frameworks build phase (#185) * Use binary name instead of absolute path * Update CHANGELOG * Remove unused resourceLocator argument
2018-12-22 01:46:42 +08:00
- Use environment tuist instead of the absolute path in the embed frameworks build phase https://github.com/tuist/tuist/pull/185 by @pepibumur.
Deprecate yaml and json manifests (#190) * Deprecate JSON and YAML manifests * Add tests * Deprecate JSON and YAML manifests
2018-12-28 05:52:33 +08:00
### Deprecated
- JSON and YAML manifests https://github.com/tuist/tuist/pull/190 by @pepibumur.
Version 0.10.2
2018-12-20 22:41:05 +08:00
## 0.10.2
Use the patch version of SwiftShell (#180) * Use the patch version of SwiftShell * Update CHANGELOG * Fix repository url * Regenerate Package.resolved
2018-12-20 22:38:26 +08:00
### Fixed
- Processes not stopping after receiving an interruption signal https://github.com/tuist/tuist/pull/180 by @pepibumur.
Version 0.10.1
2018-12-20 20:38:42 +08:00
## 0.10.1
Remplace ReactiveTask with SwiftShell (#179) * Remplace ReactiveTask with SwiftShell * Update CHANGELOG * Remove Result import * Fix issue with UpCarthage don't running when the Cartfile.resolved is missing * Update CHANGELOG
2018-12-20 20:36:43 +08:00
### Changed
- Replace ReactiveTask with SwiftShell https://github.com/tuist/tuist/pull/179 by @pepibumur.
### Fixed
- Carthage up command not running when the `Cartfile.resolved` file doesn't exist https://github.com/tuist/tuist/pull/179 by @pepibumur.
Version 0.10.0
2018-12-20 18:58:33 +08:00
## 0.10.0
Don't add the Playgrounds group if there are no playgrounds (#177) * Don't generate the Playgrounds group if the directory contains no Playgrounds * Add tests * Include note in the CHANGELOG
2018-12-19 16:19:27 +08:00
### Fixed
- Don't generate the Playgrounds group if there are no playgrounds https://github.com/tuist/tuist/pull/177 by @pepibumur.
Support cpp source files (#178) * Support cpp source files * Add update to the CHANGELOG file * Include support for .c source files
2018-12-19 17:03:13 +08:00
### Added
Update changelog
2018-12-20 19:01:48 +08:00
- Tuist up command https://github.com/tuist/tuist/pull/158 by @pepibumur.
Support cpp source files (#178) * Support cpp source files * Add update to the CHANGELOG file * Include support for .c source files
2018-12-19 17:03:13 +08:00
- Support `.cpp` and `.c` source files https://github.com/tuist/tuist/pull/178 by @pepibumur.
Version 0.9.0
2018-12-03 16:43:03 +08:00
## 0.9.0
Add acceptance tests (#166) * Gitignore TODO * Configure acceptance tests * Add CHANGELOG entry
2018-12-03 16:37:36 +08:00
### Added
- Acceptance tests https://github.com/tuist/tuist/pull/166 by @pepibumur.
Fix the files and groups sorting order (#164) * Gitignore TODO * Sorten files and groups before adding them to the project * Test it * Update CHANGELOG
2018-12-01 17:44:49 +08:00
### Fixed
- Files and groups sort order https://github.com/tuist/tuist/pull/164 by @pepibumur.
Generate all configurations (#165) * Gitignore TODO * Generate both, Debug and Release configuration * Add CHANGELOG entry
2018-12-03 16:37:56 +08:00
### Added
- Generate both, the `Debug` and `Release` configurations https://github.com/tuist/tuist/pull/165 by @pepibumur.
Release/0.8.0 (#155) * Version 0.8.0 * Add Changelog entry
2018-11-05 22:28:44 +08:00
## 0.8.0
### Added
- Swift 4.2.1 compatibility by @pepibumur.
Remove module loader (#150) * Remove module loader * Remove tests * Remove module loader
2018-10-18 20:59:18 +08:00
### Removed
- Module loader https://github.com/tuist/tuist/pull/150/files by @pepibumur.
Update CHANGELOG
2018-10-06 01:10:11 +08:00
### Added
Generate projects in a DerivedProjects directory (#146) * Add option to generate the projects and workspaces in the ~/.tuist/DerivedProjects directory * Remove unnecessary import * Test ProjectDirectoryHelper * Update CHANGELOG * Remove unnecessary line
2018-10-09 15:04:51 +08:00
- Geration of projects and workspaces in the `~/.tuist/DerivedProjects` directory https://github.com/tuist/tuist/pull/146 by pepibumur.
## 0.7.0
### Added
Update CHANGELOG
2018-10-06 01:10:11 +08:00
- Support for actions https://github.com/tuist/tuist/pull/136 by @pepibumur.
Version 0.6.0
2018-09-20 00:48:22 +08:00
## 0.6.0
Check Swift version before installing (#134) * Check Swift version before installing * Test changes * Include the type of error to catch * Add CHANGELOG entry
2018-09-20 00:43:43 +08:00
### Added
- Check that the local Swift version is compatible with the version that will be installed https://github.com/tuist/tuist/pull/134 by @pepibumur.
Bump xcodeproj to 6.0.0 (#133) * Bump xcodeproj to 6.0.0 * Remove warning * Get tests passing * Don't import xcodeproj with testable * Add entry to changelog * Build with Xcode 10 on CI * Add .swift-version file * Fix test
2018-09-19 17:44:31 +08:00
### Changed
- Bump xcodeproj to 6.0.0 https://github.com/tuist/tuist/pull/133 by @pepibumur.
Remove tuistenv from the repository (#135) * Update release notes * Add package-release task * Change install script * Add CHANGELOG entry
2018-09-20 00:46:49 +08:00
### Removed
- Remove `tuistenv` from the repository https://github.com/tuist/tuist/pull/135 by @pepibumur.
0.5.0 version
2018-09-12 00:21:04 +08:00
## 0.5.0
Support JSON and YAML manifests (#110) * Add Yams dependency * Use snake case for enum values * Add support for JSON and Yaml manifests
2018-08-28 16:52:17 +08:00
### Added
Generate .gitignore when bootstrapping a project (#118) * Generate .gitignore file and format the code with the latest version of swiftformat * Update CHANGELOG
2018-09-05 00:39:51 +08:00
Support JSON and YAML manifests (#110) * Add Yams dependency * Use snake case for enum values * Add support for JSON and Yaml manifests
2018-08-28 16:52:17 +08:00
- Support for JSON and Yaml manifests https://github.com/tuist/tuist/pull/110 by @pepibumur.
Generate .gitignore when bootstrapping a project (#118) * Generate .gitignore file and format the code with the latest version of swiftformat * Update CHANGELOG
2018-09-05 00:39:51 +08:00
- Generate `.gitignore` file when running init command https://github.com/tuist/tuist/pull/118 by @pepibumur.
Improve .gitignore (#124) * Improve .gitignore * Update CHANGELOG
2018-09-06 21:11:43 +08:00
- Git ignore Xcode and macOS files that shouldn't be included on a git repository https://github.com/tuist/tuist/pull/124 by @pepibumur.
Add Focus command (#129) * Add Focus command * Fix a bug on installer * Add entry to the CHANGELOG
2018-09-12 00:18:09 +08:00
- Focus command https://github.com/tuist/tuist/pull/129 by @pepibumur.
Generate .gitignore when bootstrapping a project (#118) * Generate .gitignore file and format the code with the latest version of swiftformat * Update CHANGELOG
2018-09-05 00:39:51 +08:00
Add missing CHANGELOG entry
2018-08-27 03:01:15 +08:00
### Fixed
- Snake-cased build settings keys https://github.com/tuist/tuist/pull/107 by @pepibumur.
Bundled releases (#104) * Add release bundling * Fix test * Update changelog * Update CHANGELOG * Regenerate tuistenv and bump version * Some fixes * Test installer * Regenerate tuistenv
2018-08-24 17:11:38 +08:00
## 0.4.0
Lint that require files exist (#98) * Lint non-existence of files using the linters approach * Lint that libraries don't contain resources * Adjust formatting * Update CHANGELOG
2018-08-21 02:04:05 +08:00
### Added
- Throw an error if a library target contains resources https://github.com/tuist/tuist/pull/98 by @pepibumur.
Support Playgrounds (#103) * Add PlaygroundGenerator * Test PlaygroundGenerator * Generate playgrounds from init command * Test init command changes * Generate Playgrounds group * Add Playgrounds references * Update CHANGELOG * Test ProjectFileElements * Fix test
2018-08-21 21:53:34 +08:00
- Playgrounds support https://github.com/tuist/tuist/pull/103 by @pepibumur.
Bundled releases (#104) * Add release bundling * Fix test * Update changelog * Update CHANGELOG * Regenerate tuistenv and bump version * Some fixes * Test installer * Regenerate tuistenv
2018-08-24 17:11:38 +08:00
- Faster installation using bundled releases https://github.com/tuist/tuist/pull/104 by @pepibumur.
Lint that require files exist (#98) * Lint non-existence of files using the linters approach * Lint that libraries don't contain resources * Adjust formatting * Update CHANGELOG
2018-08-21 02:04:05 +08:00
Show a linting warning if a Carthage dependency doesnt exist (#96) * Show a linting warning if a Carthage dependency doesnt exist * Throw an error for the non-carthage frameworks that don't exist * Test linting
2018-08-21 01:01:58 +08:00
### Changed
- Don't fail if a Carthage framework doesn't exist. Print a warning instead https://github.com/tuist/tuist/pull/96 by @pepibuymur
Lint that require files exist (#98) * Lint non-existence of files using the linters approach * Lint that libraries don't contain resources * Adjust formatting * Update CHANGELOG
2018-08-21 02:04:05 +08:00
- Missing file errors are printed together https://github.com/tuist/tuist/pull/98 by @pepibumur.
Show a linting warning if a Carthage dependency doesnt exist (#96) * Show a linting warning if a Carthage dependency doesnt exist * Throw an error for the non-carthage frameworks that don't exist * Test linting
2018-08-21 01:01:58 +08:00
Version 0.3.0
2018-08-20 16:37:24 +08:00
## 0.3.0
Update CHANGELOG
2018-08-06 04:45:48 +08:00
### Added
- Homebrew formula https://github.com/tuist/tuist/commit/0ab1c6e109134337d4a5e074d77bd305520a935d by @pepibumur.
Use https links (#91) * Use https links * Replace missing link * Update changelog
2018-08-17 18:50:46 +08:00
## Changed
- Replaced ssh links with the https version of them https://github.com/tuist/tuist/pull/91 by @pepibumur.
Add FRAMEWORK_SEARCH_PATHS settings when framework dependencies are defined (#87) * Add FRAMEWORK_SEARCH_PATHS settings when framework dependencies are defined * Update CHANGELOG
2018-08-08 19:27:19 +08:00
## Fixed
- `FRAMEWORK_SEARCH_PATHS` build setting not being set for precompiled frameworks dependencies https://github.com/tuist/tuist/pull/87 by @pepibumur.
Version 0.2.0
2018-08-06 04:12:26 +08:00
## 0.2.0
Add install command to tuistenv (#83) * wip * Add install command * Update CHANGELOG
2018-08-01 05:13:38 +08:00
### Added
- Install command https://github.com/tuist/tuist/pull/83 by @pepibumur.
Add --help-env command
2018-08-02 18:43:41 +08:00
- `--help-env` command to tuistenv by @pepibumur.
Fix missing target dependencies
2018-08-05 23:21:26 +08:00
### Fixed
- Fix missing target dependencies by @pepibumur.
Update CHANGELOG
2018-08-06 04:11:08 +08:00
### Removed
- Internal deprecation warnings by @pepibumur.
Update CHANGELOG
2018-07-21 12:10:33 +08:00
Version 0.1.0
2018-08-01 04:19:26 +08:00
## 0.1.0
Update CHANGELOG
2018-07-21 12:10:33 +08:00
### Added
LocalCommand prints the local versions if no arguments are given (#79) * Update LocalCommand to print local versions if no argument is given * Generate tuistenv binary * Add CHANGELOG entry
2018-07-26 05:30:18 +08:00
- Local command prints all the local versions if no argument is given https://github.com/tuist/tuist/pull/79 by @pepibumur.
Rename project
2018-07-23 19:59:52 +08:00
- Platform, product, path and name arguments to the init command https://github.com/tuist/tuist/pull/64 by @pepibumur.
- Lint that `Info.plist` and `.entitlements` files are not copied into the target products https://github.com/tuist/tuist/pull/65 by @pepibumur
- Lint that there's only one resources build phase https://github.com/tuist/tuist/pull/65 by @pepibumur.
Implement command runner (#81) * wip * Get the runner working * Add tests * Update CHANGELOG * Compile tuistenv
2018-08-01 03:55:26 +08:00
- Command runner https://github.com/tuist/tuist/pull/81/ by @pepibumur.
Remove build phases models (#67) * Remove BuildPhase from the ProjectDescription target * Some refactoring * More code cleanup * Get command working again * Fix tests * Hide schemes * Fix tests and update CHANGELOG * Remove references to schemes
2018-07-22 06:45:33 +08:00
### Added
Rename project
2018-07-23 19:59:52 +08:00
- Sources, resources, headers and coreDataModels property to the `Target` model https://github.com/tuist/tuist/pull/67 by @pepibumur.
Remove build phases models (#67) * Remove BuildPhase from the ProjectDescription target * Some refactoring * More code cleanup * Get command working again * Fix tests * Hide schemes * Fix tests and update CHANGELOG * Remove references to schemes
2018-07-22 06:45:33 +08:00
Migration to Codable (#78) * Refactor to Codable - update all models in ProjectDescription * Update tests to test Codable models * Update CHANGELOG * Fix JSON coding strategy in tests * Fix `projects` coding key in Workspace model * Remove file header comments
2018-07-27 02:03:42 +08:00
### Changed
- `JSON` and `JSONConvertible` replaced with Swift's `Codable` conformance.
Remove build phases models (#67) * Remove BuildPhase from the ProjectDescription target * Some refactoring * More code cleanup * Get command working again * Fix tests * Hide schemes * Fix tests and update CHANGELOG * Remove references to schemes
2018-07-22 06:45:33 +08:00
### Removed
Rename project
2018-07-23 19:59:52 +08:00
- The scheme attribute from the `Project` model https://github.com/tuist/tuist/pull/67 by @pepibumur.
- Build phases and build files https://github.com/tuist/tuist/pull/67 by @pepibumur.