Skip to content

2.0.0-alpha-8: Improved introspection, intentions to add missing schema types in SDL

Pre-release
Pre-release
Compare
Choose a tag to compare
@jimkyndemeyer jimkyndemeyer released this 10 Mar 18:52

This is the eight alpha of version 2, which contains the following changes:

  • Improved introspection including support for custom scalars
  • Added intention to add missing schema types in SDL
  • Fixed error marker positions in gql tags
  • Moved configuration scan to background tasks
  • Added support for projects in scratch files
  • Added completion of variable names
  • Added completion of enums in lists
  • Fixed arguments shown as keywords in syntax highlighter

This is expected to be the last alpha release since it's considered feature complete for the initial 2.0 release.

The first beta release will be cut after the initial round of testing.

Upgrade notes from v1 and previous alpha releases

  • The plugin no longer uses a graphql.config.json file but will show a migration notification. Schema discovery is now project-wide by default, or configured using graphql-config .graphqlconfig files.

Getting and installing the alpha releases

The alpha releases will be published directly in this repository and is added to your IDE using a custom plugin repository URL:

  • In your IDE, click "Settings" > "Plugins" > "Browse repositories..." > "Manage repositories..."
  • In the "Custom Plugin Repositories" dialog that opens, add the following url: https://github.com/jimkyndemeyer/js-graphql-intellij-plugin/raw/v2/alpha-releases/updatePlugins.xml
  • Once added, click "Ok" to return to the "Browse repositories" dialog.
  • You should now see a "Repository: All" dropdown. Select this alpha repository that you just added.
  • You should now see the GraphQL alpha plugin listed.

As new alpahas are released, you should get plugin update notifications as per ususal.

Documentation (work in progress)

https://gist.github.com/jimkyndemeyer/1903b65ff892f0811e76f16d8b530848

Reporting issues

The main issue for tracking the v2 road map is #164. Feedback and questions are welcome in that issue.

For bugs, see the known issues and limitations below. If the issue is not mentioned, use a [v2] prefix when reporting issues for the alpha.