You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,8 +2,8 @@
2
2
3
3
## Next Version
4
4
5
-
### Added
6
-
-Added `targetOrdering` option to control the order of targets in the generated project (sidebar in Xcode, `xcodebuild -list` output). Unlisted targets fall back to the existing alphabetical order, so behavior is unchanged when the option is not set. @mirkokg
5
+
### Changed
6
+
-Targets in the generated project now follow the declaration order from the YAML spec (Xcode sidebar, `xcodebuild -list` output). Previously they were always sorted alphabetically. JSON specs and projects built programmatically continue to sort alphabetically, since key order isn't recoverable. @mirkokg
Copy file name to clipboardExpand all lines: Docs/ProjectSpec.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -151,7 +151,6 @@ Note that target names can also be changed by adding a `name` property to a targ
151
151
- `top`- at the top, before files
152
152
- `bottom`(default) - at the bottom, after other files
153
153
- [ ] **groupOrdering**: **[[GroupOrdering]](#groupOrdering)** - An order of groups.
154
-
- [ ] **targetOrdering**: **[String]** - An ordered list of target names. Listed targets appear in this order in the generated project (sidebar in Xcode, `xcodebuild -list` output); unlisted targets follow, sorted alphabetically. If a name in this list doesn't match any target or aggregate target, a validation error is raised. Defaults to an empty list, in which case all targets are sorted alphabetically.
155
154
- [ ] **transitivelyLinkDependencies**: **Bool** - If this is `true` then targets will link to the dependencies of their target dependencies. If a target should embed its dependencies, such as application and test bundles, it will embed these transitive dependencies as well. Some complex setups might want to set this to `false` and explicitly specify dependencies at every level. Targets can override this with [Target](#target).transitivelyLinkDependencies. Defaults to `false`.
156
155
- [ ] **generateEmptyDirectories**: **Bool** - If this is `true` then empty directories will be added to project too else will be missed. Defaults to `false`.
157
156
- [ ] **findCarthageFrameworks**: **Bool** - When this is set to `true`, all the individual frameworks for Carthage framework dependencies will automatically be found. This property can be overridden individually for each carthage dependency - for more details see See **findFrameworks** in the [Dependency](#dependency) section. Defaults to `false`.
0 commit comments