Mrteller

Some methods of custom URLSessionDelegate are ignored by APIClient

2

It is handy we can set our own custom URLSessionDelegate in APIClient init. ``` Swift self.api = APIClient(baseURL: baseURL, { $0.sessionDelegate = ... }) ``` But custom delegate methods are...

If we turn of [alwaysIncludeDecodableImplementation](https://github.com/CreateAPI/CreateAPI/blob/main/Docs/ConfigOptions.md#entitiesalwaysincludedecodableimplementation) and/or [alwaysIncludeEncodableImplementation](https://github.com/CreateAPI/CreateAPI/blob/main/Docs/ConfigOptions.md#entitiesalwaysincludeencodableimplementation) in `[ConfingOptions](https://github.com/CreateAPI/CreateAPI/blob/main/Docs/ConfigOptions.md#entitiesalwaysincludedecodableimplementation)` then properly names of generated datatypes go out of sync with property names in OpenAPI spec because default setting for [useswiftypropertynames](https://github.com/CreateAPI/CreateAPI/blob/main/Docs/ConfigOptions.md#useswiftypropertynames)...

The `type: string` in OpenAPI spec should result in `String` property in Swift datatype and it is usually so. But if the property in the OpenAPI spec **also** has `format:...

Using [acronyms](https://github.com/CreateAPI/CreateAPI/blob/main/Docs/ConfigOptions.md#acronyms) to conform to code style can be handy. But it can lead to generating datatypes with incorrect property names. Those datatypes won't be decoded/encoded properly. Worth noting that...

The question is if this behaviour is intended or not. Suppose we have a piece of some `swagger.json`. At some It contains parameter "AccessKey" which should be passed in header...

# Less verbose initialization of discriminated union types with associated values

12

### Motivation While working with generated code for OpenAPI schemas that use discriminators (representing enums with associated values in Swift), I noticed that the current implementation requires redundant specification of...