Adds Fieldsthunk to ObjectConfig.

[chris-ramon]

Details.

• Updates ObjectConfig.Fields to be an interface, so now possibles can be:
  • graphql.Fields & graphql.FieldsThunk
• Built in top of great work from @pyros2097 on Add FieldsThunk #96 👍

Note:
I've removed extra code within Object.Fields() since graphql.defineFieldMap() does handle it and is being covered with:
TestTypeSystem_ObjectsMustHaveFields_RejectsAnObjectTypeWithMissingFields

cc/ @pyros2097

[pyrossh]

Great @chris-ramon I guess coverage has to be improved but other than that I guess we are going to reach the goal of an alpha release soon.

[chris-ramon]

@pyros2097 - I might be missing something, do we really should rely only on .Name to say, those are the same types?

[pyrossh]

I guess its not absolutely necessary but since every type has to have a unique name this should also hold valid true. It's very useful in because say we have a type ex:
type Quiz struct {} which I use internally I want to be able to send some of its data back to client without creating a new struct so we use a map[string]interface{} and map out the fields we want to send back but the problem arises when using relay.

When we are using nodeDefinition's it doesn't know it is a quiz type but is map[string]interface{}so for this we use the type name like this
Ofcourse we can use any other field but this is easier to reason and it adds some sort of dynamic behavoir to the strong go type struct type system.

MutateAndGetPayload(params graphql.Params) (interface{}, error) {
  return map[string]interface{}{
    "__typename": "Quiz",
    "id": "quiz1",
  }
}

//and in our nodeDefinitions we resolve the type like this
NodeDefinitions = relay.NewNodeDefinitions(relay.NodeDefinitionsConfig{
    IDFetcher: func(id string, info graphql.ResolveInfo) interface{} {
        resolve := relay.FromGlobalID(id)
        switch resolve.Type {
        case "Quiz":
            return map[string]interface{}{
                "__typename": "Quiz",
                "id": "some_id",
            }
            }
    }
  },
            }
  TypeResolve: func(value interface{}, info graphql.ResolveInfo) *graphql.Object {
        switch data := value.(type) {
        case map[string]interface{}:
            switch data["__typename"] {
            case "Quiz":
                return QuizType
            }
        }
    }
})

This helps us in not creating to many structs for a single graphql Type.

[chris-ramon]

Thanks for clarification @pyros2097 - let's keep this since you've provide a handy use case.

[andrewscarani]

@chris-ramon @pyros2097 Any working examples (preferably working test cases) of recursive input types using InputObjectConfigFieldMapThunk?