Known Issues, Maintainers & Contributors Needed

[acao]

👀 Actual Behavior

vscode-graphql language features don't work often.

⚠️ Known Issues

(many of these issues cause language features to not work at all, only syntax highlighting)

make sure you've consulted the readme and have a graphql config file!

• schema to SDL file support seems to be broken. try schemaPath for a single schema file instead, though declarations doesn't seem to work.
• remote schemas URLs kind of work with schema props
• .ts and .toml graphql-config files weren't working but now are because we upgraded graphql-config. hopefully that fixes other issues
• the extension activates on * all the time now, because there is no activationEvent that could pick up on graphql-config in package.json. it may crash if there is no graphql in files
• graphql-mesh style schema configuration may cause issues with remote schema cacheing, thus no language features

Expected Behavior

They should

🔧 Help Resolve the Problem

Help us improve this situation! The language server is where most of the issues are, and we have created an issue for you there to help plan the future of this extension and the graphql LSP ecosystem in general!

graphql/graphiql#2050