Fix cocoapods installation #118
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ddddxxx
reviewed
May 31, 2021
| @@ -44,6 +44,9 @@ package.dependencies += [ | |||
|
|
|||
| ```ruby | |||
| pod 'CombineX', "~> 0.3.1" | |||
|
|
|||
| # or, if you want to use `Foundation` extensions: | |||
| pod 'CombineX/CXFoundation', "~> 0.3.1" | |||
There was a problem hiding this comment.
I have very little knowledge of CocoaPods. So we don't need to state CXFoundation explicitly before, but now we do? With duplicate version number?
There was a problem hiding this comment.
It's an either-or
pod 'CombineX' means you only want CombineX.
pod 'CombineX/CXFoundation means you want CombineX, and CXFoundation.
There was a problem hiding this comment.
Did users need pod 'CombineX/CXFoundation' before?
There was a problem hiding this comment.
Yes, if they want to use CXFoundation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
and we may have encountered a compiler bug