* 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>
* Improving variable expansion runtime
The current implementation of variable expansion is O(n x m) with n being the
number of strings in the project spec and m being the number of project variables.
This implementation is now O(n).
Also, this effectively deprecates the support for $legacy_variables in favor of the
${new_variables} making this whole patch possible.
* Adding option to disable variable expansion
* Adding performance test for spec loading
* Updating changelog
PR #624 introduced a bug with operator priorities discarding false link settings
for dependencies when the target is an executable and the dependency a static
library. This PR fixes that.
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.
