apollo-tooling VS graphql-editor

Apollo is deprecating their tooling, best to go with GraphQL Code Generator.

Alternatively, you can use Apollo GraphQL or any dependency of your choice to make API request.

When you talk about GraphQL, one simply cannot forget GraphQL Tools irrespective of the architecture or stack you use. Initially developed by Apollo and then taken over by The Guild, GraphQL Tools provides you a very powerful set of utility functions to work with GraphQL which you can use in your services irrespective of whethere you are using something like Apollo Federation or Schema Stitching.

The Apollo CLI when combined with Federation does come with a lot of helpers to take care of things like pushing the schema, listing the services in the studio, doing codegen and so on though I am not currently sure why they are rewriting it again to Rust apart from the reasons as suggested here.

ApolloGraphql: https://apollographql.com

The tech stack I used for this site was: Prisma w/ GraphQL-Yoga / Apollo & GraphQL / Express / NextJS / MongoDB

This is great, thanks. I'm wondering if you still need to explicitly reference types, such as with Apollo's codegen where you would do something like useQuery or is it fully automatic like in the gif in the article?

https://github.com/apollographql/apollo-tooling#apollo-clientcodegen-output

aside from the ones mentioned graphql editor has a bunch of features that are helpful for testing like a click-out creator and a built-in mock backend for testing queries

I may be wrong, but something like graphqleditor is geared more towards setting up GraphQL API/server, in Supabase case, it's database - Postgres, is the server/API.

Show HN: Visual GraphQL Editor OSS\ (0 comments)

https://graphqleditor.com/ New version is available here