Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reverse rejoiner #88

Open
timburks opened this issue Sep 26, 2019 · 1 comment
Open

Reverse rejoiner #88

timburks opened this issue Sep 26, 2019 · 1 comment

Comments

@timburks
Copy link

timburks commented Sep 26, 2019

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).

@sheepdreamofandroids
Copy link
Contributor

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 free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants