Jump-to-definition not working within schema definition file about vscode-graphql HOT 10 CLOSED

Here's the simplest repro I can make (I grabbed the schema from the graphql-js project codebase) https://github.com/AndrewIngram/vscode-graphql-repro

I'm not seeing any jump-to-definition behaviour on anything.

from vscode-graphql.

@AndrewIngram : Thanks for raising the issue. Can you please provide a minimal reproduction (or the single graphql file) as a github gist/repo? Will expedite things at my end.

I will look into it tomorrow evening or over the weekend. Thanks.

from vscode-graphql.

@AndrewIngram : Also, Generally, one file schema jump should work without the includes. But what are you trying to jump on? We currently support it for Enum, types and input types only. Not scalars etc.

from vscode-graphql.

Thanks! I will look into it asap and revert. I have to test it with .graphqlconfig - JSON but in the meantime, would it be possible to use the yml format and rename config to .graphqlconfig.yml.

That might work. Thanks.

from vscode-graphql.

Type:

Enum:

from vscode-graphql.

I've changed the repro to use yaml, but it hasn't made any difference

from vscode-graphql.

@AndrewIngram : Thanks, I will look into this soon and revert :)

from vscode-graphql.

@AndrewIngram : Ah! the problem is that due to #18, extension thinks that schema is not valid and is unable to parse it.

Because interface and & is just a valid SDL after the latest spec release (June-2018) and we do not support that yet.

Need to make the graphql-language-service support graphql-js version 0.14.

I will try to pick this up soon.

from vscode-graphql.

Created an issue https://github.com/graphql/graphql-language-service/issues/244 to track the progress of this.

from vscode-graphql.

@AndrewIngram check out 0.3.1! I still need to expose the option to use .graphql files as source for 0.3.2 (by default generates from projectConfig.getSchema() result), but at least you'll have jump to definition!

from vscode-graphql.