I'm pretty sure `query { user { ... } }` will alw...
# prisma-whats-new
d
I'm pretty sure
query { user { ... }  }
will always be the authed user
m
That's what I had initially thought... I got the following error: Network error: Error writing result to store for query
d
That's all it says?
m
export const allFundsQueryV3 = gql` query { user { accessGroups { fund { id name managementCompany { id name } vintage fundNumber currency fundSize strategy region fundQuarterlyMetrics (last: 1, orderBy: asAtDate_ASC) { netIRR tvpi rvpi dpi asAtDate cumulativeCalled cumulativeDistributed limitedPartnersNAV } } } } } `;
that's my query so I thought it would work...
d
Have you tried opening all your permissions and seeing if that's the issue?
m
second part of error message: /nStore error: the application attempted to write an object with no provided id but the store already contains an id of User:XXXXX for this object
So it feels like it might be trying to write something to the store which is weird.
when I take off all my permissioning (other than the authentication requirement) i get the same error
d
Yep that's odd
Hopefully someone from Graph.cool can jump in and see what's up. Did you get a Request ID they can use for reference?
m
the query works fine in the playground when I select the same user...
what is a request ID? Where do I get that from?
d
I usually see it in the console but if you didn't get one with the error then I don't know.
Are you using
react-apollo
?
m
yeah - you gave me an idea. I checked the response under Chrome's network tools and graphcool is sending back the expected response. it must be an error with react-apollo
and the local store
d
oh cool, let me know how that goes
m
thanks for your help danny
d
Any time
m
I found the solution! I had to add id on the user in the response so react-apollo could store it properly 😉
d
Ah cool good to know