Mayank Agarwal

@harleyguru > As a note, just now I've suppressed by doing following: defined directive @aws_subscribe(mutations: [String]) on FIELD_DEFINITION in schema Yes you have to define directive like this and any...

@harleyguru ```javascript { schema: { files: '**/*.gql', // aws-app-sync is a npm package which defines all config specific to aws app sync. // This is same as how we create...

@harleyguru It's not released yet and also someone has to create preset ```aws-appsync``` (may be you :) ). `presets` option is added so that community can easily add (share) support...

@jvbianchi you can disable validation rules to suppress errors ```javascript // .gqlconfig { match: "path/to/files", validate: { extends: "gql-rules-query", rules: { KnownFragmentNames: "off", NoUnusedFragments: "off" } } } ```

> I'm not sure that suppressing the errors is necessarily the best solution. One might want to know, for instance, about truly unknown or unused fragments, not just fragments from...

_From @kumarharsh on June 5, 2017 12:8_ @gaoxiaoliangz thank you for the report. The plugin shouldn't be throwing this error, as the interpolation you're doing is perfectly valid. I'm myself...

Actually, the plugin will throw an error as [gql](https://github.com/Mayank1791989/gql) parser only support interpolation inside operations and fragments (relay style) not outside as in apollo.

@tizmagik Yes you are right. But in v3 I have replaced isRelay with general env option which takes package name. This package comes with few env ('relay', 'apollo' and 'relay-modern')...

@ntziolis I have released a new version [v2.6](https://github.com/Mayank1791989/gql/releases/tag/v2.6.0) with document interpolation support.

It's better we add new validation mode 'onType' which can be changed using option `graphqlForVSCode.validate: onType | onSave`