Prisma1: Support multiple type definition files

[jferrettiboke]

What is the current behavior?

If I split my "types" and "enums" into two different files and add them to the graphcool.yml file and then I run graphcool deploy, I get an error saying ! Path must be a string. Received [ './enums.graphql', './types.graphql' ].

I am using Windows 10, Node.js v8.6.0 and graphcool@next exactly 0.7.0-beta.5 at this moment.

Please share the relevant part of your project (GraphQL schema, functions, permissions, ...) for easier reproduction

types:
  - ./types.graphql
  - ./enums.graphql

# More stuff...

What is the expected behavior?

It must deploy properly to the platform.

[marktani]

types is currently a field that accepts a string, not a list of strings. I don't see a problem with supporting multiple type definitions however, great feature request @jferrettiboke!

[kbrandwijk]

@marktani
https://github.com/graphcool/graphcool/pull/783/commits/cac28c0e93dad78ef00116e9ca6380c2a2a7dc95#diff-31d33b0cd5c67b89253567e956f53621R120???

[marktani]

Good point! Might be a mismatch in the used json schema then. @timsuchanek?

[jferrettiboke]

@marktani It is also on docs.

Examples

Referring to a single type definition file

types: ./types.graphql

Referring to multiple type definition files

types:
  - ./types.graphql
  - ./customResolver.graphql

[grahamb]

I understand this is coming in 1.0 (per #1328), but it's still documented as being possible right now.

Perhaps the documentation should be changed to reflect the current reality?

[marktani]

This feature has been added in version 0.10.1. Thanks for your feedback! 🙌

https://github.com/graphcool/framework/releases/tag/0.10.1