Feature/facebook

[clayallsopp]

Starting work on a Facebook implementation; fixes #9

[clayallsopp]

Hey @leebyron & @schrockn - any thoughts on this line of thinking? (wrapping the public Graph API into GraphQL)

Current schema looks like this, trying to be compatible with Relay where possible:

type FacebookAPI {
  viewer: FacebookUser
  node(id: ID!): Node
}

type FacebookPage implements Node, FacebookProfile {
  id: ID!
  metadataType: String!
  likes: Int
}

type FacebookPageConnection {
  pageInfo: PageInfo!
  edges: [FacebookPageEdge]
}

type FacebookPageEdge {
  node: FacebookPage
  cursor: String!
}

interface FacebookProfile {
  id: ID!
  metadataType: String!
}

type FacebookUser implements Node, FacebookProfile {
  id: ID!
  metadataType: String!
  name: String
  likes(after: String, first: Int, before: String, last: Int): FacebookPageConnection
}

interface Node {
  id: ID!
}

type PageInfo {
  hasNextPage: Boolean!
  hasPreviousPage: Boolean!
  startCursor: String
  endCursor: String
}

I think I can autogenerate lots of the fields and edges using the Graph API metadata, but things like cursors don't behave exactly the same (I.e. there seem to only be cursors per page, not per item)

[clayallsopp]

@leebyron any advice or examples on a better way to do this? I want to pass in the API token once at some top-level field, and then ensure all subsequent API calls can access it