[feature request] GraphQL Schema stitching

[morficus]

In order for this Serverless component to be usable for anything more than a hobbyist project, it should support schema stitching out of the box.

As GraphQL projects and codebases grow, schema management becomes critical. The best way to manage a schema at scale is to split it up into multiple smaller files and then "stitch" them during the build/deploy process.

So in order to just specifying a single schema.graphql file, it would be awesome if we could specify either (a) an array/list of files OR (b) a directory.

This feature is also supported by the serverless-appsync-plugin plugin.

[vicary]

As far as I can understand, serverless component is overly simplified the current plugin model. Which means adding any functionality is highly not likely.

I had an approach, albeit not complete enough for me to migrate from the serverless-appsync-plugin, involving the generation of the whole serverless.yml, along with mapping templates and schema stitching, in a prebuild process.

This kinda defeated the purpose of serverless components, but at least let me move away from the cumbersome CloudFormation.

[morficus]

ping: @eahefnawy -- is create a GitHub issue the right way to submit a feature request or is there a better way?