Given the opaque nature of JSON data the following could work nicely as an alternative allowing effective introspection.
type Lead {
...
data: LeadData
}
/** | |
* Cache hits should cascade from top to bottom returning from the the first match | |
* all the way down to the last and merging results along the way. | |
* | |
* eg. query { | |
* user { | |
* name | |
* } | |
* } |
- agentAdId: UUID!
+ agentAd: AgentAd!
The data field should ideally be part of the schema definition rather than JSON scalar. A JSON scalar doesn't allow us to know what we're querying for and is undocumented, so we can't develop against it.
Subscription
is a reserved word in GraphQL.
Verifying that +imranolas is my blockchain ID. https://onename.com/imranolas |
I hereby claim:
To claim this, I am signing this object:
I, Imran Sulemanji, have read and do accept the MuleSoft Contributor Agreement | |
at http://www.mulesoft.org/legal/contributor-agreement.html | |
Accepted on Wed Aug 13 2014 09:13:36 GMT+0100 (BST) |