Skip to content

Latest commit

 

History

History

quell-client

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 
 
 
 
 
 
 

@quell/client

@quell/client is an easy-to-implement JavaScript library providing a client-side caching solution for GraphQL. Quell's schema-governed, type-level normalization algorithm caches GraphQL query responses as flattened key-value representations of the graph's nodes, making it possible to partially satisfy queries from the browser's sessionStorage, reformulate the query, and then fetch additional data from other APIs or databases.

@quell/client is an open-source NPM package accelerated by OS Labs and developed by Robleh Farah, Angela Franco, Ken Litton, Thomas Reeder, Andrei Cabrera, Dasha Kondratenko, Derek Sirola, Xiao Yu Omeara, Nick Kruckenberg, Mike Lauri, Rob Nobile and Justin Jaeger.

Installation

Download @quell/client from npm in your terminal with npm i @quell/client. @quell/client will be added as a dependency to your package.json file.

Implementation

Let's take a look at a typical use case for @quell/client by re-writing a fetch request to a GraphQL endpoint.

Sample code of fetch request without Quell:

const sampleQuery = `query {
    countries {
        id
        name
        cities {
            id
            name
            population
        }
    }
}`

function fetchMe(sampleQuery) {
    let results;
    fetch('/graphQL', {
        method: "POST",
        body: JSON.stringify(sampleQuery)
    })
    .then(res => res.json())
    .then(parsedRes => {
      // use parsed results
     });

fetchMe(sampleQuery)

To make that same request with Quell:

  1. Import Quell with import Quell from '@quell/client'
  2. Instead of calling fetchMe(query), replace with Quell(endpoint, query, map)
  • The Quell method takes in four parameters
    1. endpoint - your GraphQL endpoint as a string (ex. '/graphQL')
    2. query - your GraphQL query as a string (ex. see sampleQuery, above)
    3. map - an object that maps named queries to the user-defined GraphQL types they return
    const sampleMap = {
      countries: 'Country',
      country: 'Country',
      citiesByCountryId: 'City',
      cities: 'City',
    }
    
    

Using the example snippets above, your Quell-powered GraphQL fetch would look like this:

Quell('/graphQL', sampleQuery, sampleMap)
  .then( // use parsed response);

Note: Quell will return a promise that resolves into a JS object containing your data in the same form as a typical GraphQL response { data: // response }

That's it! You're now caching your GraphQL queries in the browser's sessionStorage.

Usage Notes

  • If you want to specify the headers sent on your GraphQL request, pass in an additional object to Quell like so:
const headersObject = {
  'Content-Type': 'application/json',
};

Quell('/graphQL', sampleQuery, sampleMap, { headers: headersObject })
  .then( // use parsed response);
  • @quell/client can only cache items it can uniquely identify. It will will look for fields called id, _id, Id, or ID on the response. If a query lacks all four, it will execute the query without caching the response.

  • Currently, Quell can only cache query-type requests without variables or directives. Quell will still process these requests but will not cache the responses.

For information on @quell/server, please visit the corresponding README file.