Fake Relay connections

[IvanGoncharov]

suggested by @5hanth in #2
Need to think how to describe Relay connections in IDL without requiring too much boilerplate.

[soneymathew]

Hi @IvanGoncharov / @5hanth what are your thoughts on how to go about implementing this?
To breakdown the problem I had the following thoughts

1. How do I identify that a type is a connection?
   Approach 1: We could use a directive to mark a field as a connection

type Company {
  name: String @fake(type:companyName)
  employees(
      first: Int,
      after: String,
      last: Int,
      before: String,
 : EmployeeConnection @connection(options:{type: "relay"})
}

Approach 2: Detect if something is a connection using the same technique used by voyager

https://github.com/APIs-guru/graphql-voyager/blob/b2deb19bf8d82e0b496e1ad660823e61b5ce8772/src/introspection/introspection.ts#L135

  if (!/.Connection$/.test(field.type.name)) return;

2. How does the field resolvers know the connection args to determine the length as done in

https://github.com/APIs-guru/graphql-faker/blob/7bce2980dccef21c1d121688cb741bff47ea2a45/src/fake_schema.ts#L180-L182

3. How do we enable a hybrid connection as supported by Github APIs?
   https://developer.github.com/v4/object/searchresultitemconnection/
   tricky bit I think is the presence of both nodes and edges in the result

If we can converge on an approach I can put in some time to help out with this.

Best,
Soney

[timonkbd]

Any progress on this? Faking Relay connections would be super helpful for us! 🙂