Matt Krick

By putting the loader inside the `client.js`, we're sending all the schema creation logic to the client, which is not necessary. Furthermore, the only reason stuff like `introspectionQuery` is needed...

Cashay v2

18

#149 gets us half way to a new mutations API, so let's dive in how that might change. I like Relay 2's direction of imperatively mutating the normalized store. I...

create cashay-server for realtime updates

2

The problem is not everyone uses RethinkDB for reactivity & even if they do, they're more or less limited to single-table subscriptions. This makes sense, since it can get pretty...

remove id from the @cached directive

3

the `id, ids` fields are pretty useless & can use a pre-cached value causing source.id to come up undefined. It's not terrible, but it causes an extra render. Plus this...

Support TTL on a per-field basis

1

Every prop on the server GraphQL schema should be given a `__ttl` field that is automatically requested by cashay. When received by the client, an `expiresAt` field is generated on...

let's say you have a bunch of agenda items 1. mow the lawn 2. eat 3. ??? 4. profit The URL looks like this `/agenda/2` Since we're on page 2,...

Persisted documentId

1

Instead of sending a query, the query string should be stored on the server and we tell it what parts we want. Since the AST is a tree and it's...

The mutation API should be more functional. We can make it more reduxy by providing an `optimistic` and `response` callback. Additionally, a general problem with cashay-- when i accept an...

Linting

3

Add eslint to the repo & get it cleaned up

performance is already pretty dang good. BUT, if we make a react-cashay wrapper, we could encapsulate redux so we don't even call cashay unless a cashay action is called, essentially,...