Open tislars opened 2 years ago
The problem is here overfetching vs underfetching. I'm not yet sure how we solve this issue, best would be to make every field configurable like it is done in pages via properties
and optimize the query based on the request fields.
At current state it is still valid that you overwrite
the contact_selection
resolver and use your own query and serialization to get the data you want.
What I expected Added a
contact_selection
block to a Article so I can use the output like first name, last name & their organization. However, the organization isn't shown in the response.Potential cause The
partialContact
group is being used in the ContactSelectionResolver whereas thefullContact
will indeed return the hash of the Account in the output.