Skip to content

"Unknown type 'String'" error in GraphQL request body editor #8657

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
lkaratun opened this issue Jun 15, 2020 · 7 comments · Fixed by #8767
Closed

"Unknown type 'String'" error in GraphQL request body editor #8657

lkaratun opened this issue Jun 15, 2020 · 7 comments · Fixed by #8767

Comments

@lkaratun
Copy link

Describe the bug
Getting an error Unknown type 'String' in GraphQL request body editor

To Reproduce
Steps to reproduce the behavior:

  1. Create a new endpoint, go to body editor
  2. Change body type to "GraphQL"
  3. Enter the following in the "Query" panel:
mutation createAd ($data: String!) {
    createAd (data: $data) {
        id
        description
    }
}
  1. See red squiggly line with error Unknown type 'String'

Expected behavior
No error

Screenshots
image

App information (please complete the following information):

  • App Type Native App
  • Postman Version 7.26.0
  • OS: Windows 10
@eladcandroid
Copy link

I'm facing the same problem, also with predefined types from GraphQL schema

@marcoaleixo
Copy link

same problem here

@middiu
Copy link

middiu commented Jun 21, 2020

same problem for me...

@srinivasskc
Copy link

I see the same problem. But it does not impact my request to proceed.

@coro101
Copy link

coro101 commented Jun 22, 2020

I imported the schema, and there is the same problem. However, auto-completion works well.

@benjaminaudet
Copy link

I have the same problem. It's probably a parsing problem, because the request is working, it was not doing that in the previous version (7.25)

@pankajk07
Copy link
Member

Hi all, we have fixed this as part of v7.28 release. Please update the app and try it out. Do let us know if you come across any other issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

9 participants