• JSONParser
• LocationFetcher
• APIClient
• Figure out how to do recover and fallback using Swift Concurrency

Hi all,

Due to the version 1 of your library is not compatible with Xcode 10, we are updating our project to use the last stable version of the library.

During that migration we have identified several functionalities that we cannot use on the current version.

Due to our app needs, we need to read response status code and headers. It was possible through the DroskyResponse (which has been removed) on version 1, but it is not possible on the current version, because the new APIClient class does not return this information.

Is there any way to read and process response status codes and http headers on the current version?

Thanks a lot.

We are using the version 2.2.1 and we want to upload our app to the Apple Store. Can we disable the geolocation requirements?

Thanks.

With the improvements in URLSession for iOS 11, I think it’s time we remove Alamofire and just use it instead of it

When a request is redirected, the parameters are lost somehow

It's very pretty, but you can't set in what queue you want the code to be executed, so it's leading to some weird edge cases that I'd rather remove

It should be great to add the possibility of cancelling the current network request (or requests) at any time, e. g., when user navigates back to a previous screen and the network response block tries to access an unexisting view controller or another property

This would allow to prioritise some network calls over other, control how many are being sent at the same time, etc...

Task:

func updateUser(_ user: User) -> Task<User> { .never }

Async/await:

func updateUser(_ user: User) async throws -> User { ??? }

Example:
extension Array where Element == PostAuthenticationJob { func waitForCompletion() async throws { _ = await withThrowingTaskGroup(of: Void.self) { group in self.map { job in group.addTask { try await job() } } } return } }