still getting the error `No cluster set. Please se...
# orm-help
w
still getting the error
No cluster set. Please set the "cluster" property in your prisma.yml
when trying to use playground - I thought clusters were deprecated in favour of the endpoint
n
that's correct. When exactly do you get this error? Is it for a certain command?
w
@nilan its when i start the playground from npm
n
I see - is it the Playground in the browser, or the Electron app?
w
electron
Version 1.6.0 (1.6.0)'
n
can you share your
prisma.yml
and
.graphqlconfig.yml
? ๐Ÿ™‚
I also get this:
Copy code
warning command prepare both exists in plugin /Users/wesbos/Sites/advanced-react/next/finished-applica
tion/backend/node_modules/graphql-cli-prepare and is shipped with the graphql-cli.
The plugin is being ignored.
n
so you run
npm run playground
, right?
w
yep
n
what do you use for your env vars? I set up an
.env
file but it isn't picked up in
db.js
w
๐Ÿ‘ 1
n
can reproduce, thanks! I will look into this.
@wesbos this looks like a regression in the electron app
1.6.0
w
ohhh really
can i roll bak?
n
I just tried it with
1.5.8
and it works
Yes, you can download and install
1.5.8
from here: https://github.com/prismagraphql/graphql-playground/releases/tag/v1.5.8
Remember to then click away the auto upgrade
w
will try that - thank you
n
ok, let me know how that goes for you ๐Ÿ™‚
w
@nilan same problem - I remember @schickling had this issue when he demoโ€™d it to me and I have never not had it
n
Ok. I am not able to reproduce it with
1.6.0
anymore so I might have done another change that fixed it. I will try to reproduce it again ๐Ÿ™‚
w
okay
n
this is just a hunch, can you update the
playground
npm script to
"playground": "graphql playground --dotenv variables.env",
I added
--dotenv variables.env
w
ah I think that worked ๐Ÿ™‚
still telling me
Copy code
warning command prepare both exists in plugin /Users/wesbos/Sites/advanced-react/next/finished-application/backend/node_modules/graphql-cli-prepare and is shipped with the graphql-cli.
The plugin is being ignored.
n
ok - it's not a regression, it's just a bad error message. the
endpoint
property has no value, and so the checker tries to check the
cluster
property instead
w
ah that makes sense
n
Yes this warning is expected for now.
w
okay cool thanks a lot
n
I created an issue here to resolve the warning: https://github.com/graphql-cli/graphql-cli/issues/326
cheers!