GitHub repo for @kbrandwijk/swagger-to-graphql ?

[mohawk2]

I found yarax's one a while ago, and used it to start https://github.com/graphql-perl/GraphQL-Plugin-Convert-OpenAPI . The t directory there contains all the corpus it handles so far, several of which broke yarax's version. I would be interested to see where yours is at, and/or to unify these projects with something a bit more declaratively OpenAPI -> GraphQL-y.

[kbrandwijk]

Mine lives here: https://github.com/supergraphql/swagger-to-graphql. The only thing I changed in my fork is being able to pass in the endpoint. There's an open PR on the main repo to move back to it when it's merged.

[fabien0102]

@kbrandwijk If you talk about this PR yarax/swagger-to-graphql#50 I think that we can go back to the official npm package here 😉

[kbrandwijk]

Not exactly, the other big change was about the viewer field that I didn't want to use (as it was more geared towards Relay, and the Graphcool/Prisma way wasn't). It is mentioned here: yarax/swagger-to-graphql#49 (comment), and didn't get approval from @yarax.

[yarax]

@kbrandwijk we got rid of viewer as well, that was just done in another place, can we maybe merge libraries?

[kbrandwijk]

@yarax Sounds good to me. I'll try and switch graphql-binding-openapi to your swagger-to-graphql over the coming days and see if it produces the same output. If so, I'll make the switch.

[yarax]

great, thank you

[Urigo]

Thank you for reporting.

In the last few months, since the transition of many libraries under The Guild's leadership, We've reviewed and released many improvements and versions to graphql-cli, graphql-config and graphql-import.

We've reviewed graphql-binding, had many meetings with current users and engaged the community also through the roadmap issue.

What we've found is that the new GraphQL Mesh library is covering not only all the current capabilities of GraphQL Binding, but also the future ideas that were introduced in the original GraphQL Binding blog post and haven't come to life yet.

And the best thing - GraphQL Mesh gives you all those capabilities, even if your source is not a GraphQL service at all!
it can be GraphQL, OpenAPI/Swagger, gRPC, SQL or any other source!
And of course you can even merge all those sources into a single SDK.

Just like GraphQL Binding, you get a fully typed SDK (thanks to the protocols SDKs and the GraphQL Code Generator), but from any source, and that SDK can run anywhere, as a connector or as a full blown gateway.
And you can share your own "Mesh Modules" (which you would probably call "your own binding") and our community already created many of those!
Also, we decided to simply expose regular GraphQL, so you can choose how to consume it using all the awesome fluent client SDKs out there.

If you think that we've missed anything from GraphQL Binding that is not supported in a better way in GraphQL Mesh, please let us know!