Uknown types and fields - but they work in the app

Version and Environment Details

Operation system:

MacOS 10.14.5

IDE name and version:

Webstorm 2019.1 and the 2019.2 EAP

Plugin version:

2.2.0

Expected Behaviour

Recognize valid GraphQL types and fields.

Actual Behaviour

Highlights MemberInput as Unknown type “MemberInput” and addMember as Unknown field “addMember”. All my queries and mutations on all components have the same issue. If I uncheck the plugin in the IDE then this flagging goes away. The mutations and queries perform as expected either way so this is a plugin, not code, issue.

const addMember = gql `
          mutation addMember($input: MemberInput!) {
              addMember (input: $input) {
                  first_name
                  last_name
                  user_name
              }
          }`;

this.apollo.mutate({
          mutation: addMember,
          variables: {
            input: {
              first_name: first_name,
              last_name: last_name,
              user_name: user_name,
            }
          },
        })
        .subscribe(result => {
          console.log('result.data in subscribe: ', result.data);
          errors = result.errors;
          console.log('errors in mutate', errors)
        });

Steps to Reproduce / Link to Repo with Reproduction and Instructions

Just writing a query or mutation causes this. The schema is compiled by Nestjs on the server as such:

graphql.schema.ts

export class MemberInput {
    first_name: string;
    last_name: string;
    user_name: string;
}

export abstract class IMutation {
    abstract addMember(input: MemberInput): Member | Promise<Member>;

    abstract updateMember(member_id: number, input: MemberInput): Member | Promise<Member>;

    abstract deleteMember(member_id: number): Member | Promise<Member>;
}

This behavior started recently. I didn’t change the IDE version and I also tried 2019.2 EAP.

[tintin10q]

He never came back.

[jimkyndemeyer]

A couple of things to check:

• In the GraphQL tool panel it should show the default schema. It should list any errors and how many types it has found during discovery. You can double click the type summary tree node to see type names and associated files they’re declared in
• If no types are found, and you do have a .graphqlfile, then verify that it’s within the Project scope, e.g. not excluded or in an excluded folder
• As a final step you could do a File menu > “Invalidate caches /Restart”. This can solve issues with index corruption during upgrades