I spent an hour chasing down the cause of transition framerate jank in a VueJS app at the weekend — it turned out it was caused by Graphcool consistently responding too quickly to queries, and triggering DOM updates midway through the transition 😄

As problems go, <50ms responses to queries is a nice one to have

Is something up with Graphcool? Can’t access the console.

Me too I get this error:

@merott @jvbianchi Issue seems to be resolved (at least, everything is working here). Can you confirm?

yes It has been resolved for me

Is there any good way to ‘transfer’ the functions (both subscription and pipeline) from one project to another? Or I have to simply copy everything across?

Does anyone understand what

gc-pat

is supposed to be in this tutorial for using graph.cool with Stripe? https://www.graph.cool/docs/tutorials/stripe-payments-with-mutation-callbacks-using-micro-and-now-soiyaquah7/

Additionally, this is unclear:

>> To protect our microservices from unauthorized access, let’s generate two secret passphrases, we’ll use length 32 here. Let’s call them

create-secret

and

charge-secret

.

As much as I would love to endlessly scroll through all of these messages, does anyone know if Stripe will be an integration in the future?

Any plans to support node 8 for graphcool functions? If so is there a timeline?

Is there any reason not to use subscriptions? It seems to offload the live-update process from apollo and onto the queries themselves, which appears much easier

@amann currently you can't do that I think. I've tried but it just didn't work. I think they are working on updating the version soon

@zaksingh check out this thread

If I do this.

mutation updateReport($reportId: ID!, $logs: [ID!]){
    updateReport(
      id: $reportId
      logsIds: $logs
      userId: $userId
    ), {
      id
    	logs{
        id
        startedAtOdometerReading
      }
    }
  }

I get insufficient permissions, but if I add

logs: {
        userId: $userId
      }

after userId it creates a new log instead of updating the logs on this report

Any suggestions?

Oheyo! Does anyone know if there is a limit on the number of Graph.cool Types you can have?

If I want to be able to associate a certain Type with any other Type is there a way to make a global

@relation

?

Like say I have a Comments Type that I want to put on Pages, Posts, Videos, and Products

Do I have to create a separate relation for each?

Is that what Interfaces are for?

Hi, I have been playing with the beta cli and it's really awesome ! While reading the

next

docs, in here https://docs-next.graph.cool/reference/database/overview-viuf8uus7o I read

Graphcool uses a SQL database under the hood. In the hosted version of Graphcool, every project comes with an instance of AWS Aurora. In the self-hosted version, it's possible to plug in other databases like MySQL.

Is it possible to self host graphcool ???

Hey guys, anybody has recent experience with subscriptions? It seems that

addGraphQLSubscriptions

is no longer part of the

subscriptions-transport-ws

package, and all the examples reference it (https://blog.graph.cool/how-to-build-a-real-time-chat-with-graphql-subscriptions-and-apollo-d4004369b0d4)

Nevermind, I think I've found the answer: https://www.graph.cool/forum/t/typeerror-during-the-subcriptions-part-of-the-howtographql-tutorial-on-addgraphqlsubscriptions/934

As Apollo in version 0.9 deprecates addGraphQLSubscriptions in favor of Apollo Link (https://dev-blog.apollodata.com/apollo-link-the-modular-graphql-network-stack-3b6d5fcf9244) the solution was to use the old version (0.8.3) of the

subscriptions-transport-ws

package. Is Apollo Link currently supported by graph.cool, or are some changes necessary to support it?

@tomaash If you follow the link in this comment: https://github.com/graphcool/content/issues/292#issuecomment-331789499 It will show you the basic implementation using Apollo Link.