Background

I want to add multipart/form-data support to CreateAPI. The typical reason people need multipart/form-data is the lack of native support for binary data in JSON format. Let’s say you have an endpoint to post not only a comment but also a photo, you would need to send both data in a payload and want to use multipart/form-data. Looking at the codebase, currently, CreateAPI seems to postpone supporting the format. When an endpoint supports only multipart/form-data in the request body, it becomes Data type. That leaves CreateAPI unusable for such an endpoint.

I can see why it wasn't supported initially because https://github.com/kean/Get doesn't support request body serialization other than JSONEncoder.

What I changed

I added a new option called useStructuredMultipartFormDataRequest to have CreateAPI generate a structured request body, just like normal application/json based requests. The default value is false. Nothing is affected by existing users here. Previously it was limited to just a Data but now it’s easier to compose data with a documented structure. The idea is that once this was implemented, the responsibility is down to CreateAPI users to handle encoding request body. You would need something like MultipartFormDataEncoder instead of JSONEncoder in their HTTP clients.

This is an example of what a multipart/form-data request looks like when the option is enabled.
31469ad#diff-b304b36e06a0c0a28709263be23a00d9ab31e810f924da2a1468e1109e277227

And also, I changed the default type for binary data from String to Data. Despite the JSON format doesn’t support binary data, JSONEncoder and JSONDecoder does support Data type using Base64 encoding/decoding. Data would still work with existing JSONEncoder and JSONDecoder.

• https://developer.apple.com/documentation/foundation/jsonencoder/2895381-dataencodingstrategy
• https://developer.apple.com/documentation/foundation/jsondecoder/2895108-datadecodingstrategy

This part would be a breaking change. Given the version is still 0.1.1 and theoretically, CreateAPI users have never utilised binary data in their request body just yet (since multipart/form-data support isn't in place!), I hope this is an acceptable change🙏

Another thought on using Data for binary field. In a multipart/form-data request, we normally also need to specify a MIME type. Data type alone can do nothing to identify the type. I think we can solve that by leveraging custom struct type having both mimeType and data properties or assuming MIME type from magic bytes, like https://github.com/sendyhalim/Swime.