The api is stateless. All you need to do is delete the token locally. See also https://auth0.com/docs/logout we don't currently have a way to revoke a token but might add that in the future

@sorenbs: hm, so there's no way to force invalidation of a token?

(For non-auth0)

I'm thinking something like the user can see all active sessions & potentially revoke a session

@thisismissem: not at the moment. We'll ad this in the future

@sorenbs this is something I'm currently having to implement for my company

So far I've just gone with a GenericResponse type, which simply has:

{ success: Boolean! }

As logout doesn't have any other information to communicate, other that success or failure

(I could also go with

type MaybeError { error: String }

but idk how this all fits in graphql right now

@sorenbs do you publish the base schema for graph.cool? (I feel like there's so many people using graphql in production, but so few actually publish their schemas

Interesting. Wouldn’t the introspection query give you all you want to know about the schema? We have 3 schemas - system (for managing your projects) + simple and relay for interacting with your data.

not sure

Like, Github's is pretty brilliant: https://developer.github.com/early-access/graphql/

Given the built in File model in Graphcool should I still use a CDN like Uploadcare? I can think of a few advantages like the fact that the widget will cut out a good deal of coding.

Hi @brad.barnes! Yes, we’re using Cloudfront as a CDN with edge nodes all around the globe.

hello guys

I'm having trouble finding documentation on appending to a list field could anybody point me in the right direction? I am afraid the normal updateModel(.. will overwrite the array, Is this the case?

Hey @brad.barnes, yes array type values are always replaced as a whole. If you want to append/remove to a list, you should try to use a relation instead 🙂

Welcome @nikoloza and @aparedes 😄

@thisismissem, just like @sorenbs mentioned, you can do an introspection query and get the entire schema (it’s how GraphiQL does it)

Hey @xpepermint - welcome!

hey, hey 🙂

I understand you spoke with Nilan about contributing to the Vue track for Learn Apollo. I think that would be really really cool! A lot of people are excited about Vue and GraphQL together and Vue is kind of a blind spot for me 🙂

hehe… sure, I’ll do my best 🙂 - I’ll take some time for this next week ...

I am working on query permissions today. I am planning to make a page where admin users can create other user accounts manually instead of allowing open sign up. I made a create node permission for the User model (authenticated) with this rule.

{
  user(id:$userId) {
    roles(filter: {name: "admin"}) {
      id
    }
  }
}

When I log in as a user with the admin role, I cannot create a user. I get the message "It is not possible to create a user when you are already signed in." Is it possible to work around this?

we haven't considered this scenario, do you mind creating an issue here http://github.com/graphcool/console/issues?

Sure. Here you go. https://github.com/graphcool/console/issues/578

thanks!