Updated Automatic Integration Example - #1
Conversation
| --destination UnitTestTarget | ||
| --project MyProject.xcodeproj \ | ||
| --targets MyProject SomeExternalTarget \ | ||
| --destination MyProjectTests |
There was a problem hiding this comment.
Thanks for the PR! I agree that it could be confusing since most iOS devs might not have multi-module projects. To keep the example more concrete, what do you think about making the example something similar to:
--project Bird.xcodeproj \
--targets Bird BirdManagers \
--destination BirdTestsThere was a problem hiding this comment.
That works! Just the fact that the naming convention is consistent across the three different arguments is much clearer than before. This is the issue I ran into last night. I was attempting to use my BirdModel file, which had a BirdModel protocol and I used that as a target.
91aac5d to
77551d6
Compare
7d6f400 to
77551d6
Compare
|
Accidentally closed the PR. Anyway, for a simpler installation process I’m actually going to make |
|
I was actually going to try and implement a guided process over the weekend. I need to spend some time on this since it’s been over a year since I’ve done any terminal apps and even then they were super basic. I would like to have a read line for each argument. Something like: What project? |
The previous example for Automatic Integration was slightly confusing. Although the argument is named "targets" the arguments passed seemed as if they could be files (BirdModels.swift). The suggested update takes the approach that the user is using a single project, using the models within that project (and possibly some external target as well), and sets the destination as the default testing folder.