Closed twmillett closed 4 years ago
thanks for reporting this!
we are working on upgrading the underlying graphql-language-service-server
which addresses this problem, however there are a few breaking changes in gls-server@2.4.x
and at least one regression from dropping watchman as well.
now that i'm a maintainer, i will disable this semantic pull request business, haha!
we are working on upgrading the underlying
graphql-language-service-server
which addresses this problem, however there are a few breaking changes ingls-server@2.4.x
and at least one regression from dropping watchman as well.now that i'm a maintainer, i will disable this semantic pull request business, haha!
I'm totally happy to fulfill the tool's requirements. Do I just add another commit with "feat" in the message?
Totally love the plugin -- the best out there that I could find. Will be awesome to see the upgrade to the next language server :-)
looks good to go, thank you @twmillett !
As a small workaround for Does not work when updating the schema and from this suggestion:
This PR proposes a command to restart the gql plugin. So, instead of restarting vs-code, a user can do ctrl-shift-p to pull up the Command Palette and type something like "graphql restart".
It's not great, but as the cantiero indicates, "Beats restarting the editor for sure".