Setup way too complex

Isn’t it sufficient to only point to the schema.graphql file? Also, can’t it make some assumptions about where that file might be?

[malexandre]

I agree with other that the gql dependency should be included inside the plugin. It’s weird that I need to install a module in my project for an extension that my coworkers won’t use because they are not all on VS Code. Also, I think the .gqlconfig file’s option should be options of the extension (options means it can be defined globally, per workspace, per user, etc.), for the same reason. Again, I do not see why I should create a file in the project for my editor. The project files are for the team.

At least that’s my point of view. That’s still awesome to have an extension for graphql intellisense.

[batjko]

I have a fairly large schema at work, which we split into conceptually segregated js files (usually one file for each type and all its resolvers), and use the merge-graphql-schemas package to merge the types and resolvers from the various files. I think for any large schema it makes sense to modularize somehow, so I appreciate that some config will often be required to tell this extension about it.

However, the fact that one needs this @playlyfe/gql library and then also watchman (which is a PITA trying to set it up on anything else but Macs), in addition to the configuration file, just in order to get the basics of this extension running, does strike me as quite an overhead.

Watchman should certainly not be necessary. Linters and others just spawn a background ‘server’ process to watch files, completely transparent to the user.