Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 main, this PR will be updated.
Releases
[email protected]
Minor Changes
82f1ecc
Thanks @dimaMachina! - addclassName
prop. Additional class names which will be appended to the GraphiQL container elementPatch Changes
5bc7b84
,fdec377
,56c6f45
,93c7e9f
]:@graphiql/[email protected]
Minor Changes
5bc7b84
Thanks @dimaMachina! - update vite to v5Patch Changes
#3637
fdec377
Thanks @dimaMachina! - update eslint plugins and fix errors#3656
93c7e9f
Thanks @dimaMachina! - setbuild.minify: false
for cjs/esm builds since minified variable names change every build timeUpdated dependencies [
fdec377
,56c6f45
]:[email protected]
Patch Changes
#3637
fdec377
Thanks @dimaMachina! - update eslint plugins and fix errorsUpdated dependencies [
fdec377
]:@graphiql/[email protected]
Patch Changes
#3657
5bc7b84
Thanks @dimaMachina! - update vite to v5#3656
93c7e9f
Thanks @dimaMachina! - setbuild.minify: false
for cjs/esm builds since minified variable names change every build timeUpdated dependencies [
5bc7b84
,fdec377
,93c7e9f
]:@graphiql/[email protected]
Patch Changes
#3657
5bc7b84
Thanks @dimaMachina! - update vite to v5#3656
93c7e9f
Thanks @dimaMachina! - setbuild.minify: false
for cjs/esm builds since minified variable names change every build timeUpdated dependencies [
5bc7b84
,fdec377
,93c7e9f
]:@graphiql/[email protected]
Patch Changes
56c6f45
Thanks @dimaMachina! - preferlocalStorage
overwindow.localStorage
[email protected]
Patch Changes
fdec377
Thanks @dimaMachina! - update eslint plugins and fix errors[email protected]
Patch Changes
#3647
ba5720b
Thanks @acao! - several LSP fixes and improvements:Bugfixes
debounce schema change events to fix codegen bugs to fix [lsp-server] vscode-graphql triggers large amounts of requests to my graphql server for bulk file change events in 0.11.0 #3622
on mass file changes, network schema is overfetching because the schema cache is now invalidated on every watched schema file change
to address this, we debounce the new
onSchemaChange
event by 400msnote that
schemaCacheTTL
can only be set in extension settings or graphql config at the top level - it will be ignored if configured per-project in the graphql configCode Improvements
schemaCacheTTL
setting not being passed to the cacheUpdated dependencies [
ba5720b
,fdec377
,e2c04c7
]:[email protected]
Patch Changes
#3647
ba5720b
Thanks @acao! - several LSP fixes and improvements:Bugfixes
debounce schema change events to fix codegen bugs to fix [lsp-server] vscode-graphql triggers large amounts of requests to my graphql server for bulk file change events in 0.11.0 #3622
on mass file changes, network schema is overfetching because the schema cache is now invalidated on every watched schema file change
to address this, we debounce the new
onSchemaChange
event by 400msnote that
schemaCacheTTL
can only be set in extension settings or graphql config at the top level - it will be ignored if configured per-project in the graphql configCode Improvements
schemaCacheTTL
setting not being passed to the cache#3637
fdec377
Thanks @dimaMachina! - update eslint plugins and fix errors#3671
e2c04c7
Thanks @acao! - - switch to using just @astrojs/compiler instead of the more complex "sync" adaptation using workersUpdated dependencies [
fdec377
]:[email protected]
Patch Changes
#3637
fdec377
Thanks @dimaMachina! - update eslint plugins and fix errorsUpdated dependencies [
fdec377
]:[email protected]
Patch Changes
#3647
ba5720b
Thanks @acao! - several LSP fixes and improvements:Bugfixes
debounce schema change events to fix codegen bugs to fix [lsp-server] vscode-graphql triggers large amounts of requests to my graphql server for bulk file change events in 0.11.0 #3622
on mass file changes, network schema is overfetching because the schema cache is now invalidated on every watched schema file change
to address this, we debounce the new
onSchemaChange
event by 400msnote that
schemaCacheTTL
can only be set in extension settings or graphql config at the top level - it will be ignored if configured per-project in the graphql configCode Improvements
schemaCacheTTL
setting not being passed to the cacheUpdated dependencies [
ba5720b
,fdec377
,e2c04c7
]: