* Prefix static library target filenames with 'lib' to match Xcode.
Given a target named 'MyTarget', Xcode automatically prefixes the filename with 'lib', resulting in the filename 'libMyTarget.a'.
* Update CHANGELOG.md
Co-authored-by: Yonas Kolb <yonaskolb@users.noreply.github.com>
* Bug fix in SourceGenerator
Folders which would have a dot in it, would be added to Copy Bundle Resources even though it contained swift files. This commit, updates the if checks to check if the extension is not of type lproj or xcassets or bundle. This would let Xcodegen handle paths with dots in it
* Refactor SourceGenerator.swift getGroupSources function
* Add FolderWithDot2.0 to TestProject/App_iOS
* Update TestProject fixture with SwiftFileInDotPath and FolderWithDot2.0 changes
* Update test to assert bundles are included in resources
* Remove intentDefinition from whitelistedDirectoryExtensions because it's not a directory, it's always a file so the check is not required
* Allow messages applications to skip the compile sources phase
By default, simple iOS sticker packs created in Xcode do not include
a compile sources phase. This change will allow messages applications
with an empty list of sources to skip that phase entirely.
* Add support for launchAutomaticallySubstyle in run schemes
This is especially important for simple iOS sticker packs that require
this run scheme setting to be set to 2 in order to run the scheme
properly.
* added on-demand-resources setting to project.yml
* update documents
* Apply suggestions from code review
fixed docs
Co-Authored-By: Yonas Kolb <yonaskolb@users.noreply.github.com>
* Make it possible to resourceTags convert to json
* Use sorted() instead of Array initializer
* Avoid merge assetTags if it is empty
* Changed access to resourceTags to inline
* Don't add resourceTags other than chosenBuildPhase is .resources
* update CHANGELOG.md
* update spec loading test
* add a new "generates resource tags" test case
* add resourceTags in Test Fixture and update
Co-authored-by: Yonas Kolb <yonaskolb@users.noreply.github.com>
Resolves#695
Previously, macOS unit test targets would appear to have no test host.
By manually setting the test host in Xcode on the fixture project, I discovered that macOS test hosts require an additional `Contents/MacOS/` path component before the product name.
We can manually detect the platform when setting the test host and as such generate the host correctly for macOS unit test targets.