Go To Definition No Longer works about vscode-graphql HOT 9 CLOSED

Would you please confirm whether this is broken so I can maybe try to fix it, or is it problem of my configuration? Maybe some bad global dependencies?

Current:

Prisma: prisma/1.14.2 (darwin-x64) node-v10.9.0
Graphql: 2.16.5

from vscode-graphql.

@tomitrescak mine isn't working either.

from vscode-graphql.

Confirming - same issue, worth mentioning running on code-insiders. quadruple checked the graphql config files, paths, schemas

from vscode-graphql.

@divyenduz you mention "Needs Reproduction", but I mentioned two repos where it does not work. You can just try the following one:

https://github.com/prisma/graphql-server-example

Thanks for looking into this. The plugin is otherwise spectacular!

from vscode-graphql.

I'm running into the same issue with a Gatsby (graphql) project as well.

from vscode-graphql.

It'd be nice if somebody could look into this issue.

from vscode-graphql.

Thanks all for the feedback. Can any of you please share the logs for GraphQL Language Service? From your environment: https://github.com/prisma/vscode-graphql#a-testinglogging-graphql-language-features

from vscode-graphql.

Ok so I followed the instructions here's what my log shows:

Which to me makes absolutely no sense, and how is it related to Go to definition not working.

from vscode-graphql.

@chanlito : It looks like you have the same fields on mutation type (maybe you are using schema stitching or something or maybe it is a multi-repo project - extension cannot tell if different files belong to different projects, if they have duplicates).

This fails extendSchema from graphql-js being used by the graphql-language-service.

Here is an example of how this might be going wrong: https://codesandbox.io/s/34lvxl4pn1

Posted this information here for anyone who might attempt a fix for this. This might require big changes in the language service.

from vscode-graphql.