Does anyone know how I would go about versioning a specific resource? For example, say I was re-writing Facebook. How would I go about using GraphQL/Graphcool to version a Post? (That a User can access the latest version on but also access previous versions of that same Post.)

Hello.

I'm having trouble with a resolver, which gives me absolutely nothing about the error that occurs.

The only thing I get is a request id, which leads me nowhere.

Somebody?

hey all, any idea why when signing out and signing in as another user keeps the data of the previous user cached with Apollo?

I’ve tried using client.resetStore but that doesn’t seem to do as expected

yeah confirmed, when trying to sign in and receiving a new token, the previously signed in user’s data is still cached

interesting, now when I use emailpassword signin and looking at my apollo store, there are two user accounts on there

Apollo has been notoriously stubborn with regards to resetStore

resetStore

does not necessarily remove any data from your store. Instead, it just calls refetch on all active queries, causing the cache to be refreshed.

However, after logout, all queries that require authentication will actually fail, which sucks.

originally i was querying for the logged in user by id

So, you could decide to call

resetStore

after login instead of logout, because then you at least have authentication, and all of your queries should actually return data. But that does leave the data cached after logout, so you need another method to make sure no data gets exposed.

yeah that’s what I understand now too @agartha from what i’ve been reading

thanks for the response

is there still a loggedInUser query?

I was trying to use that per the graphcool docs, but

Error: GraphQL error: Cannot query field 'loggedInUser' on type 'Query'.

Where does it say that in the docs?

If you use the

User

type, the

user

query is still available

If you use any other Type for your users, you have to add your own resolver function, that's what the

loggedInUser

refers to

If you check after step 21, you'll see that

loggedInUser

is part of the

email-password

template

But afaik,

user

is also still available

can you elaborate what you mean by user is still availble?

as of recent I was querying on user and passing in the user’s id to retrieve the current user

the id was retrieved via localStorage

@agartha I got it!

thank you

Anyone do end to ending testing? Curious to know what your setup is.