-
Notifications
You must be signed in to change notification settings - Fork 491
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
import types of schema A into schema B #1
Comments
Hi @bsr203, thanks for looking into my project. My current plan is to not expose the schema data structures. The only way to create a schema is via the schema language. However, at some point I want to add a way to load multiple schema strings and have one schema import types from another schema. Then each schema still has its own namespace, but you can use them together as one big schema. Does that sound good to you? Do you need such a feature soon? |
Thank you for the quick response. What you described would be ideal, and I am in no rush :-) I just wanted to make sure it is considered so we may add it in the future without much of breaking the existing implementation. Do you want to keep this open till it is implemented? Thank you for all your effort on this. |
Yes, we can keep it open. I've changed the title accordingly. |
Just adding reference to an approach I saw. I currently modularize the schema by exporting the schema of the module and concatenate before pass to |
Happy to hear that! String concatenation sounds like a very clear and simple way of implementing modularization. Do you see any potential limitations? |
not really, it works great for me as the order of types within schema doesn't matter. Also, namespacing is not supported by graphql. There been need for this, but for the moment, we are good :-) |
Cool, I'll close this issue. Maybe I'll even replace |
Fixed failed tests and restored `language/parser` and `testutil` packages
Limit the number of concurrent list nodes processed
Expose selected fields in context
Thank you for more idiomatic graphql option for go.
I am currently using https://github.com/graphql-go/graphql, though it is incredibly verbose, I could structure the schema so it is kept at module level.
I see one thread in
graphql-js
regarding the same, in which lee saysgraphql/graphql-js#223
I wonder what is the best approach you propose with this library. Any plan for incrementally building the schema by registering the graphql schema and resolve functions for isolated modules ?
thanks again for providing this library.
The text was updated successfully, but these errors were encountered: