netable
netable copied to clipboard
steamclock
A Swift library for encapsulating network APIs using Codable in a type-oriented way.
Adding interceptors to Netable will be necessary for working with our mocking libraries. I think we can be pretty flexible here and offload most of the work to the actual...
One of the design goals for Netable was to reduce the need for "wide" enums or function interfaces to specify sets of operations, stuff like: ``` enum Endpoint { case...
Change `jsonKeyEncodingStrategy` and `jsonKeyDecodingStrategy` to non-optional with default values
As they currently exist, you can create a request like ``` struct UserRequest: Request { // ... var jsonKeyDecodingStrategy: JSONDecoder.KeyDecodingStrategy { return .convertFromSnakeCase } } ``` that _looks_ correct but...
Right now since our graphQL requests just read from one file we can't do shared fragments, which are a pretty powerful feature in GQL.
When encoding GET parameters, we're currently encoding the params to JSON, the decoding to [String: Any]. This is far from ideal but at the time seems like the simplest way....
In one of our projects, we found ourselves often needing to identify networking errors, and so we've extended the error as such: ``` var isNetworkingError: Bool { switch errorCode {...
- We often have to write numerous helpers to process and output date and time strings - Server APIs also tend to require and return date formats inconsistently - Simple...
> My feeling is that network reachability is different enough from accessing REST APIs that there isn’t much value in just building it into SCNetworkAPI. If we find we are...
Right now we are pretty expansive in what errors we will retry on. In the discussion on #71 we ended up adding retying for a type of error that didn't...
Look into XCframework or custom build scripts
Metadata
Owner
Metadata
A Swift library for encapsulating network APIs using Codable in a type-oriented way.