`graphql` signature diverges with standard graphql-js's one

[alexstrat]

The common signature of the function graphql in reactive-graphql differs from graphql-js.

With graphql-js the signature is roughly:

import { graphql } from 'graphql'; 

graphql(schema: GraphQLSchema, query: Source | string, context?: object)..

While with reactive-graphql:

import graphql from 'reactive-graphql'; 

graphql(query: DocumentNode, schema: GraphQLSchema, context: object) ..

Note the differences:

• the default import vs the "named" import
• query and schema arguments position are inverted
• the type of query is a string (or Source) in standard implementation and transformed in DocumentNode in the implementation while in reactive version it expects a DocumentNode directly
• context is optional

These differences are more or less minor, but wanted to know if they are intended or not, and thus if maintainer would be open to accepting a PR fixing this.

[alexstrat]

#6 can be added as divergent signature issue

[mesosphere-frontend-ci]

🎉 This issue has been resolved in version 3.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀