CocoaPods trunk is moving to be read-only. Read more on the blog, there are 14 months to go.
| TestsTested | ✗ |
| LangLanguage | SwiftSwift |
| License | MIT |
| ReleasedLast Release | Feb 2018 |
| SwiftSwift Version | 3.0 |
| SPMSupports SPM | ✓ |
Maintained by Liquidsoul.
This is my attempt to implement some Sourcery templates which automatically generates JSON bindings for your structs and classes.
My objective here is to provide a fully tested code generation template that will let you skip the pain of writing this code:
extension Contact: JSONDeserializable {
enum Fields: String {
case identifier = "id"
case firstName = "first_name"
case lastName = "last_name"
case age = "age"
}
init?(JSONObject: Any) {
guard let JSONObject = JSONObject as? [String: Any],
let let id = JSONObject[Fields.identifier.rawValue] as? String,
let firstName = JSONObject[Fields.firstName.rawValue] as? String,
let lastName = JSONObject[Fields.lastName.rawValue] as? String,
let age = JSONObject[Fields.age.rawValue] as? Int
else {
return nil
}
self.id = id
self.firstName = firstName
self.lastName = lastName
self.age = age
}
}The JSON serialization/deserialization is based on two protocols.
protocol JSONDeserializable {
init?(JSONObject: Any)
}
protocol JSONSerializable {
func toJSONObject() -> Any
}With this tool, you do not need to implement these protocols, the Sourcery templates will do the boiler plate code for you.
To do this, all you need to do is add sourcery annotations to you structs:
// sourcery: AutoJSONSerializable, AutoJSONDeserializable
struct Contact {
// ...
}And then run Sourcery using the templates found in the Templates/ folder of this repository.
Let say you have a model struct like this one:
struct Contact {
let id: String
let firstName: String
let lastName: String
let age: Int
}Adding the AutoJSONDeserializable annotation would make it initializable from this JSON data:
{
"id": "SomeID",
"firstName": "John",
"lastName": "Doe'"
}RawRepresentable enums.JSONSerializable/JSONDeserializable.JSONSerializable or JSONDeserializable implementation.enums and JSON*able types.class types because an extension can only declare convenience initializers
Dates are not supported out of the box anymore
Because almost every project use a different date format to communicate with the server the embedded implementation has been removed. You can support Dates by providing your implementation.
However, you can still find an implementation for Dates Serialization/Deserialization using ISO8601DateFormatter with milliseconds support in the testing code here.
When mapping your JSON to your model structure, you may sometimes want to use a different attribute name as the one in the JSON file.
Let’s say you have this JSON:
{
"id": "SomeID",
"first_name": "John",
"last_name": "Doe'"
}As you can see, the naming convention does not follow camel case. To fix this you can use Sourcery annotations.
On a property, you can define the JSONKey attribute with the JSON name you want to bind the property to:
struct Contact {
let id: String
// sourcery: JSONKey = "first_name"
let firstName: String
// sourcery: JSONKey = "last_name"
let lastName: String
}If you want to nest some types that are not supported out of the box (e.g. enums with associated values) or if you want to provide a special implementation of the serde methods for those types, you can simply implement the JSONSerializable and/or JSONDeserializable protocols.
For example, if Job is an enum, you can still add it to Contact:
struct Contact {
let id: String
let job: Job
}
enum Job: JSONSerializable {
[…]
func toJSONObject() -> Any {
// Implemnt your custom serializer.
}
}You can find some examples in the models I use to test the library in Sources/AutoJSONSerialization/Models/.
To install just copy the following source files in your project:
Sources/AutoJSONSerialization/JSONSerializable.swiftSources/AutoJSONSerialization/JSONDeserializable.swiftAnd then copy the Templates files and configure Sourcery.
This library uses the Swift Package Manager to build the code with a Sourcery pre-build step described using a Makefile.
You can find all the possible build rules using the command make help.
We offer a cocoapods installation which involves several steps to deliver new versions of the library.
This process is automated using fastlane and can be accessed using make. Here it what it’ll do:
cocoapods trunk