Skip to content
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

Parsing Exception on newly downloaded schema #452

Closed
SriwanKm opened this issue Apr 24, 2021 · 2 comments
Closed

Parsing Exception on newly downloaded schema #452

SriwanKm opened this issue Apr 24, 2021 · 2 comments

Comments

@SriwanKm
Copy link

SriwanKm commented Apr 24, 2021

Steps to Reproduce:

  1. Download Schema
  2. Focus on .graphql file with query, as it attempts to parse popups show parse exception

Parsing Errors prevent plugin from functioning normally

Expected:

Can successfully parse and start introspecting and highlighting queries
Latest Version of Plugin, using in Android App on .graphql files

Have been able to manually edit and find a lot of value in the plugin, but in order to increase ease of adoption I would like to find a solution for downloading the schema and parsing smoothly.

Link to Repo with Reproduction or Steps to Reproduce:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Version and Environment Details
Operation system: [version]
IDE name and version: [version]
Plugin version: [version]

Additional context
Add any other context about the problem here.
Screen Shot 2021-04-20 at 11 18 52 AM

@vepanimas
Copy link
Collaborator

Hi @SriwanKm ! Do you still experience this issue? Looks like you had this error due to a default values mismatch. You could skip them in introspection by choosing this option:
gql-introspect-skip-default-values

Actually, I think that we could skip validating default values (at least do not fail schema building completely on conflicting definitions) and remove that option because IMHO it's confusing for the user (as for me, I also always forget why do we have it here 😄). I'm not sure if a default value is a part of the parameter signature, so I'm waiting for the response from the GraphQL team, but I don't think I'll get it ever 😞.

@vepanimas
Copy link
Collaborator

Closing for no response. Also, I suppose it should be fixed in the most recent release. If it's not the case, please, feel free to reopen.

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

No branches or pull requests

2 participants