@nilan Any ETA on the deployment part of the docs getting updated to the latest version? 🙏

@schickling hey, just received a really weird error from the new graphql for vs code

I've opened https://github.com/prismagraphql/vscode-graphql/issues/23

A file was commented on

Hey, this isn’t a rant, I’m just legitimately confused. The documentation has so many starting points. Using docker, using a boilerplate, etc. Neither seem to be complete. The docker tutorial, for example, says the next step is to “build a GraphQL server”, but links to the same page 😕. Every tutorial has a different starting point without explaining the nuances. I’ve been trying to understand the past 2 days how to deploy a service to prisma cloud. Does

prisma deploy

deploy there? Where do all of the tutorials fit in with the prisma cloud service? What are the servers for in prisma cloud? Do I need to add my own? Can I use docker with prisma cloud? Should I use docker at all? what about

node-basic

and

node-advanced

? It seems there is a whole lot of background knowledge that is assumed in so much of this ecosystem. I’m yet to experience the simplicity advertised on the homepage of prisma.io. Its just all very confusing, imo.

Feedback is helpful but if you are looking for how to buy a product or what products are available and struggling, you'd probably have more success contacting their product people... if you're looking to accomplish a specific goal I'm guessing asking about that and then explaining why it was confusing would be more helpful as well

(I run an open source project myself and I get a lot of feedback on it, and even where we know we struggle -- like documentation, for example -- it can be hard to know what exactly would make things better if we don't really know what you were trying to do)

How can I send multiple mutations in one request? and how to handle at ruby-server side?

I'm having some trouble generating types for my custom binding. I'm pretty much following (I think) the example in the docs about creating a class that extends from

Binding

(where I differ is that I'm getting my schema by converting the downloaded introspection result json to SDL with buildClientSchema + printSchema) then I call

npx graphql-binding --language typescript --input schema.ts --outputBinding binding.ts

and get

TypeError: this.schema.getQueryType is not a function
    at TypescriptGenerator.renderQueries (node_modules/graphql-binding/src/codegen/TypescriptGenerator.ts:180:35)
    at TypescriptGenerator.render (node_modules/graphql-binding/src/codegen/TypescriptGenerator.ts:144:31)
    at node_modules/graphql-binding/src/bin.ts:58:34
    at step (node_modules/graphql-binding/dist/bin.js:41:23)
    at Object.next (node_modules/graphql-binding/dist/bin.js:22:53)
    at node_modules/graphql-binding/dist/bin.js:16:71
    at Promise (<anonymous>)
    at __awaiter (node_modules/graphql-binding/dist/bin.js:12:12)
    at run (node_modules/graphql-binding/dist/bin.js:81:12)
    at Object.<anonymous> (node_modules/graphql-binding/src/bin.ts:40:1)

based on the code in TypescriptGenerator.ts, it seems it's supposed to take an executableSchema, not a binding so i'm finding the docs here really confusing

has anybody created a graphql-binding? My goal is simply that one my microservices has a strongly typed API for calling my other microservices' graphql server

Hi Guys, how can we login to multiple Prisma accounts using CLI? I can see the

cloudSession

is stored in ~/.prisma/config.yml. If I want to login to another Prisma account, I have to remove that

cloudSession

and do the CLI:

prisma login

again. @nilan

Does prisma support fuzzy search in any way?

hi guys, sorry if this is a newbie question but I've already spent a lot of time trying to figure out a solution and not even close. I was hoping someone could give me a direction. I created a project using the node-basic boilerplate and I want it to use a local postgres database. So, I created a temp folder, ran

prisma init

, copied the docker-compose file to the database folder, removed the endpoint key, ran prisma init and then got a new endpoint key in the prisma.yml file. I ran

docker-compose up -d

and it was fine, then when I ran prisma deploy I get this:

Error: Could not connect to server at <http://localhost:4466>. Please check if your server is running.

. Am I missing anything? For what I understand I need 2 servers, the one created by docker-compose which is where Prisma sits, and then the web server to consume it.

Hello world, I have a question concerning prisma subscriptions. I have a prisma backend with subscriptions implemented and and react native frontend. When I test my subscriptions in the playground, they work just as expected. (🙌 at Prisma for getting there, prisma gets more fun every day 🙂 ). When I subscribe with my frontend using

apollo-client

, the first time I subscribe, everthing works as expected. However, when I reload my frontend and resubscribe, the subscriptions dont get fired any more. Now, how does prisma handle resubscriptions, and what happens to the old subscriptions when my client app is killed and relaunches, i.e. the subscription is left hanging and another subscription is called from the same client? I know that this is deeply linked with apollo and the solution is probably located on the client side, however, I still thought I'd ask what happens on the server side. Glad about any input and experiences! Thanks!

graphql is an architecture ? and what's advantages of using architecture graphql in my project ?

graphql is a spec, not an architecture

but it can be a critical part of your architecture

there are a bunch of upsides. for example, querying with graphql allows the client to be very concise in what they want (no over/under fetching) and to traverse relations in a single request

@hamdi ^

❓ Terrible newbie question here: I have set up a Demo server in Prisma Cloud. Correct me if I am wrong, but there seems to be no authentication?. Once somebody knows the URL of this demo server, can they fire queries against it?

hello everyone, I’m digging currently into graphql-yoga and try to find a more complete example of PubSub and subscribing with variables. I don’t use prisma yet, just try to follow the bare setup for learning purpose

I found this example: https://github.com/prismagraphql/graphql-yoga/tree/master/examples/subscriptions

But it lacks some more complete usecase for CRUD

any more details would be appreciated, for example where and how to setup publish

here is my current attempt, but unfortunately its not working: https://gist.github.com/dohomi/cecd58454512d682c83d814e1b56cfbb

hi...trying to work with graphql playground and aws appsync...i am using (so far) a simple api key to connect to my graphql endpoint...unfortunately the playground doesn't seem to add the x-api-key header when connecting to the websocket endpoint for the subscription...is that a bug or is it simply unimplemented at this time? how are others coping with this problem? :S

(for non subscription requests the playground works after adding the x-api-key header to the http headers)

just realising that browser websockets do not support custom headers 😄

Prisma peeps, trying to use your new graphql VSCode extension, but experiencing an unhappy conflict with Apollo's graphql-tools! For the typeDefs option that the graphql-tools makeExecutableSchema function receives, a string is expected. Prisma's extension doesn't recognize just any old string as a target for the extension, so my strings are as monochrome and unclickable as before! Are there any existing solutions to this issue?