Brian Cardarella
Brian Cardarella
Using 'supportedDestinations' with watchOS app doesn't generate an 'Embed Watch Content' build phase
I am also looking for an answer on this. The doc's aren't clear if `watchOS` is supported for `supportedDestinations` or not. It's not included in the list of supported destrinations...
Using 'supportedDestinations' with watchOS app doesn't generate an 'Embed Watch Content' build phase
Perhaps it is fixed with https://github.com/yonaskolb/XcodeGen/pull/1438
Using 'supportedDestinations' with watchOS app doesn't generate an 'Embed Watch Content' build phase
@tatsuky does this mean that it would skip `watchos`?
Using 'supportedDestinations' with watchOS app doesn't generate an 'Embed Watch Content' build phase
@tatsuky perhaps emmit a warning or error if it is included and point to this issue so understand why it isn't (yet) supported. Looking at the issue tracker and it...
If the project is being renamed can a patch release still be done under this project that emits a warning telling people about the new name and that they should...
@lolmaus I wasn't sure how best to handle this case or how to work around it within unit tests. Ideally we could support both use cases without having the `null`...
Well all acceptance tests should make use of the context.
I'd prefer to not impose opinions on the serializer and have it just 1-to-1. However, we could offer an option to force to underscore ``` elixir s(data, underscore: true) ```...
this, still happening. Solution por favor?
Correct PR #391