You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 16, 2024. It is now read-only.
I think it would be useful to be able to analyze a GraphQL schema and produce a set of .proto files describing services that, when implemented, could be stitched together by Rejoiner to implement the specified schema. I'm not sure that all possible GraphQL schemas could be supported by this, but even a subset could be useful (particularly if the analyzer also generated warnings about what was unsupportable).
The text was updated successfully, but these errors were encountered:
The problem with that is that there are so many possible solutions: each field is a potential join with another grpc service. It is really up to you to decide which data belongs together.
Also, the GraphQL schema doesn't carry any type info, so there just isn't enough data to create proto files.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I think it would be useful to be able to analyze a GraphQL schema and produce a set of .proto files describing services that, when implemented, could be stitched together by Rejoiner to implement the specified schema. I'm not sure that all possible GraphQL schemas could be supported by this, but even a subset could be useful (particularly if the analyzer also generated warnings about what was unsupportable).
The text was updated successfully, but these errors were encountered: