graphql: Haskell GraphQL implementation

[ language, library ] [ Propose Tags ]
Versions [RSS] 0.1, 0.2, 0.2.1, 0.3, 0.4.0.0, 0.5.0.0, 0.5.0.1, 0.5.1.0, 0.6.0.0, 0.6.1.0, 0.7.0.0, 0.8.0.0, 0.9.0.0, 0.10.0.0, 0.11.0.0, 0.11.1.0, 1.0.0.0, 1.0.1.0, 1.0.2.0, 1.0.3.0, 1.1.0.0, 1.2.0.0, 1.2.0.1, 1.2.0.2, 1.2.0.3 (info)
Change log CHANGELOG.md
Dependencies aeson (>=1.4.7.1 && <1.5), base (>=4.7 && <5), conduit (>=1.3.2 && <1.4), containers (>=0.6.2.1 && <0.7), exceptions (>=0.10.4 && <0.11), hspec-expectations (>=0.8.2 && <0.9), megaparsec (>=8.0.0 && <8.1), parser-combinators (>=1.2.1 && <1.3), scientific (>=0.3.6.2 && <0.4), text (>=1.2.4.0 && <1.3), transformers (>=0.5.6.2 && <0.6), unordered-containers (>=0.2.10.0 && <0.3) [details]
License BSD-3-Clause
Copyright (c) 2019-2020 Eugen Wissner, (c) 2015-2017 J. Daniel Navarro
Author Danny Navarro <j@dannynavarro.net>, Matthías Páll Gissurarson <mpg@mpg.is>, Sólrún Halla Einarsdóttir <she@mpg.is>
Maintainer belka@caraus.de
Category Language
Home page https://github.com/caraus-ecms/graphql#readme
Bug tracker https://github.com/caraus-ecms/graphql/issues
Source repo head: git clone https://github.com/caraus-ecms/graphql
Uploaded by belka at 2020-08-29T16:51:59Z
Distributions LTSHaskell:1.2.0.3, NixOS:1.2.0.3, Stackage:1.2.0.3
Reverse Dependencies 4 direct, 0 indirect [details]
Downloads 8157 total (71 in the last 30 days)
Rating 2.25 (votes: 2) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs available [build log]
Last success reported on 2020-08-29 [all 1 reports]

Readme for graphql-0.10.0.0

[back to package description]

GraphQL implementation in Haskell

Hackage Version Build Status License Simple Haskell

This implementation is relatively low-level by design, it doesn't provide any mappings between the GraphQL types and Haskell's type system and avoids compile-time magic. It focuses on flexibility instead, so other solutions can be built on top of it.

State of the work

For now this library provides:

  • Parser for the query and schema languages, as well as a printer for the query language (minimizer and pretty-printer).
  • Data structures to define a type system.
  • Executor (queries, mutations and subscriptions are supported).
  • Validation is work in progress.
  • Introspection isn't available yet.

But the idea is to be a Haskell port of graphql-js.

For a more precise list of currently missing features see issues marked as "not implemented".

Documentation

API documentation is available through Hackage.

You'll also find a small tutorial with some examples under docs/tutorial.

Getting started

We start with a simple GraphQL API that provides us with some famous and less famous cites.

"""
Root Query type.
"""
type Query {
  """
  Provides a cite.
  """
  cite: String!
}

This is called a GraphQL schema, it defines all queries supported by the API. Query is the root query type. Every GraphQL API should define a query type.

Query has a single field cite that returns a String. The ! after the type denotes that the returned value cannot be Null. GraphQL fields are nullable by default.

To be able to work with this schema, we are going to implement it in Haskell.

{-# LANGUAGE OverloadedStrings #-}

import Control.Exception (SomeException)
import qualified Data.Aeson as Aeson
import qualified Data.ByteString.Lazy.Char8 as ByteString.Lazy.Char8
import qualified Data.HashMap.Strict as HashMap
import Language.GraphQL
import Language.GraphQL.Type
import qualified Language.GraphQL.Type.Out as Out

-- GraphQL supports 3 kinds of operations: queries, mutations and subscriptions.
-- Our first schema supports only queries.
schema :: Schema IO
schema = Schema
    { query = queryType, mutation = Nothing, subscription = Nothing }

-- GraphQL distinguishes between input and output types. Input types are field
-- argument types and they are defined in Language.GraphQL.Type.In. Output types
-- are result types, they are defined in Language.GraphQL.Type.Out. Root types
-- are always object types.
--
-- Here we define a type "Query". The second argument is an optional
-- description, the third one is the list of interfaces implemented by the
-- object type. The last argument is a field map. Keys are field names, values
-- are field definitions and resolvers. Resolvers are the functions, where the
-- actual logic lives, they return values for the respective fields.
queryType :: Out.ObjectType IO
queryType = Out.ObjectType "Query" (Just "Root Query type.") []
    $ HashMap.singleton "cite" citeResolver
  where
    -- 'ValueResolver' is a 'Resolver' data constructor, it combines a field
    -- definition with its resolver function. This function resolves a value for
    -- a field (as opposed to the 'EventStreamResolver' used by subscriptions).
    -- Our resolver just returns a constant value.
    citeResolver = ValueResolver citeField
        $ pure "Piscis primum a capite foetat"
    -- The first argument is an optional field description. The second one is
    -- the field type and the third one is for arguments (we have none in this
    -- example).
    --
    -- GraphQL has named and wrapping types. String is a scalar, named type.
    -- Named types are nullable by default. To make our "cite" field
    -- non-nullable, we wrap it in the wrapping type, Non-Null.
    citeField = Out.Field
        (Just "Provides a cite.") (Out.NonNullScalarType string) HashMap.empty

-- Now we can execute a query. Since our schema defines only one field,
-- everything we can do is to ask to resolve it and give back the result.
-- Since subscriptions don't return plain values, the 'graphql' function returns
-- an 'Either'. 'Left' is for subscriptions, 'Right' is for queries and
-- mutations.
main :: IO ()
main = do
    Right result <- graphql schema "{ cite }"
    ByteString.Lazy.Char8.putStrLn $ Aeson.encode result

Executing this query produces the following JSON:

{
  "data": {
    "cite": "Piscis primum a capite foetat"
  }
}

Further information

Contact

Suggestions, contributions and bug reports are welcome.

Should you have questions on usage, please open an issue and ask – this helps to write useful documentation.

Feel free to contact on Slack in #haskell on GraphQL. You can obtain an invitation here.