Support multiple schemas #389
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vektah
force-pushed
the
multiple-schemas
branch
from
5982ca7
to
a230eb0
Compare
|
I like the idea and look good. Didn't have time to test it. I can avoid go bindata for schema generation now. Thanks. |
|
@vektah remind me to send to you a beer :) 🍻 |
|
Sorry i'm late but is there any plan for merging type definitions instead of simple concatenation ? Example : |
cgxxv
pushed a commit
to cgxxv/gqlgen
that referenced
this pull request
Mar 25, 2022
Support multiple schemas
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Not quite what was wanted in #383, but import syntax is still not in the spec and there are many other concerns around namespacing etc.
This basically just concatenates the files, but keeps file names and line numbers accurate.
related reading:
I have: