This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
All notable changes to the "vscode-graphql" extension will be manually documented in this file.
Check Keep a Changelog for recommendations on how to structure this file.
The git log should show a fairly clean view of each of these new versions, and the issues/PRs associated.
0.3.25
Remove node_modules from bundle after adding esbuild to make the extension bundle smaller
0.3.24
Add highlighting and langauge support for .mjs, .cjs, .es6, .esm and other similar extensions
0.3.23
Major bugfixes for language features. Most bugs with language features not working should be resolved.
The useSchemaFileDefinition setting was deprecated, and SDL-driven projects work by default. If you want to opt-into an experimental feature to cache graphql-config schema result for definitions (useful for remote schemas), consult the readme on how to configure cacheSchemaFileForLookup option in vscode settings, or graphql config (yes you can enable/disable it per-project!)
Definition lookup works by default with SDL file schemas. cacheSchemaFileForLookup must be enabled if you have a remote schema want definition lookup for input types, etc in queries
0.3.19
support graphql-config for .ts and .toml files by upgrading graphql-config & graphql-language-service-server
use * activation event, because graphql-config in package.json is impossible to detect otherwise using vscode activationEvents
support additional language features in graphql-language-service-server such as interface implements interfaces, etc
upgrade operation execution to use a new graphql client and support subscriptions
fix openvsx & vscode publish by re-creating PATs and signing new agreements
Note: there are still some known bugs in the language server we will be fixing soon:
if you don't see editor output, please check your config
output channel may show errors even after your configuration works
require dotenv in the server runtime (for loading graphql config values), and allow a graphql-config.dotEnvPath configuration to specify specific paths
reload server on workspace configuration changes
reload severside graphql-config and language service on config file changes. definitions cache/etc will be rebuilt
note: client not configured to reload on graphql config changes yet (i.e endpoints)
accept all graphql-config.loadConfig() options
0.3.7
update underlying graphql-language-service-server to allow .gql, .graphqls extensions
0.3.6
documentation fix
0.3.5
readme documentation improvements, more examples, FAQ, known issues
bump graphql-language-service-server to allow implicit fragment completion (non-inline fragments). just include your fragments file or string in the graphql-config documents
0.3.4
remove insiders announcement until tooling is properly in place, and insiders extension is up to date
0.3.3
useSchemaFileDefinition setting
0.3.2
#213: bugfix for input validation on operation exection
0.3.1 🎉
upgrade to graphql-config@3
upgrade to latest major version of graphql-language-service-server
upgrades graphql-config@3
remove watchman dependency 🎉
introduce workspace symbol lookup, outline
validation and completion for input variables
generate a schema output by default, for code-first schemas. SDL first schemas have an override option now
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
vscode-graphql@0.3.43
Patch Changes
#391
6be5593
Thanks @acao! - LSP upgrades:insertText
& completion on invalid list typesAll notable changes to the "vscode-graphql" extension will be manually documented in this file.
Check Keep a Changelog for recommendations on how to structure this file.
The git log should show a fairly clean view of each of these new versions, and the issues/PRs associated.
0.3.25
Remove
node_modules
from bundle after addingesbuild
to make the extension bundle smaller0.3.24
Add highlighting and langauge support for
.mjs
,.cjs
,.es6
,.esm
and other similar extensions0.3.23
Major bugfixes for language features. Most bugs with language features not working should be resolved.
The
useSchemaFileDefinition
setting was deprecated, and SDL-driven projects work by default. If you want to opt-into an experimental feature to cache graphql-config schema result for definitions (useful for remote schemas), consult the readme on how to configurecacheSchemaFileForLookup
option in vscode settings, or graphql config (yes you can enable/disable it per-project!)Definition lookup works by default with SDL file schemas.
cacheSchemaFileForLookup
must be enabled if you have a remote schema want definition lookup for input types, etc in queries0.3.19
graphql-config
for.ts
and.toml
files by upgradinggraphql-config
&graphql-language-service-server
*
activation event, becausegraphql-config
inpackage.json
is impossible to detect otherwise using vscodeactivationEvents
graphql-language-service-server
such as interface implements interfaces, etcNote: there are still some known bugs in the language server we will be fixing soon:
0.3.13
LSP bugfixes:
0.3.8
dotenv
in the server runtime (for loading graphql config values), and allow agraphql-config.dotEnvPath
configuration to specify specific pathsgraphql-config
and language service on config file changes. definitions cache/etc will be rebuiltgraphql-config.loadConfig()
options0.3.7
graphql-language-service-server
to allow .gql, .graphqls extensions0.3.6
0.3.5
graphql-language-service-server
to allow implicit fragment completion (non-inline fragments). just include your fragments file or string in the graphql-configdocuments
0.3.4
0.3.3
useSchemaFileDefinition
setting0.3.2
0.3.1 🎉
graphql-config@3
graphql-language-service-server
graphql-config@3