Alamofire.request. We’re still working on the rest of the documentation, so let us know if you have any usage questions, either here or on our Swift Forums.
Encodableparameters and not just
[String: Any]dictionaries, use those if you can.
AnyDecodableshould only really be necessary for heterogenous collections, not for your response handling.
Single<Data>where Data could be either an Error or a response's data that will then be decoded afterwards into some sort of object T. However, I'm unsure if this is necessary anymore as unless I'm misunderstanding, publishDecodable attempts to decode via the decoder in that function
sessionTokenthat needs to be placed in the header while writing the request? From what I'm seeing,
.authenticatelooks like it should handle this, however, the value is not really a SecTrust or a SecIdentity. Previously I'd converted the URLRequestConvertible into a URLRequest, then added the object to the headers in the request, however, I'd like to move away from that if possible
Publishedvalue for it, you can access that value directly to add it to the request.
mutableState.refreshTimestampshas been emptied out, but I don't see a spot in which this occurs