Prisma1: Support new description definitions from recent GraphQL spec

[kbrandwijk]

Descriptions have changed from comment to string literal blocks in the latest version of the GraphQL spec. I created this issue to track support for it with Graphcool.

More details here: https://github.com/graphql/graphql-js/pull/927.
Sangria is already up to date with it: https://github.com/sangria-graphql/sangria/issues/303.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[benjixx]

This feature would be really nice to document GraphQL types and also passing descriptions through to the actual app's GraphQL layer, so one would not need to duplicate types (just to add descriptions) in schema.graphql but instead could reuse them from datamodel.graphql.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[jgoux]

This feature would be awesome for codegen too.

For the database, it could create COMMENT on tables and columns.

We could also use these descriptions as labels for autogenerated forms using something like https://github.com/vazco/uniforms.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions.