Title
n

noahdavis

02/20/2018, 12:33 PM
Has anyone hit this error before:
{
  "data": {
    "signup": null
  },
  "errors": [
    {
      "message": "Field \"user\" of type \"User\" must have a selection of subfields. Did you mean \"user { ... }\"?",
      "locations": [
        {
          "line": 3,
          "column": 3
        }
      ],
      "path": [
        "signup"
      ]
    }
  ]
}
^ just started happening, doesn't matter if we are using the prisma cloud deployed data store (AWS Aurora) or the public clusters
j

jof

02/20/2018, 12:35 PM
Is this in the playground?
If so, do you have more than one open?
n

noahdavis

02/20/2018, 12:37 PM
@jof - yes, I have about 6 open
j

jof

02/20/2018, 12:37 PM
Close them all and then open just one
If that solves it, file an issue if you get a moment. (I'd do it but I have to leave right now). @ me (JofArnold on GitHub) if you do
n

noahdavis

02/20/2018, 12:38 PM
still no luck @jof
I shut down my browser completely and rebooted
n

nilan

02/20/2018, 12:40 PM
This error message is explained here: https://blog.graph.cool/graphql-server-basics-demystifying-the-info-argument-in-graphql-resolvers-6f26249f613a It has nothing to do with the Playground, it's about your resolvers 🙂
n

noahdavis

02/20/2018, 12:43 PM
Thanks Nilan
Interesting that the problem just popped up
n

nilan

02/20/2018, 12:46 PM
depending on your resolver, two different queries might work and not work. maybe this is what you're encountering as well.
n

noahdavis

02/20/2018, 2:21 PM
It was actually not an issue with the resolvers, but an issue with pointing to our AWS Aurora datastore deployed via prisma
we switched back to the public clusters in our .env.prod and everything was great
n

nilan

02/20/2018, 2:21 PM
hmm that's strange 🙂
n

noahdavis

02/20/2018, 2:22 PM
PRISMA_CLUSTER
should look like what for the prisma cloud deployed data store?
n

nilan

02/20/2018, 2:27 PM
I don't understand the question, sorry
can you elaborate?
n

noahdavis

02/20/2018, 2:29 PM
so I deploy with
prisma deploy
and I get my uri returned
which I set as my Prisma endpoint in my
.env.prod
file
Just answered my own question. Trying something and seeing if there error persists
n

nilan

02/20/2018, 2:31 PM
Ok!
n

noahdavis

02/20/2018, 3:53 PM
Yeah, when using my prisma.sh uri, I get the following error now:
{
  "data": {
    "signin": null
  },
  "errors": [
    {
      "message": "GraphQL Error (Code: 200)",
      "locations": [],
      "path": [
        "user"
      ]
    }
  ]
}
but no issues when using the public clusters. There are no errors when running deploy to the production cluster
n

nilan

02/20/2018, 3:55 PM
Gotcha, please reach out to me in a PM 🙂