How to migrate Alamofire router class to Swift 3?

后端 未结 1 1715
孤独总比滥情好
孤独总比滥情好 2020-12-13 21:37

Does anybody know how to change this entire approach to Swift 3? At this moment I have something very similar to this working OK on Swift 2.2 but now I\'m trying to change t

相关标签:
1条回答
  • 2020-12-13 22:20

    EDITED for Alamofire 4.0.0 release (updated URLRequestConvertible protocol with throwing capabilities):

    A lot has changed in Swift 3 and you should first really read up on all the changes, maybe starting at http://swift.org. Here's the fixed code:

    enum Router: URLRequestConvertible {
        static let baseURLString = "http://example.com"
        static var OAuthToken: String?
        
        case createUser([String: AnyObject])
        case readUser(String)
        case updateUser(String, [String: AnyObject])
        case destroyUser(String)
        
        var method: Alamofire.HTTPMethod {
            switch self {
            case .createUser:
                return .post
            case .readUser:
                return .get
            case .updateUser:
                return .put
            case .destroyUser:
                return .delete
            }
        }
        
        var path: String {
            switch self {
            case .createUser:
                return "/users"
            case .readUser(let username):
                return "/users/\(username)"
            case .updateUser(let username, _):
                return "/users/\(username)"
            case .destroyUser(let username):
                return "/users/\(username)"
            }
        }
        
        func asURLRequest() throws -> URLRequest {
            let url = URL(string: Router.baseURLString)!
            var urlRequest = URLRequest(url: url.appendingPathComponent(path))
            urlRequest.httpMethod = method.rawValue
            
            if let token = Router.OAuthToken {
                urlRequest.setValue("Bearer \(token)", forHTTPHeaderField: "Authorization")
            }
            
            switch self {
            case .createUser(let parameters):
                return try Alamofire.JSONEncoding.default.encode(urlRequest, with: parameters)
            case .updateUser(_, let parameters):
                return try Alamofire.URLEncoding.default.encode(urlRequest, with: parameters)
            default:
                return urlRequest
            }
        }
    }
    

    The main changes for Swift 3 are :

    • enum cases are now lowercase and you should adopt it too.
    • Variable names now start with lowercase, even if it's an abbreviation like "URL". That why the protocol requires var urlRequest and not var URLRequest (and it would conflict with the next point)
    • Bye-bye NS prefix in many places. NSURLRequest and NSMutableURLRequest are now URLRequest, NSURL is URL, etc.
    • How you name your functions and parameters is now a lot less redundant and more natural. See for example how URLByAppendingPathComponent has changed.

    And as for Alamofire v4 :

    • There's a new ParameterEncoding protocol to encoding parameters yourself is different but more versatile
    • MANY other changes which have no impact here but you sure have to read about them too.

    And final word of advice : avoid migrating to unreleased versions of a programming language or API if it's time-sensitive. Swift 3 won't budge much but Alamofire still might! For example the ParameterEncoding protocol is only two days old! (EDIT: and indeed it changed since, now in its final version above)

    Cheers

    0 讨论(0)
提交回复
热议问题