A Swift package for encoding to- and decoding from JSON API compliant requests and responses.
See the JSON API Spec here: https://jsonapi.org/format/
- JSONAPI
- Table of Contents
- Primary Goals
- Dev Environment
- Project Status
- Usage
- Example
- JSONAPI+Testing
- JSONAPI+Arbitrary
- JSONAPI+OpenAPI
The primary goals of this framework are:
- Allow creation of Swift types that are easy to use in code but also can be encoded to- or decoded from JSON API v1.0 Spec compliant payloads without lots of boilerplate code.
- Leverage
Codableto avoid additional outside dependencies and get operability with non-JSON encoders/decoders for free. - Do not sacrifice type safety.
- Be platform agnostic so that Swift code can be written once and used by both the client and the server.
The big caveat is that, although the aim is to support the JSON API spec, this framework ends up being naturally opinionated about certain things that the API Spec does not specify. These caveats are largely a side effect of attempting to write the library in a "Swifty" way.
If you find something wrong with this library and it isn't already mentioned under Project Status, let me know! I want to keep working towards a library implementation that is useful in any application.
- Swift 4.2+
- Swift Package Manager OR Cocoapods
To use this framework in your project via Cocoapods instead of Swift Package Manager, add the following dependencies to your Podfile.
pod 'Poly', :git => 'https://github.com/mattpolzin/Poly.git'
pod 'JSONAPI', :git => 'https://github.com/mattpolzin/JSONAPI.git'
To create an Xcode project for JSONAPI, run
swift package generate-xcodeproj
To run the included Playground files, create an Xcode project using Swift Package Manager, then create an Xcode Workspace in the root of the repository and add both the generated Xcode project and the playground to the Workspace.
Note that Playground support for importing non-system Frameworks is still a bit touchy as of Swift 4.2. Sometimes building, cleaning and building, or commenting out and then uncommenting import statements (especially in the Entities.swift Playground Source file) can get things working for me when I am getting an error about JSONAPI not being found.
data- Encoding/Decoding
included- Encoding/Decoding
errors- Encoding/Decoding
meta- Encoding/Decoding
jsonapi(i.e. API Information)- Encoding/Decoding
links- Encoding/Decoding
id- Encoding/Decoding
type- Encoding/Decoding
attributes- Encoding/Decoding
relationships- Encoding/Decoding
links- Encoding/Decoding
meta- Encoding/Decoding
data- Encoding/Decoding
links- Encoding/Decoding
meta- Encoding/Decoding
href- Encoding/Decoding
meta- Encoding/Decoding
- Support transforms on
Attributesvalues (e.g. to support different representations ofDate) - Support validation on
Attributes. - Support sparse fieldsets. At the moment, not sure what this support will look like. A client can likely just define a new model to represent a sparse population of another model in a very specific use case. On the server side, it becomes much more appealing to be able to support arbitrary combinations of omitted fields.
- Create more descriptive errors that are easier to use for troubleshooting.
- Disallow optional array in
Attribute(should be empty array, notnull). - Only allow
TransformedAttributeand its derivatives as stored properties withinAttributesstruct. Computed properties can still be any type because they do not get encoded or decoded. - Only allow
ToManyRelationshipandToOneRelationshipwithinRelationshipsstruct.
- (Maybe) Use
KeyPathto specifyIncludesthus creating type safety around the relationship between a primary resource type and the types of included resources. - (Maybe) Replace
SingleResourceBodyandManyResourceBodywith support at theDocumentlevel to just interpretPrimaryResource,PrimaryResource?, or[PrimaryResource]as the same decoding/encoding strategies. - Support sideposting. JSONAPI spec might become opinionated in the future (json-api/json-api#1197, json-api/json-api#1215, json-api/json-api#1216) but there is also an existing implementation to consider (https://jsonapi-suite.github.io/jsonapi_suite/ruby/writes/nested-writes). At this time, any sidepost implementation would be an awesome tertiary library to be used alongside the primary JSONAPI library. Maybe
JSONAPISideloading. - Error or warning if an included resource object is not related to a primary resource object or another included resource object (Turned off or at least not throwing by default).
In this documentation, in order to draw attention to the difference between the JSONAPI framework (this Swift library) and the JSON API Spec (the specification this library helps you follow), the specification will consistently be referred to below as simply the SPEC.
A ResourceObjectDescription is the JSONAPI framework's representation of what the SPEC calls a Resource Object. You might create the following ResourceObjectDescription to represent a person in a network of friends:
enum PersonDescription: IdentifiedResourceObjectDescription {
static var jsonType: String { return "people" }
struct Attributes: JSONAPI.Attributes {
let name: Attribute<[String]>
let favoriteColor: Attribute<String>
}
struct Relationships: JSONAPI.Relationships {
let friends: ToManyRelationship<Person>
}
}The requirements of a ResourceObjectDescription are:
- A static
var"jsonType" that matches the JSON type; The SPEC requires every Resource Object to have a "type". - A
structofAttributes- OR -typealias Attributes = NoAttributes - A
structofRelationships- OR -typealias Relationships = NoRelationships
Note that an enum type is used here for the ResourceObjectDescription; it could have been a struct, but ResourceObjectDescriptions do not ever need to be created so an enum with no cases is a nice fit for the job.
This readme doesn't go into detail on the SPEC, but the following Resource Object would be described by the above PersonDescription:
{
"type": "people",
"id": "9",
"attributes": {
"name": [
"Jane",
"Doe"
],
"favoriteColor": "Green"
},
"relationships": {
"friends": {
"data": [
{
"id": "7",
"type": "people"
},
{
"id": "8",
"type": "people"
}
]
}
}
}Once you have a ResourceObjectDescription, you create, encode, and decode ResourceObjects that "fit the description". If you have a CreatableRawIdType (see the section on RawIdTypes below) then you can create new ResourceObjects that will automatically be given unique Ids, but even without a CreatableRawIdType you can encode, decode and work with resource objects.
The ResourceObject and ResourceObjectDescription together with a JSONAPI.Meta type and a JSONAPI.Links type embody the rules and properties of a JSON API Resource Object.
A ResourceObject needs to be specialized on four generic types. The first is the ResourceObjectDescription described above. The others are a Meta, Links, and MaybeRawId.
The second generic specialization on ResourceObject is Meta. This is described in its own section below. All Meta at any level of a JSON API Document follow the same rules. You can use NoMetadata if you do not need to package any metadata with the ResourceObject.
The third generic specialization on ResourceObject is Links. This is described in its own section below. All Links at any level of a JSON API Document follow the same rules, although the SPEC makes different suggestions as to what types of links might live on which parts of the Document. You can use NoLinks if you do not need to package any links with the ResourceObject.
The last generic specialization on ResourceObject is MaybeRawId. This is either a RawIdType that can be used to uniquely identify ResourceObjects or it is Unidentified which is used to indicate a ResourceObject does not have an Id (which is useful when a client is requesting that the server create a ResourceObject and assign it a new Id).
The raw type of Id to use for the ResourceObject. The actual Id of the ResourceObject will not be a RawIdType, though. The Id will package a value of RawIdType with a specialized reference back to the ResourceObject type it identifies. This just looks like Id<RawIdType, ResourceObject<ResourceObjectDescription, Meta, Links, RawIdType>>.
Having the ResourceObject type associated with the Id makes it easy to store all of your resource objects in a hash broken out by ResourceObject type; You can pass Ids around and always know where to look for the ResourceObject to which the Id refers. This encapsulation provides some type safety because the Ids of two ResourceObjects with the "raw ID" of "1" but different types will not compare as equal.
A RawIdType is the underlying type that uniquely identifies a ResourceObject. This is often a String or a UUID.
Often you can use one RawIdType for many if not all of your ResourceObjects. That means you can save yourself some boilerplate by using typealiases like the following:
public typealias ResourceObject<Description: JSONAPI.ResourceObjectDescription, Meta: JSONAPI.Meta, Links: JSONAPI.Links> = JSONAPI.ResourceObject<Description, Meta, Links, String>
public typealias NewResourceObject<Description: JSONAPI.ResourceObjectDescription, Meta: JSONAPI.Meta, Links: JSONAPI.Links> = JSONAPI.ResourceObject<Description, Meta, Links, Unidentified>It can also be nice to create a typealias for each type of resource object you want to work with:
typealias Person = ResourceObject<PersonDescription, NoMetadata, NoLinks>
typealias NewPerson = NewResourceObject<PersonDescription, NoMetadata, NoLinks>Note that I am assuming an unidentified person is a "new" person. I suspect that is generally an acceptable conflation because the only time the SPEC allows a Resource Object to be encoded without an Id is when a client is requesting the given Resource Object be created by the server and the client wants the server to create the Id for that object.
There are two types of Relationships: ToOneRelationship and ToManyRelationship. A ResourceObjectDescription's Relationships type can contain any number of Relationship properties of either of these types. Do not store anything other than Relationship properties in the Relationships struct of a ResourceObjectDescription.
In addition to identifying resource objects by Id and type, Relationships can contain Meta or Links that follow the same rules as Meta and Links elsewhere in the JSON API Document.
To describe a relationship that may be omitted (i.e. the key is not even present in the JSON object), you make the entire ToOneRelationship or ToManyRelationship optional. However, this is not recommended because you can also represent optional relationships as nullable which means the key is always present. A ToManyRelationship can naturally represent the absence of related values with an empty array, so ToManyRelationship does not support nullability at all. A ToOneRelationship can be marked as nullable (i.e. the value could be either null or a resource identifier) like this:
let nullableRelative: ToOneRelationship<Person?, NoMetadata, NoLinks>A ResourceObject that does not have relationships can be described by adding the following to a ResourceObjectDescription:
typealias Relationships = NoRelationshipsRelationship values boil down to Ids of other resource objects. To access the Id of a related ResourceObject, you can use the custom ~> operator with the KeyPath of the Relationship from which you want the Id. The friends of the above Person ResourceObject can be accessed as follows (type annotations for clarity):
let friendIds: [Person.Identifier] = person ~> \.friendsThe Attributes of a ResourceObjectDescription can contain any JSON encodable/decodable types as long as they are wrapped in an Attribute, ValidatedAttribute, or TransformedAttribute struct.
To describe an attribute that may be omitted (i.e. the key might not even be in the JSON object), you make the entire Attribute optional:
let optionalAttribute: Attribute<String>?To describe an attribute that is expected to exist but might have a null value, you make the value within the Attribute optional:
let nullableAttribute: Attribute<String?>A resource object that does not have attributes can be described by adding the following to an ResourceObjectDescription:
typealias Attributes = NoAttributesAttributes can be accessed via the subscript operator of the ResourceObject type as follows:
let favoriteColor: String = person[\.favoriteColor]Sometimes you need to use a type that does not encode or decode itself in the way you need to represent it as a serialized JSON object. For example, the Swift Foundation type Date can encode/decode itself to Double out of the box, but you might want to represent dates as ISO 8601 compliant Strings instead. The Foundation library JSONDecoder has a setting to make this adjustment, but for the sake of an example, you could create a Transformer.
A Transformer just provides one static function that transforms one type to another. You might define one for an ISO 8601 compliant Date like this:
enum ISODateTransformer: Transformer {
public static func transform(_ value: String) throws -> Date {
// parse Date out of input and return
}
}Then you define the attribute as a TransformedAttribute instead of an Attribute:
let date: TransformedAttribute<String, ISODateTransformer>Note that the first generic parameter of TransformAttribute is the type you expect to decode from JSON, not the type you want to end up with after transformation.
If you make your Transformer a ReversibleTransformer then your life will be a bit easier when you construct TransformedAttributes because you have access to initializers for both the pre- and post-transformed value types. Continuing with the above example of a ISODateTransformer:
extension ISODateTransformer: ReversibleTransformer {
public static func reverse(_ value: Date) throws -> String {
// serialize Date to a String
}
}
let exampleAttribute = try? TransformedAttribute<String, ISODateTransformer>(transformedValue: Date())
let otherAttribute = try? TransformedAttribute<String, ISODateTransformer>(rawValue: "2018-12-01 09:06:41 +0000")You can also creator Validators and ValidatedAttributes. A Validator is just a Transformer that by convention does not perform a transformation. It simply throws if an attribute value is invalid.
You can add computed properties to your ResourceObjectDescription.Attributes struct if you would like to expose attributes that are not explicitly represented by the JSON. These computed properties do not have to be wrapped in Attribute, ValidatedAttribute, or TransformedAttribute. This allows computed attributes to be of types that are not Codable. Here's an example of how you might take the person[\.name] attribute from the example above and create a fullName computed property.
public var fullName: Attribute<String> {
return name.map { $0.joined(separator: " ") }
}If your computed property is wrapped in a AttributeType then you can still use the default subscript operator to access it (as would be the case with the person[\.fullName] example above). However, if you add a property to the Attributes struct that is not wrapped in an AttributeType, you must either access it from its full path (person.attributes.newThing) or with the "direct" subscript accessor (person[direct: \.newThing]). This keeps the subscript access unambiguous enough for the compiler to be helpful prior to explicitly casting, comparing, or storing the result.
ResourceObject is a value type, so copying is its default behavior. There are two common mutations you might want to make when copying a ResourceObject:
- Assigning a new
Identifierto the copy of an identifiedResourceObject. - Assigning a new
Identifierto the copy of an unidentifiedResourceObject.
The above can be accomplished with code like the following:
// use case 1
let person1 = person.withNewIdentifier()
// use case 2
let newlyIdentifiedPerson1 = unidentifiedPerson.identified(byType: String.self)
let newlyIdentifiedPerson2 = unidentifiedPerson.identified(by: "2232")The entirety of a JSON API request or response is encoded or decoded from- or to a Document. As an example, a JSON API response containing one Person and no included resource objects could be decoded as follows:
let decoder = JSONDecoder()
let responseStructure = JSONAPI.Document<SingleResourceBody<Person>, NoMetadata, NoLinks, NoIncludes, UnknownJSONAPIError>.self
let document = try decoder.decode(responseStructure, from: data)A JSON API Document is guaranteed by the SPEC to be "data", "metadata", or "errors." If it is "data", it may also contain "metadata" and/or other "included" resources. If it is "errors," it may also contain "metadata."
The first generic type of a JSONAPIDocument is a ResourceBody. This can either be a SingleResourceBody<PrimaryResource> or a ManyResourceBody<PrimaryResource>. You will find zero or one PrimaryResource values in a JSON API document that has a SingleResourceBody and you will find zero or more PrimaryResource values in a JSON API document that has a ManyResourceBody. You can use the Poly types (Poly1 through Poly6) to specify that a ResourceBody will be one of a few different types of ResourceObject. These Poly types work in the same way as the Include types described below.
If you expect a response to not have a "data" top-level key at all, then use NoResourceBody instead.
If you expect a SingleResourceBody to sometimes come back null, you should make your PrimaryResource optional. If you do not make your PrimaryResource optional then a null primary resource will be considered an error when parsing the JSON.
You cannot, however, use an optional PrimaryResource with a ManyResourceBody because the SPEC requires that an empty document in that case be represented by an empty array rather than null.
The second generic type of a JSONAPIDocument is a Meta. This Meta follows the same rules as Meta at any other part of a JSON API Document. It is described below in its own section, but as an example, the JSON API document could contain the following pagination info in its meta entry:
{
"meta": {
"total": 100,
"limit": 50,
"offset": 50
}
}You would then create the following Meta type:
struct PageMetadata: JSONAPI.Meta {
let total: Int
let limit: Int
let offset: Int
}You can always use NoMetadata if this JSON API feature is not needed.
The third generic type of a JSONAPIDocument is a Links struct. Links are described in their own section below.
The fourth generic type of a JSONAPIDocument is an Include. This type controls which types of ResourceObject are looked for when decoding the "included" part of the JSON API document. If you do not expect any included resource objects to be in the document, NoIncludes is the way to go. The JSONAPI framework provides Includes for up to six types of included resource objects. These are named Include1, Include2, Include3, and so on.
IMPORTANT: The number trailing "Include" in these type names does not indicate a number of included resource objects, it indicates a number of types of included resource objects. Include1 can be used to decode any number of included resource objects as long as all the resource objects are of the same type.
To specify that we expect friends of a person to be included in the above example JSONAPIDocument, we would use Include1<Person> instead of NoIncludes.
The fifth generic type of a JSONAPIDocument is an APIDescription. The type represents the "JSON:API Object" described by the SPEC. This type describes the highest version of the SPEC supported and can carry additional metadata to describe the API.
You can specify this is not part of the document by using the NoAPIDescription type.
You can describe the API by a version with no metadata by using APIDescription<NoMetadata>.
You can supply any JSONAPI.Meta type as the metadata type of the API description.
The final generic type of a JSONAPIDocument is the Error. You should create an error type that can decode all the errors you expect your JSONAPIDocument to be able to decode. As prescribed by the SPEC, these errors will be found in the root document member errors.
A Meta struct is totally open-ended. It is described by the SPEC as a place to put any information that does not fit into the standard JSON API Document structure anywhere else.
You can specify NoMetadata if the part of the document being described should not contain any Meta.
A Links struct must contain only Link properties. Each Link property can either be a URL or a URL and some Meta. Each part of the document has some suggested common Links to include but generally any link can be included.
You can specify NoLinks if the part of the document being described should not contain any Links.
If you want to create new JSONAPI.ResourceObject values and assign them Ids then you will need to conform at least one type to CreatableRawIdType. Doing so is easy; here are two example conformances for UUID and String (via UUID):
extension UUID: CreatableRawIdType {
public static func unique() -> UUID {
return UUID()
}
}
extension String: CreatableRawIdType {
public static func unique() -> String {
return UUID().uuidString
}
}There is not anything special going on at the JSONAPI.Attributes and JSONAPI.Relationships levels, so you can easily provide custom key mappings by taking advantage of Codable's CodingKeys pattern. Here are two models that will encode/decode equivalently but offer different naming in your codebase:
public enum ResourceObjectDescription1: JSONAPI.ResourceObjectDescription {
public static var jsonType: String { return "entity" }
public struct Attributes: JSONAPI.Attributes {
public let coolProperty: Attribute<String>
}
public typealias Relationships = NoRelationships
}
public enum ResourceObjectDescription2: JSONAPI.ResourceObjectDescription {
public static var jsonType: String { return "entity" }
public struct Attributes: JSONAPI.Attributes {
public let wholeOtherThing: Attribute<String>
enum CodingKeys: String, CodingKey {
case wholeOtherThing = "coolProperty"
}
}
}You can safely provide your own encoding or decoding functions for your Attributes struct if you need to as long as you are careful that your encode operation correctly reverses your decode operation. Although this is generally not necessary, AttributeType provides a convenience method to make your decoding a bit less boilerplate ridden. This is what it looks like:
public enum ResourceObjectDescription1: JSONAPI.ResourceObjectDescription {
public static var jsonType: String { return "entity" }
public struct Attributes: JSONAPI.Attributes {
public let property1: Attribute<String>
public let property2: Attribute<Int>
public let property3: Attribute<String>
public let weirdThing: Attribute<String>
enum CodingKeys: String, CodingKey {
case property1
case property2
case property3
}
}
public typealias Relationships = NoRelationships
}
extension ResourceObjectDescription1.Attributes {
public init(from decoder: Decoder) throws {
let container = try decoder.container(keyedBy: CodingKeys.self)
property1 = try .defaultDecoding(from: container, forKey: .property1)
property2 = try .defaultDecoding(from: container, forKey: .property2)
property3 = try .defaultDecoding(from: container, forKey: .property3)
weirdThing = .init(value: "hello world")
}
public func encode(to encoder: Encoder) throws {
var container = encoder.container(keyedBy: CodingKeys.self)
try container.encode(property1, forKey: .property1)
try container.encode(property2, forKey: .property2)
try container.encode(property3, forKey: .property3)
}
}This advanced feature may not ever be useful, but if you find yourself in the situation of dealing with an API that does not 100% follow the SPEC then you might find meta-attributes are just the thing to make your resource objects more natural to work with.
Suppose, for example, you are presented with the unfortunate situation where a piece of information you need is only available as part of the Id of a resource object. Perhaps a user's Id is formatted "{integer}-{createdAt}" where "createdAt" is the unix timestamp when the user account was created. The following UserDescription will expose what you need as an attribute. Realistically, the following example code is still terrible for its error handling. Using a Result type and/or invariants would clean things up substantially.
enum UserDescription: ResourceObjectDescription {
public static var jsonType: String { return "users" }
struct Attributes: JSONAPI.Attributes {
var createdAt: (User) -> Date {
return { user in
let components = user.id.rawValue.split(separator: "-")
guard components.count == 2 else {
assertionFailure()
return Date()
}
let timestamp = TimeInterval(components[1])
guard let date = timestamp.map(Date.init(timeIntervalSince1970:)) else {
assertionFailure()
return Date()
}
return date
}
}
}
typealias Relationships = NoRelationships
}
typealias User = JSONAPI.ResourceObject<UserDescription, NoMetadata, NoLinks, String>Given a value user of the above resource object type, you can access the createdAt attribute just like you would any other:
let createdAt = user[\.createdAt]This works because createdAt is defined in the form: var {name}: ({ResourceObject}) -> {Value} where {ResourceObject} is the JSONAPI.ResourceObject described by the ResourceObjectDescription containing the meta-attribute.
This advanced feature may not ever be useful, but if you find yourself in the situation of dealing with an API that does not 100% follow the SPEC then you might find meta-relationships are just the thing to make your resource objects more natural to work with.
Similarly to Meta-Attributes, Meta-Relationships allow you to represent non-compliant relationships as computed relationship properties. In the following example, a relationship is created from some attributes on the JSON model.
enum UserDescription: ResourceObjectDescription {
public static var jsonType: String { return "users" }
struct Attributes: JSONAPI.Attributes {
let friend_id: Attribute<String>
}
struct Relationships: JSONAPI.Relationships {
public var friend: (User) -> User.Identifier {
return { user in
return User.Identifier(rawValue: user[\.friend_id])
}
}
}
}
typealias User = JSONAPI.ResourceObject<UserDescription, NoMetadata, NoLinks, String>Given a value user of the above resource object type, you can access the friend relationship just like you would any other:
let friendId = user ~> \.friendThis works because friend is defined in the form: var {name}: ({ResourceObject}) -> {Identifier} where {ResourceObject} is the JSONAPI.ResourceObject described by the ResourceObjectDescription containing the meta-relationship.
The following serves as a sort of pseudo-example. It skips server/client implementation details not related to JSON:API but still gives a more complete picture of what an implementation using this framework might look like. You can play with this example code in the Playground provided with this repo.
// We make String a CreatableRawIdType.
var GlobalStringId: Int = 0
extension String: CreatableRawIdType {
public static func unique() -> String {
GlobalStringId += 1
return String(GlobalStringId)
}
}
// We create a typealias given that we do not expect JSON:API Resource
// Objects for this particular API to have Metadata or Links associated
// with them. We also expect them to have String Identifiers.
typealias JSONResourceObject<Description: ResourceObjectDescription> = JSONAPI.ResourceObject<Description, NoMetadata, NoLinks, String>
// Similarly, we create a typealias for unidentified resource objects. JSON:API
// only allows unidentified resource objects (i.e. no "id" field) for client
// requests that create new resource objects. In these situations, the server
// is expected to assign the new resource object a unique ID.
typealias UnidentifiedJSONResourceObject<Description: ResourceObjectDescription> = JSONAPI.ResourceObject<Description, NoMetadata, NoLinks, Unidentified>
// We create typealiases given that we do not expect JSON:API Relationships
// for this particular API to have Metadata or Links associated
// with them.
typealias ToOneRelationship<ResourceObject: Identifiable> = JSONAPI.ToOneRelationship<ResourceObject, NoMetadata, NoLinks>
typealias ToManyRelationship<ResourceObject: Relatable> = JSONAPI.ToManyRelationship<ResourceObject, NoMetadata, NoLinks>
// We create a typealias for a Document given that we do not expect
// JSON:API Documents for this particular API to have Metadata, Links,
// useful Errors, or a JSON:API Object (i.e. APIDescription).
typealias Document<PrimaryResourceBody: JSONAPI.ResourceBody, IncludeType: JSONAPI.Include> = JSONAPI.Document<PrimaryResourceBody, NoMetadata, NoLinks, IncludeType, NoAPIDescription, UnknownJSONAPIError>
// MARK: ResourceObject Definitions
enum AuthorDescription: ResourceObjectDescription {
public static var jsonType: String { return "authors" }
public struct Attributes: JSONAPI.Attributes {
public let name: Attribute<String>
}
public typealias Relationships = NoRelationships
}
typealias Author = JSONResourceObject<AuthorDescription>
enum ArticleDescription: ResourceObjectDescription {
public static var jsonType: String { return "articles" }
public struct Attributes: JSONAPI.Attributes {
public let title: Attribute<String>
public let abstract: Attribute<String>
}
public struct Relationships: JSONAPI.Relationships {
public let author: ToOneRelationship<Author>
}
}
typealias Article = JSONResourceObject<ArticleDescription>
// MARK: Document Definitions
// We create a typealias to represent a document containing one Article
// and including its Author
typealias SingleArticleDocumentWithIncludes = Document<SingleResourceBody<Article>, Include1<Author>>
// ... and a typealias to represent a document containing one Article and
// not including any related resource objects.
typealias SingleArticleDocument = Document<SingleResourceBody<Article>, NoIncludes>// Skipping over all the API and database stuff, here's a chunk of code
// that creates a document. Note that this document is the entirety
// of a JSON:API response body.
func articleDocument(includeAuthor: Bool) -> Either<SingleArticleDocument, SingleArticleDocumentWithIncludes> {
// Let's pretend all of this is coming from a database:
let authorId = Author.Identifier(rawValue: "1234")
let article = Article(id: .init(rawValue: "5678"),
attributes: .init(title: .init(value: "JSON:API in Swift"),
abstract: .init(value: "Not yet written")),
relationships: .init(author: .init(id: authorId)),
meta: .none,
links: .none)
let document = SingleArticleDocument(apiDescription: .none,
body: .init(resourceObject: article),
includes: .none,
meta: .none,
links: .none)
switch includeAuthor {
case false:
return .a(document)
case true:
let author = Author(id: authorId,
attributes: .init(name: .init(value: "Janice Bluff")),
relationships: .none,
meta: .none,
links: .none)
let includes: Includes<SingleArticleDocumentWithIncludes.Include> = .init(values: [.init(author)])
return .b(document.including(.init(values: [.init(author)])))
}
}
let encoder = JSONEncoder()
encoder.keyEncodingStrategy = .convertToSnakeCase
encoder.outputFormatting = .prettyPrinted
let responseBody = articleDocument(includeAuthor: true)
let responseData = try! encoder.encode(responseBody)
// Next step would be encoding and setting as the HTTP body of a response.
// we will just print it out instead:
print("-----")
print(String(data: responseData, encoding: .utf8)!)
// ... and if we had received a request for an article without
// including the author:
let otherResponseBody = articleDocument(includeAuthor: false)
let otherResponseData = try! encoder.encode(otherResponseBody)
print("-----")
print(String(data: otherResponseData, encoding: .utf8)!)enum NetworkError: Swift.Error {
case serverError
case quantityMismatch
}
// Skipping over all the API stuff, here's a chunk of code that will
// decode a document. We will assume we have made a request for a
// single article including the author.
func docode(articleResponseData: Data) throws -> (article: Article, author: Author) {
let decoder = JSONDecoder()
decoder.keyDecodingStrategy = .convertFromSnakeCase
let articleDocument = try decoder.decode(SingleArticleDocumentWithIncludes.self, from: articleResponseData)
switch articleDocument.body {
case .data(let data):
let authors = data.includes[Author.self]
guard authors.count == 1 else {
throw NetworkError.quantityMismatch
}
return (article: data.primary.value, author: authors[0])
case .errors(let errors, meta: _, links: _):
throw NetworkError.serverError
}
}
let response = try! docode(articleResponseData: responseData)
// Next step would be to do something useful with the article and author but we will print them instead.
print("-----")
print(response.article)
print(response.author)The JSONAPI framework is packaged with a test library to help you test your JSONAPI integration. The test library is called JSONAPITesting. It provides literal expressibility for Attribute, ToOneRelationship, and Id in many situations so that you can easily write test ResourceObject values into your unit tests. It also provides a check() function for each ResourceObject type that can be used to catch problems with your JSONAPI structures that are not caught by Swift's type system. You can see the JSONAPITesting in action in the Playground included with the JSONAPI repository.
This library has moved into its own Package. See https://github.com/mattpolzin/JSONAPI-Arbitrary
This library has moved into its own Package. See https://github.com/mattpolzin/JSONAPI-OpenAPI