How to create a mutation after being authorized? https://www.graph.cool/forum/t/permission-insufficient-permissions-for-this-mutation-code-3008/1939

Anyone working with µ-services or working on breaking up huge schemas into more manageable pieces, GrAMPS 1.0 is live! https://twitter.com/jlengstorf/status/943198813849882626 If you have any questions, the Graphcool team was nice enough to set up an official support channel in this Slack, so hit up #gramps.

<!here> check out GrAMPS, it's not only an amazing name but a great tool as well! 💯

@nilan Is there an example connecting Authentication + simple CRUD?

My apologies if this is a redundant question but why do we need two schema.graphql files in the new graphcool api?

"code": 3032, "message": "The field 'author' on type 'Post' is required. Performing this mutation would violate the constraint" 
 Does the author fill in the field automatically, after add new Header Authorization Bearer …?

@illuday commented on @playra’s file : Nop, if you want to do this automatically you need to make a custom resolver.

js
async writePost(parent, { title, text }, ctx, info) {
    const authorId = getUserId(ctx)
    return ctx.db.mutation.createPost(
      {
        data: {
          title,
          text,
          isPublished: true,
          author: {
            connect: { id: authorId },
          },
        },
      },
      info,
    )
  }

You should try the basic project from the @beta release.

Is there a way to alter your data model via graphql itself? I.e. a mutation that adds a field to a type that you've defined?

whats the status for cascading deletions? docs still say not available yet

Can be Tipe a possible future competitor of Graphcool? Who knows... https://tipe.io/

Hi there, I think I found a bug. When I use

graphql get-schema -e default

, and my schema has comments/docs, then the generated schema is malformed. Or am I doing something wrong?

Here's the issue for the

get-schema

malformed output: https://github.com/graphql-cli/graphql-cli/issues/70

Hi, I am having proxy issues in local environment, is there way I can bring up multiple locals with my own docker-compose which specifies the proxy

Hi All, Anybody knows why the export feature is gone from the console?

Does anyone have a practical suggestion for how to work with

@migrationValue

in your

types.graphql

as you move from dev to production? In dev it resets the values in my database everytime I run

gc deploy

. Are you just putting up with that and then remembering to remove them all after your first production deploy?

Hello everyone, can anyone help me on how I can connect my frontend with the backend ?

When I set up the advanced Node js boilerplate, I noticed I have a type User defined in both my application schema as well as my datamodel. However, the Post type is only defined in the database schema. Can somebody explain to me why the User type is defined twice?

the

Post

type is imported from the database schema so it doesn’t have to be redefined (https://github.com/graphql-boilerplates/node-graphql-server/blob/master/advanced/src/schema.graphql#L1). the

User

type is “redefined” by without the

password

field to not expose it through the API

graph.cool returns max 1000 items in array in one response?

@nikolasburk Thank you! I understand now. Quick other question, can I already use interfaces in my application schema?

Also, after initalizing the boilerplate, what files do I have to change and which ones get updated automatically?

Hello guys

it's a pleasure to be here

nice to have you with us @kdieubenit 💚

🙂

i needs help guys, how can i create a Graphcool account ?

Hi All, We're developing microservices platform based in CQRS and Event Sourcing principals. The idea is very simple: - we have set of low level services hosted on Kafka Bus and perform streams processing (join, aggregation, etc) - we have set of mid level services that uses stream processing results and provide access to it by exposing REST API - we have high level frontend applications that uses above-mentioned REST API We faced the problem that developers needs to be in the known how Kafka works while implementing new features in frontend and/or REST services. We have an idea to decouple frontend (mid/high level) and backend (low level). To solve that we'd like to: - sink stream processing results into Mysql databases to have so called "read model" for quering - have one separate microservice for data mutations in Kafka (which are asynchronously reflected in mysql read model state). On top of that we'd like to have framework to: - easily spawn new high level microservices - add read models in runtime to make them available for high level microservices - allow high level microservices to make queries across different read models So the question: is GraphCool the right solution to that? If no: what backend framework would you suggest? Thanks in advance!

Hello all, Any suggestions / best practices for item deletion mutations? The simplest way is probably to just create separate mutations for creating, deleting, etc. I would like to keep everything (if it’s feasible) in the one update mutation that I have that sends the input to the backend which updates the columns of the particular row in the database. The issue I’m running into is how do I tell the backend to delete the item from this update mutation. I’m using Elm on the front-end which doesn’t differentiate between

null

and

undefined

so I can’t just set the property of the item I want to delete to say

null

. What do you guys thing about passing an array of items to delete along with whatever input to update in the mutation? Thank you for any advice!

Hello! Has anyone ever experienced issues with

graphcool deploy

on Ubuntu?

FetchError: request to <https://api.graph.cool/system> failed, reason: socket hang up
    at ClientRequest.<anonymous> (/home/jekporkins/.nvm/versions/node/v9.2.1/lib/node_modules/graphcool/node_modules/node-fetch/index.js:133:11)
    at ClientRequest.emit (events.js:159:13)
    at TLSSocket.socketOnEnd (_http_client.js:423:9)
    at TLSSocket.emit (events.js:164:20)
    at endReadableNT (_stream_readable.js:1054:12)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
Exiting with code: 1