Decide how to create a wrapper for the graphql api #1
Description
I don't know how to provide a smooth library design and still keep the advantages of graphql. For example, graphql enables to select the fields the client is interested in the response to save bandwidth. However, which fields are needed is application specific and can't be covered by the library. Basically we can't provide response types.
The idea is to use this graphql client library. A option is to provide input types, scalar types. The biggest question is how to abstract the crypto part.