3squared/peaknetwork

PeakNetwork is a Swift networking microframework, built on top of Session and leveraging the power of Codable.

peaknetwork's Issues

Provide more flexibility when chaining operations

DecodableOperation is useful, but has a very narrow use case. Either allow it to be subclassed to provide more flexibility when building chains of operations, or make a version that implements ConsumesResult.

Add an operation to make batch uploads easier

I've encountered situations where, given an array of Encodables, I need to upload each one in an individual request to the web service I'm working with. It would be nice if PeakNetwork had an operation that took a Requestable and an array of Codables and performed a request for each one.

Support `downloadTask` and `uploadTask` on `Session`

Session only has support for dataTasks currently. Nice to support the other types of task easily. Additionally, built-in operations for upload/download would be handy.

https://developer.apple.com/documentation/foundation/urlsession/1411608-downloadtask
https://developer.apple.com/documentation/foundation/urlsession/1411518-uploadtask

Provide clearer definition of the role of WebAPI

Version 6.0.0 replaces the Requestable paradigm with that of WebAPI. As I understand it, WebAPI is responsible for defining all information (base URL, endpoints, common headers, etc.) about the web API you are interfacing with in your application. This rigidity is pleasing and reminds me of Retrofit by Square.

However, I'm not sure WebAPI should be responsible for creating operations or holding information about the session they are executed on. Personally, I feel WebAPI should only be a static representation and definition of a web API.

Furthermore, unless the APIs for Resource are more strictly defined with Endpoint in mind, I find the availability of Endpoint to users of PeakNetwork a little redundant.