Example that illustrates modular typeDef and resolvers file organization

[jboothe]

This example illustrates how one could organize typeDef and resolver files in any manner and merge them using merge-graphql-schemas.
Closes #136
Closes #214

[jboothe]

@marktani In my haste, I submitted this PR on master. Would you prefer I submit it as a feature branch?

[corydeppen]

Compiling a project with tsc using this approach fails to include the .graphql files, which causes a run-time error Specified query type "Query" not found in document. I was wondering what your approach might look like to ensure the .graphql files are included in the output directory so they're available to fileLoader.

Based on the response in Urigo/merge-graphql-schemas#119, it seems like building for production using .graphql files hasn't been explored yet or it may be an exercise left for the library consumer to figure out.

/cc @cfnelson

[timsuchanek]

Thanks for the PR @jboothe ! @corydeppen yes, we're for example using this in a graphql server we're running:

  "scripts": {
    "build": "rimraf dist && tsc && copyfiles -u 1 src/**/**/*.{graphql,json} dist/",
  }

Feel free to do another PR to add that :)

[cfnelson]

@corydeppen Sorry for not noticing your comment here earlier. Just wanted to thank you for cc'ing me 🙌 ! It's been quite helpful in giving me more context and clarifying some of my own confusion with issues/questions some users have raised on merge-graphql-schemas.

The fileLoader could definitely be improved further as there are a few issues around it depending on your server env/build process etc. currently it is up to the end user to ensure the .graphql files are available to you in your production bundle. I suspect this might be a common pitfall for some users who have builds that use tree-shaking and are not including the .graphql files.

Always love to see/hear how people are consuming the merge-graphql-schemas library. So please feel free to open an issue and let us know your use cases/pain-points and how we could potentially improve the pkg. Always looking for more contributors as well!