Rikki Schulte
Rikki Schulte
Hey so! What does the roadmap for the rest of 3.x look like? I have some ideas for the programattic API and other feature improvements. Do you all mind if...
We should use atlassian changesets in this repo for easier publishing!
I apologize how neglected this repository has been! We have many co-maintainers who are all busy with work and maintaining other graphql ecosystem tooling. 🥵 We had planned on merging...
We have made many improvements to `codemirror-graphql` and the underlying language services since this version, including interface implements interface, variables completion, and more I also upgraded electron so that `yarn...
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically....
a starting point, based on https://github.com/graphql/vscode-graphql TODO: - [x] as with `vscode-graphql`, port to the latest `vscode-anguageserver-client` using `vscode-anguageserver-client/node` import - [x] fix embarassing package.json typos haha - [ ]...
I'm noticing @divyenduz 's original `vscode-graphql` package.json had pinned `dependencies` and I think I understand why. ^ versions when you're shipping shared libraries work pretty great. But for end consuming...
Massive optimization for multi-project users! Warning: this changes the cache lifecycle a lot, especially after config change. Might need some fine tuning 😆 I should add lots of tests actually....
## How it used to work and it could be this simple again or simpler! **Developing graphiql:** 1. clone the monorepo 2. run `yarn install` 3. run `yarn build --watch`...
because it's good for the earth 🌍 and the patience of contributors 😆 i wish you could use `paths-ignore` further down, to skip individual tasks note: i decided to upgrade...