Esqarrouth/EZSwiftExtensions

Cocoapods Update

Esqarrouth opened this issue · 7 comments

I tried to do this and got this error. My development tools might not be up to date.

 -> EZSwiftExtensions (1.12)
    - ERROR | xcodebuild: Returned an unsuccessful exit code. You can use `--verbose` for more information.
    - ERROR | xcodebuild:  /Users/gok2/Downloads/EZSwiftExtensions-master/Sources/EZSwiftFunctions.swift:81:9: error: unexpected platform condition (expected 'os', 'arch', or 'swift')
    - ERROR | xcodebuild:  /Users/gok2/Downloads/EZSwiftExtensions-master/Sources/EZSwiftFunctions.swift:90:9: error: unexpected platform condition (expected 'os', 'arch', or 'swift')
    - ERROR | xcodebuild:  /Users/gok2/Downloads/EZSwiftExtensions-master/Sources/ArrayExtensions.swift:117:16: error: value of type 'EnumeratedSequence<[Element]>' has no member 'compactMap'
    - WARN  | xcodebuild:  /Users/gok2/Downloads/EZSwiftExtensions-master/Sources/DictionaryExtensions.swift:31:33: warning: redundant conformance constraint 'K': 'Equatable'
    - NOTE  | xcodebuild:  /Users/gok2/Downloads/EZSwiftExtensions-master/Sources/DictionaryExtensions.swift:31:74: note: conformance constraint 'K': 'Equatable' inferred from type here
    - WARN  | xcodebuild:  /Users/gok2/Downloads/EZSwiftExtensions-master/Sources/DictionaryExtensions.swift:180:19: warning: redundant conformance constraint 'K': 'Hashable'
    - NOTE  | xcodebuild:  /Users/gok2/Downloads/EZSwiftExtensions-master/Sources/DictionaryExtensions.swift:180:40: note: conformance constraint 'K': 'Hashable' inferred from type here

Check this out to how to do it: https://github.com/thellimist/EZPods Pods Update CheckList

@goktugyil It looks like your Xcode and Swift version are a bit out of date, since these changes like compactMap were introduced since Xcode 9.3. You can also take a look at my commit in #477 .

Maybe try updating Xcode and see if it works.

Current codes are built based on Xcode 9.3 and Swift 4.1, maybe we should revert some changes and provide a version for Swift 4.0.

Speaking of version, 1.12 is kind of confusing, is it possible that we can use semantic versioning like 2.0.x for Swift 4.0, 2.1.x for Swift 4.1, 3.0.x for Swift 5.0 for better understanding?

Taking a look.

@isimple4 I guess I could make it 2.0, but we did not do it for the swift 2 -> 3 migration. Anyone else feels 2 is a good idea can comment on it.

I released the version as 2.0 on @isimple4 recommendation. #487 there is a retroactive pull request for it. Once thats done, i will close this request.