graphql-editor VS federation

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

I feel like we ran into this recently at work but not with custom scalars etc. My colleague raised an issue for it. Hope this helps in some way.

as per the Github issue here. However I have trouble understanding this statement. Why can't the gateway pick and choose which input fields are routed to each subgraph? Isn't it the responsibility of the supergraph SDL and the gateway to do exactly this, this same way it does for entities? What limitations are there that make merging input types using the union strategy not viable?

Federation comes with its own specification and directives as part of it which helps people to define all of the relations between multiple GraphQL entities so that the Apollo Gateway can combine them all together without having to modify the GraphQL gateway and also functions like __resolveReference which helps in resolving an entity with its reference as specified by the directives.