How to handle multiple schemas defining different Query types

[AlecAivazis]

Right now, the merging algorithm assumes that both schemas follow the convention of naming the root query type Query. This is an assumption that can lead to confusing outcomes if one of the schemas doesn't have Query defined but instead opted to have their root fields defined on something else.

With this in mind, Query shouldn't be handled like the other types in a schema. Instead, we want to merge the root types even if they dont have the same name so that they are all available at the root of the resulting API.

[jasondeutsch]

@AlecAivazis should this issue be closed or are their further requirements?

[AlecAivazis]

No, unfortunately this is still a problem. Let me add a description to the initial issue so it will be a bit more clear what I had in mind.