This is very nice, but shouldn't it be integrated on the GQL server-layer, rather than in the react client?
I would expect this to be valuable where the API is, i.e. for developers trying to access and utilise your GraphQL service, you would offer an extra RESTful endpoint on that API (e.g. in Expres, Koa, or whatever you're using) that brings up this schema explorer, so they know what to develop against.
But if I understand correctly, you're expecting people to add this to their existing (React) client apps instead?
👋 Hi Patrick! The guy who built Birdseye here 😃.
Our intention with Birdseye is to make it compatible with other GraphQL tools like GraphiQL and GraphQL playground. We felt that releasing it as a react component made it more portable for other members of the community to integrate into their own projects. We are planning to make PRs to some of these libraries integrating Birdseye.
We also published a pure JavaScript version called graphql-birdseye-core (documentation coming soon) which can be used in even more places like a Vue, Angular, or even as a standalone endpoint via Express, etc.
This is very nice, but shouldn't it be integrated on the GQL server-layer, rather than in the react client?
I would expect this to be valuable where the API is, i.e. for developers trying to access and utilise your GraphQL service, you would offer an extra RESTful endpoint on that API (e.g. in Expres, Koa, or whatever you're using) that brings up this schema explorer, so they know what to develop against.
But if I understand correctly, you're expecting people to add this to their existing (React) client apps instead?
👋 Hi Patrick! The guy who built Birdseye here 😃.
Our intention with Birdseye is to make it compatible with other GraphQL tools like GraphiQL and GraphQL playground. We felt that releasing it as a react component made it more portable for other members of the community to integrate into their own projects. We are planning to make PRs to some of these libraries integrating Birdseye.
We also published a pure JavaScript version called graphql-birdseye-core (documentation coming soon) which can be used in even more places like a Vue, Angular, or even as a standalone endpoint via Express, etc.
Ah, that makes sense. Certainly the core version could then already be used for server-side integration. Thanks for clarifying!
If you are willing to contribute a server-side version, I think the community would really benefit from it! 🙂