Setup way too complex
See original GitHub issueIsn’t it sufficient to only point to the schema.graphql
file? Also, can’t it make some assumptions about where that file might be?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:13
- Comments:27 (10 by maintainers)
Top Results From Across the Web
PM opting for an overly-complex setup which nobody has ...
There is no sense of control and no clear way back to it. The last thing you should do is work hard, keep...
Read more >How to Tell If Your Robot Simulation Setup Is Too Complex
A Quick Tip to Avoid Simulation Overcomplexity The key to creating a simulation that is not overly complex is to always think about...
Read more >Solo mode. Way too complex to run?
I suggest playing a dual-handed learning game first. This was common tactic used by most play testers. Once they were comfortable with their ......
Read more >How to handle your kids wanting to play games way too ...
If a game is legitimately too difficult, it doesn't help a child's enjoyment of the hobby to get obliterated or to just feel...
Read more >page too complex - HP Support Community - 7486781
what does the message page too complex mean, and is there a fix ... is any way to install more memory, I can't...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
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.
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.