and isUser() and state.isUser is

false

, but when I try to createUser, graph.cool says user with details already exists, and I've verified that in the console

Is there a suitable way to do optimistic locking with GraphCool? (e.g. fail an update if a

version

field does not match). From what I can see the

update...

mutations only update by id.

is there a way to delete all of some data?

Just wanted to retry asking this:

How do I run an introspection query against a GraphQL endpoint? Trying to use this awesome visualization tool: https://apis.guru/graphql-voyager/

Is it some type of root query that returns all my nodes and fields?

@doug_w in the Graphcool console switch to Schema and click on "Graph View" button in top right corner ... you get something very similar, probably not that fancy, but works 🙂

Thanks @Daniel K. funny enough I noticed that right after I posted! It’s pretty neat - curious to get the voyager working though if anyone else has tried it.

@doug_w this might perhaps help you ? did not dive into it 🙂 https://www.graph.cool/docs/faq/graphql-introspection-queries-shoe5xailo/

@doug_w When you run graphql-voyager, the initial screen has an option 'copy introspection query'. You paste that query into the playground, run it, and copy-paste the query results back into the box below.

@doug_w commented on @agartha’s file : Soo awesome, thanks!

Has anyone manages to successfully make a GraphCool query to create a new Auth0 authenticated user?

Is anyone else not getting activity to show up on their pipeline function invocation graph/logs?

Is it possible yet to define our infrastructure in code? Cloning environments and keeping them up to date is getting to be a LOT of work

we can't login into the graph.cool console

Hi, I'm having an issue accessing one of my project's console

I can access other projects though

@florian same issue here just now

hi!

i'm having problems with serverless typescript plugin

i'm just integrating the plugin in a legacy project

and when i run serverless offline it shows: Unexpected token ...

node4.3 is the issue

spread operator

it's impossible to use typescript with node4.3 ?

well.. with this plugin

To everyone using the built-in Auth0 integration: Auth0 has now officially announced that for new clients, OIDC conformance will be enabled by default. In order for the built-in Auth0 integration to work, you need to disable this setting in your Auth0 dashboard, as well as setting the Signature Algorithm to

HS256

. Also, if you're using the new

react-native-auth0

client library, make sure you do not specify an audience, because that will override your Auth0 client settings, and switch to OIDC conformant RS256 tokens, which cannot be used for Graphcool!

@agartha pinned ’s Image to this channel.