GraphQLicious is a swift component that provides an intuitive and convenient way to build GraphQL queries and convert them easily to String representations.
[![iOS 8] (https://img.shields.io/badge/iOS%208%2B%20%7C%20MacOS%20X%2B%20%7C%20TV%20OS%20%7C%20Watch%20OS%202%2B-Compatible-brightgreen.svg)] ()
GraphQLicious
supports Carthage. To install it, simply add the following line to your Cartfile
github "WeltN24/GraphQLicious"
GraphQLicious
is available through CocoaPods. To install it, simply add the following line to your Podfile
pod "GraphQLicious"
If you don't use CocoaPods, you can still add GraphQLicious
as a submodule, drag and drop GraphQLicious.xcodeproj
into your project, and embed GraphQLicious.framework
in your target.
- Drag
GraphQLicious.xcodeproj
to your project - Select your app target
- Click the + button on the Embedded binaries section
- Add
GraphQLicious.framework
You can directly drag and drop the needed files into your project, but keep in mind that this way you won't be able to automatically get all the latest features.
The files are contained in the Sources
folder and work for the iOS
framework
Let's assume, we have the id of an article and we want to have the headline
, body
text and opener image
of that article.
Our graphQL query for that will look like this:
query {
test: content(id: 153082687){
...contentFields
}
}
fragment contentFields on Content {
headline,
body,
image(role: "opener", enum: [this, that]){
...imageContent
}
}
fragment imageContent on Image {
id
url
}
fragment urlFragment on Image {
url (ratio: 1, size: 200)
}
First, let's create a Fragment
to fetch the contents of an image, namely the image id
and the image url
let imageContent = Fragment(
withAlias: "imageContent",
name: "Image",
fields: [
"id",
"url"
]
)
Next, let's embed the Fragment
into a Request
that gets the opener image.
Note: Argument
values that are of type String
are automatically represented with quotes.
GraphQL also gives us the possibility to have custom enums as argument values. All you have to do is letting your enum implement ArgumentValue
and you're good to go.
enum customEnum: String, ArgumentValue {
case This = "this"
case That = "that"
private var asGraphQLArgument: String {
return rawValue // without quotes
}
}
let customEnumArgument = Argument(
key: "enum",
values: [
customEnum.This,
customEnum.That
]
)
let imageContentRequest = Request(
name: "image",
arguments: [
Argument(key: "role", value: "opener"),
customEnumArgument
],
fields: [
imageContent
]
)
So now we have a Request with an embedded Fragment. Let's go one step further.
If we want to, we can imbed that Request into another Fragment. (We can also embed Fragments into Fragments)
Additionally to the opener image with its id and url we also want the headline
and body
text of the article.
let articleContent = Fragment(
withAlias: "contentFields",
name: "Content",
fields: [
"headline",
"body",
imageContentRequest
]
)
Finally, we put everything together as a Query
. A Query always has a top level Request to get everything started, and requires all the Fragments that are used inside.
let query = Query(request: Request(
withAlias: "test",
name: "content",
arguments: [
Argument(key: "id", values: [153082687])
],
fields: [
articleContent
]),
fragments: [articleContent, imageContent]
)
All we have to do now is to call create()
on our Query and we're good to go.
print(query.create())
Let's assume, we want to change our username and our age in our backend and we want to have the new name and age back to make sure everything went right.
Let's assume further, our server provides a mutating method editMe
for exactly that purpose.
Our graphQL query for that will look like this:
mutation myMutation {
editMe(
name: "joe",
age: 99
)
{
name,
age
}
}
Let us first create the actual mutating function. We can use a Request
for that. As Argument
values
we give information about which fields should be changed and what's the actual change
let mutatingRequest = Request(
name: "editMe",
arguments: [
Argument(name: "name", value: "joe"),
Argument(name: "age", value: 99)
],
fields: [
"name",
"age"
]
)
Finally, we put everything together as a Mutation
.
Mutation
s work just like Queries
let mutation = Mutation(
withAlias: "myMutation",
mutatingRequest: mutatingRequest
)
After we've done that we can create the request.
print(mutation.create())
ReadingRequest
is now simplyRequest
MutatingRequest
has been removed, you can useRequest
insteadMutatingArgument
has been removed, you can useArgument
insteadMutatingValue
andMutatingField
have been removed, you can useArgument
, orObjectValue
andObjectKeyValuePair
instead
GraphQLicious
was made in-house by WeltN24
Felix Dietz, [email protected], @podboq (@joemcbomb) on Github, @joemcbomb on Twitter
Vittorio Monaco, [email protected], @vittoriom on Github, @Vittorio_Monaco on Twitter
GraphQLicious
is available under the MIT license. See the LICENSE files for more info.