graphql / graphiql

GraphiQL & the GraphQL LSP Reference Ecosystem for building browser & IDE tools.
MIT License
15.97k stars 1.71k forks source link

Python Language Server conflicting with GraphQL extension #2342

Open webdog opened 3 years ago

webdog commented 3 years ago

Hello, I am x-posting this issue for visibility. Thanks!

Environment data

Expected behaviour

Execute GraphQL queries to a remote endpoint successfully, inside of a multi-root, multi-language workspace.

image

Actual behaviour

Installing and running this extension inside of my Python Workspace with the listed configuration generates the following error

  ERR name must not be falsy: Error: name must not be falsy
    at Function.validate (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:524:978)
    at new C (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:524:927)
    at new C (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:511:436)
    at asSymbolInformation (/Users/user/.vscode/extensions/graphql.vscode-graphql-0.3.12/node_modules/vscode-languageclient/lib/protocolConverter.js:383:22)
    at /Users/user/.vscode/extensions/graphql.vscode-graphql-0.3.12/node_modules/vscode-languageclient/lib/protocolConverter.js:372:42
    at Array.map (<anonymous>)
    at Object.asSymbolInformations (/Users/user/.vscode/extensions/graphql.vscode-graphql-0.3.12/node_modules/vscode-languageclient/lib/protocolConverter.js:372:23)
    at /Users/user/.vscode/extensions/graphql.vscode-graphql-0.3.12/node_modules/vscode-languageclient/lib/client.js:1005:62

The errors do not appears to be from the Language Server, but googling for the error itself yields only issues related to the Python Language Server. I am able to run the graphql extensions inside a single language, non multi-root workspace (From my screenshot above). Search Reference

Steps to reproduce:

Logs

Thanks!

acao commented 2 years ago

we have disabled the inline query execution for now, but we can revisit this in the future

acao commented 2 years ago

I have another ticket where we are tracking multi-root workspaces support, it is definitely planned!