Closed teh closed 7 years ago
What exactly do you mean by "support input objects"? To the extent that we run fromValue
on data received from users, we already do this.
Also, "input objects" is a technical term in GraphQL, referring to a restricted type of Object suitable for input.
The link is exactly what I mean. I'm not sure where we read input objects? Do we have a generic class already? Can't see it in the code.
Discussed IRL: There will be no extra metadata other than the data that can be derived generically.
This is implemented though the API probably isn't final (see #73)
Just to be clear for googlers and to save having to click elsewhere: GraphQL specifies two types of Objects
.
GraphQLObjectType
GraphQLInputObjectType
At first glance, the two types might seem redundant. But, it turns out there is value in having a distinction between your inputs and outputs for the same object.
We have several constraints:
Map Text Value
.Object name i f
and aderive Generic
record.Object name i f
and aderive Generic
record.Would be nice but not necessary:
Object n i f
to define input objects as well.I think 1 in particular points to a
derive Generic
style input. We could add that toFromValue
.