v1.4.1.143-145 - Support for gql tagged templates used by Apollo and Lokka GraphQL Clients

Compatible with versions prior to 2016.2.2.

Features:

• Support for gql tagged templates used by Apollo and Lokka GraphQL Clients (#25)
• Language Service 1.3.0 with Lokka and Apollo gql support (#25)
• Persist endpoint selection to project configuration

v1.4.1 - Support for gql tagged templates used by Apollo and Lokka GraphQL Clients

Features:

• Support for gql tagged templates used by Apollo and Lokka GraphQL Clients (#25)
• Language Service 1.3.0 with Lokka and Apollo gql support (#25)
• Persist endpoint selection to project configuration

v1.4.0.143-145 - Upgrade to Language Service v1.2.0

Compatible with versions prior to 2016.2.2.

Features:

• Language Service 1.2.0 based on graphql 0.7.0 and codemirror-graphql 0.5.4 (#22)
• Basic editor support for GraphQL Schema files (.graphqls) (#22)

v1.4.0 - Upgrade to Language Service v1.2.0

Features:

• Language Service 1.2.0 based on graphql 0.7.0 and codemirror-graphql 0.5.4 (#22)
• Basic editor support for GraphQL Schema files (.graphqls) (#22)

v1.3.3 - IDEA 2016.2.2 compatibility fix

Changes:

• Closes #18 Plugin not compatible with IDEA 2016.2.2

v1.3.2.143-145 - Plugin compatibility updated

Changes:

• This release limits the newest version to 145.* (IDEA 2016.1) due to changes in the JavaScript and NodeJS APIs

v1.3.2 - Remove GraphQL schema from scratch file formats

Changes:

• Closes #14 Remove GraphQL schema from scratch file formats

v1.3.1 - Webstorm 2016.2 EAP compatibility fix, schema size limit increased

Changes:

• Closes #13 JSLanguageCompilerToolWindowManager: NoClassDefFoundError in WebStorm 2016.2 EAP
• Language Service 1.1.2 increases maximum size of JSON schema from 100kb to 32mb

v1.3.0 - Query result enhancements

• Support for GraphQL scratch files
• Invoke reformat code action on query result

Closes #11

v1.2.0 - Add support for contextual queries

Closes #6:

Execute specific parts of a .graphql query buffer:

• Selection
• Named operation including any used fragments

This allows for experimentation since multiple queries can be present in the editor, and the "Unused fragment" server validation error can be avoided.