1.7.0 GraphQL Issues

TheDunco

last month

29

• 

  jmikrut

  Payload Team

  last month

  hmmm - @dribbens will have info for you here

• 

  dribbens

  Payload Team

  last month

  Can you share an example?

• 

  TheDunco

  last month

  All it took for me to experience the issue was updating to 1.7.0, going to the /api/graphql-playground, and trying to run the same queries from before. It says that every query variable isn't defined, even though they are. Do you need a specific example?

• 

  jmikrut

  Payload Team

  last month

  maybe a screenshot of the query you're trying to run, or a minimal example (if your query is too complex)

• 

  noheadphones

  last month

  Seeing this issue right now in my production, let me get more info

• 

  TheDunco

  last month

  Simple example: Logging in a user.

  
  
  

  Query:

  
  

  mutation Login($email: String!, $password: String!) {
    loginUser(email: $email, password: $password) {
      user {
        id
        email
      }
    }
  }

  
  
  

  Query Variables:

  
  

  {
    "email": "<my email>",
    "password": "<my password>"
  }

  
  
  

  Result pictured

  
• 

  noheadphones

  last month

  'Variable "$id" of required type "String!" was not provided.'
  

  
  

  in a query that worked previously, did a

  yarn upgrade
  

  
  

  {"query":"\n    query ArticleLikesById($id: String!) {\n  Article(id: $id) {\n    likeCount\n  }\n}\n    ","variables":{"id":"643c0a4c80bff36c46d68ddc"}}

• 

  jmikrut

  Payload Team

  last month

  is this only in the playground

  
  

  
  

  or is it in your frontends

• 

  noheadphones

  last month

  i can see my variables being set, this is happening for me in production frontend

• 

  jmikrut

  Payload Team

  last month

  ok on it

• 

  TheDunco

  last month

  Yeah, my frontend wasn't working at all when I updated locally

• 

  noheadphones

  last month

  i dont see the deprecation notice for one of the graphql packages anymore...not sure if its related 👀

  
  

  
  

  feat: replace deprecated express-graphql dependency
  

  ahh i see

• 

  jmikrut

  Payload Team

  last month

  yes

  
  

  
  

  this should not have affected anything but apparently it has

• 

  Jarrod

  Payload Team

  last month

  Possibly related:

  https://discord.com/channels/967097582721572934/1097846808631324704
• 

  TheDunco

  last month

  Not sure if I'm interpreting that thread correctly or not, but I did definitely change my lock file when I updated, so I do believe this is a separate issue

• 

  jmikrut

  Payload Team

  last month

  found bug

  
  

  
  

  patch coming in a few mins

• 

  dribbens

  Payload Team

  last month

  I'm going to add GraphQL variable use to our test coverage too. Thanks for reporting @TheDunco!

• 

  TheDunco

  last month

  Awesome, thanks guys, you're great!Adding the test case is fantastic. It's not something you'd think to test unless it happens, yknow

• 

  eloahsam

  last month

  Has the solution been added ?

• 

  noheadphones

  last month

  yeah its released and working!

• 

  eloahsam

  last month

  Oh so I just have to update all my deps

• 

  noheadphones

  last month

  1.7.1 fixes it

• 

  eloahsam

  last month

  yeah works well now finally

• 

  TheDunco

  last month

  Yes, marking this thread as "answered" now, can confirm that 1.7.1 fixes it! Thanks team! @jmikrut @dribbens