Js-graphql-intellij-plugin: After the most recent update, fragment fields are being seen as unknown

[xxx]

After a plugin upgrade a couple of days ago, I have fragments that are showing that they have invalid fields. The fragments are working fine and were correctly handled in the previous version.

Expected behavior
The fragments are found in the schema and highlighted correctly.

Screenshots

Version and Environment Details
Operation system: Linux vatican 5.3.0-64-generic #58-Ubuntu SMP Fri Jul 10 19:33:51 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
IDE name and version: RubyMine 2020.2
Plugin version: 2.6.0

[vepanimas]

@xxx hi, thank you for the report. Unfortunately, I can't reproduce it, I have an example project with GitHub schema, everything works there. I need more information about your project configuration, .graphqlconfig and an example schema for which fragments don't work.

[xxx]

@vepanimas Hi, thank you for responding. Is the example project online? These fragments are multiple levels deep, which is one point of complexity that most examples won't contain.

[xxx]

@vepanimas hm, now they are rendering ok, even though nothing has changed. I guess I'll close this, but this was very strange behavior. Even an 'invalidate and restart' didn't work earlier. Dunno.

[vepanimas]

@xxx ok, if you encounter this problem again feel free to reopen this issue. Also, I know about some existing problems with caching now, which possibly could lead to this behavior, I hope to fix them in next releases. But I'm not sure about your case though, because restart usually fixes them.

[a-sane]

@vepanimas @xxx I have the same problem

Version and Environment Details
Operation system: macOS Mojave 10.14.6
IDE name and version: WebStorm 2020.2
Plugin version: 2.6.0

[vepanimas]

@a-sane hi, do any other schema errors in the GraphQL tab? Any information could be useful. Also, have you tried invalidating caches? Of course, this is not a solution, but it's better to know if caching or something else is affecting it.

[a-sane]

@vepanimas

if I understood correctly there is no errors in the GraphQL tab:

I'm tried invalidating caches, still no luck. Also sometimes this error randomly disappear and then appear again.
I can't figure out how to reproduce this stably.

.graphqlconfig:

{
  "schemaPath": "schema.graphql",
  "includes": ["*.graphql", "*.js"],
  "excludes": ["node_modules/**"]
}

[vepanimas]

@a-sane @xxx is it still reproduced? I fixed some issues similar to that one, so I'm not sure if it's still relevant.

[xxx]

@vepanimas I just updated to 2.8.0 this morning, but things seem good so far.

[vepanimas]

Then I'll close it for now. If similar problems arise, feel free to comment here or open a new issue.