Skip to content

Commit 469105b

Browse files
author
David McRae
committed
Add example in the example MergeFile and add a draft of the README
1 parent 40dd605 commit 469105b

File tree

2 files changed

+19
-2
lines changed

2 files changed

+19
-2
lines changed

PodMergeExample/MergeFile

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,12 +11,13 @@ group 'UI'
1111
end
1212

1313
group 'MergedSwiftPods' do
14-
pod 'SnapKit'
15-
pod 'SwiftyJSON'
14+
pod 'SnapKit'
15+
pod 'SwiftyJSON'
1616
end
1717

1818
group 'AlamofireGroup' do
1919
swift_version! '5.0'
20+
platform :ios, '11.0'
2021
has_dependencies!
2122

2223
pod 'Alamofire'

README.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -199,6 +199,22 @@ end
199199

200200
This is especially handy if some of the pods in your group do not have a Swift Version defined in their `podspec`.
201201

202+
#### platform
203+
204+
If you have multiple platforms in your base Podfile, you can specify the `platform` for each group in your MergeFile
205+
206+
```ruby
207+
group 'SwiftPodsGroup'
208+
platform :ios, '11.0'
209+
210+
pod 'SwiftPodA'
211+
pod 'SwiftPodB'
212+
pod 'SwiftPodC'
213+
end
214+
```
215+
216+
This is helpful when you have a Podfile with Pods for iOS, WatchOS, etc...
217+
202218
## Version Control (like git)
203219

204220
You should definitely commit the `MergeFile` into your repository, since this is just like your Podfile, and is required for the plugin to work.

0 commit comments

Comments
 (0)