Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version Packages #2862

Merged
merged 1 commit into from
Nov 3, 2022
Merged

Version Packages #2862

merged 1 commit into from
Nov 3, 2022

Conversation

acao
Copy link
Member

@acao acao commented Nov 3, 2022

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

graphql-language-service-cli@3.3.12

Patch Changes

  • Updated dependencies [bdd1bd04, 967006a6]:
    • graphql-language-service-server@2.9.2

graphql-language-service-server@2.9.2

Patch Changes

  • #2861 bdd1bd04 Thanks @aloker! - add missing pieces for svelte language support

  • #2488 967006a6 Thanks @acao! - DisablefillLeafsOnComplete by default

    Users found this generally annoying by default, especially when there are required arguments

    Without automatically prompting autocompletion of required arguments as well as lead expansion, it makes the extension harder to use

    You can now supply this in your graphql config:

    config.extensions.languageService.fillLeafsOnComplete

    Setting it to to true will enable this feature.
    Will soon add the ability to manually enable this in monaco-graphql as well.

    For both, this kind of behavior would be better as a keyboard command, context menu item &/or codelens prompt

monaco-graphql@1.1.5

Patch Changes

  • #2488 967006a6 Thanks @acao! - DisablefillLeafsOnComplete by default

    Users found this generally annoying by default, especially when there are required arguments

    Without automatically prompting autocompletion of required arguments as well as lead expansion, it makes the extension harder to use

    You can now supply this in your graphql config:

    config.extensions.languageService.fillLeafsOnComplete

    Setting it to to true will enable this feature.
    Will soon add the ability to manually enable this in monaco-graphql as well.

    For both, this kind of behavior would be better as a keyboard command, context menu item &/or codelens prompt

vscode-graphql@0.8.2

Patch Changes

  • #2861 bdd1bd04 Thanks @aloker! - add missing pieces for svelte language support

  • #2488 967006a6 Thanks @acao! - DisablefillLeafsOnComplete by default

    Users found this generally annoying by default, especially when there are required arguments

    Without automatically prompting autocompletion of required arguments as well as lead expansion, it makes the extension harder to use

    You can now supply this in your graphql config:

    config.extensions.languageService.fillLeafsOnComplete

    Setting it to to true will enable this feature.
    Will soon add the ability to manually enable this in monaco-graphql as well.

    For both, this kind of behavior would be better as a keyboard command, context menu item &/or codelens prompt

  • #2849 9b98c1b6 Thanks @acao! - docs typo bug - /* GraphQL */ (not /* GraphiQL */) is the delimiter for vscode-graphql-syntax & vscode-graphql language support

  • Updated dependencies [bdd1bd04, 967006a6]:

    • graphql-language-service-server@2.9.2

vscode-graphql-syntax@1.0.5

Patch Changes

  • #2849 9b98c1b6 Thanks @acao! - docs typo bug - /* GraphQL */ (not /* GraphiQL */) is the delimiter for vscode-graphql-syntax & vscode-graphql language support

@github-actions
Copy link
Contributor

github-actions bot commented Nov 3, 2022

The latest changes of this PR are not available as canary, since there are no linked changesets for this PR.

@acao acao merged commit 7da648b into main Nov 3, 2022
@acao acao deleted the changeset-release/main branch November 3, 2022 22:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant