For a server-side subscription, can a change in relation be observed? For example, if my restaurant has tables, and each table is assigned a waiter, can a server-side subscription be triggered when a table is assigned a waiter?—when a relation is added or removed?

Hey <!channel> 👋 We are super excited to kick-off the developer preview of the Graphcool 1.0 beta graphcool 🦜 Graphcool 1.0 incorporates much of the feedback we've received over the last two years. The developer preview will be in open beta over the following weeks. This blog post provides general information about Graphcool 1.0: https://medium.com/@graphcool/c1d4981383d9 If you want to get your hands dirty and provide early feedback, check out the boilerplate example (https://github.com/graphcool/graphql-boilerplate). You can discuss questions and feedback in the Forum (https://www.graph.cool/forum/t/developer-preview-graphcool-1-0-beta/1891?u=nilan) Thanks so much 🙌

exciting!

Interfaces ❤️

Kudos to everyone on the team and contributors 👏💪 Rock on

@nilan Thanks for the wonderful updates. I am a bit ‘out of date’ and still use graphcool cli v0.8.5. I can see the project structure has changed a lot and there is a yoga server sitting in between client and Graphcool database. I am very eager to try the new 1.0, but I do have a live system that I need to keep running safely. Is it possible for your team to produce a guide of upgrading? I would really appreciate it 💪

Here's the link to the Feedback forum post for the new Framework (the link above didn't work for me):

YEAH! Awesome. Thanks everyone. Just in right time as well.

👏 Just in time for Christmas.. what a present.

Pre 1.0 / beta GraphCool has many, often radical, API shifts. How stable do you think 1.0 will be?

And it doesn't look like

graphcool@beta

is on NPM yet. Edit: now it is but with an error

syscall chmod
npm ERR! enoent ENOENT: no such file or directory, chmod '/usr/local/lib/node_modules/graphcool/dist/index.js'
npm ERR! enoent This is related to npm not being able to find a file.

finally i've been waiting for this forever.. thank you Graphcool team! ❤️

graphcool❤️

awesome and just watched the video, I am going to explore this deeper!

I have a question regarding the new Graphcool 1.0. Currently, I love Graphcool because of the whole idea of not needing to host a backend myself, instead, I just need to host frontend JS files. As of right now I am using the Graphcool Framework and it is great because I have version control and full access to the files while at the same time I am not actually having to host any of them. My question is, with the introduction of the new 1.0, will I be able to keep things the way they are currently? For instance, will I need to host a database or server myself? Or, will I be able to continue to use the Graphcool Cloud and have the server and database hosted for me still? Sorry if my question does not make a ton of sense, but I am just a little bit confused on what could possibly change for me from the way things are right now with the current version of the Graphcool Framework. Thank you, Michael.

I've just watched the video and I'm feeling a bit lost. What I loved about graphcool was the abstraction from the backend. In the video you're showing the code for each query and resolver. With 1.0, do we have to worry about them or will they be created automatically like the old version? Maybe I'm confusing it with the framework? Sorry, I'm quite new to this project!

btw the hosted demo on https://github.com/graphcool/graphql-server-example is down atm!

@Michael Jones @Emi The basics about the Graphcool backend will not change. You will still get a full back-end with connected database out of the box, just like you are now. There will be some changes in the API, but the basic functionality will remain the same. You will still be able to use that back-end 'as-is' like you are now. The API/Gateway is the emerging answer to a lot of common requirements/questions/features that people using GraphQL are looking for: more control over the exposed schema, more control over authentication, stitching multiple schemas together in one endpoint etc. For this purpose, Graphcool and others in the GraphQL community (like Apollo and myself) have been developing tooling to make this process easier. The boilerplate and tools that Graphcool offer for this purpose are the result of these emerging best practices. So this does not change anything about the back-end offering, it just adds on top of it for those that need the features that it offers.

getting an error after deploying "Schema could not be fetched. Please check if the endpoint 'http://localhost:60001/api/graphql-boilerplate/test' is a valid GraphQL Endpoint." Any ideas? 🙂

Is being able to host on your own infrastructure still on the roadmap anywhere? It isn't listed at https://github.com/graphcool/framework/pull/1318

I'm getting this problem on windows when trying to follow along with the video in the medium article

@Kat commented on @mwarger’s file https://prisma.slack.com/files/U7YAK1S9J/F8F4Z0FK6/any_ideas_.txt: There seems to be some issues with windows right now.. I got the same thing and another windows related issue I posted on the forum

As always, the first version appears not to work on Windows 😞

You can run

yarn

manually inside the created blogr folder

heh, that seems to be the case with so many projects these days... not everyone has a mac 😞

thanks for the tip about yarn

hi all, may I kindly ask, why in my two models that have a relation

mutation createLinkAndTags { createLink( title:"heyyy" description: "I am a good author!“ url:”“ category:”" tagsIds: [“cjb65amkn7yhv0172gi3rg7x6”] ) { id title url description tags { id name } } }

when I run this^ in my react app. I see the tagIds in my Link Objects in graphcool console, but they are not related? I have to click that they are related and hit save