graphcool local up

The component-based approach of React Router v4 does not readily allow for aggregating the data requirements for nested routes, and as such does not readily permit an approach that will avoid request waterfalls from nesting QueryRenderer components.

graphcool-lib

type Roles {
  id: String!
  roles: [String]
}

extend type Query {
  roles(id: String): Roles
}

module.exports = function(event) {
  const id = event.data.id

  const roles = ["somerole"]

  return {
    data: {
      id: id,
      roles: roles}}
}

graphcool local up

query readNotification($user_id: ID) {
  SomeNotificationExists(filter: {AND: [{sender: {id_not: $user_id}}, {receiver: {id: $user_id}}]})
}