v1.0.0-beta.3

v1.0.0-beta.3

• For documents, we'll now print the result of running gql on the operation node as a part of the Query/Mutation module.

v1.0.0-beta.2

v1.0.0-beta.2

• Added option to filter input objects based on usage in documents

v1.0.0-beta.1

Initial Beta build of the 1.0 release

v0.2.1

v0.2.1

• fixes an issue with parsing the response from a Mutation

Enum Maps + Int Support

Breaking changes

• GraphQL Int types are now represented as int on the Reason side as well. (#5)

New Features

• Added enumMap type + instance for each enum in the GraphQL schema. (#4 - see PR for more details)

Final(?) Build Fix...

I like said... I'm not great at this 😆. This should actually fix the build/release process.

v0.1.1 - Fixing the build

I'm new at this 😆. Initial version wasn't actually including the built assets in the published package, but I'm hoping that's fixed with this one. Also fixed a typo with __typename that basically broke everything. So, overall, this should be a pretty big improvement.

🎉Initial Release!

GraphQL Objects

For each GraphQL Object in the schema, an abstract ReasonML type will be created, alone with a module for that type with accessor methods for each field.

GraphQL Enums

For each GraphQL enum in the schema, a ReasonML polymorphic variant is created using[@bs.deriving jsConverter]. These variant types are returned when accessing enum fields in the Object type.

GraphQL Inputs

For each GraphQL input in the schema, a ReasonML Js.t type is created, along with a module which contains a make function for generating an object of that type. The idea is to be able to generate input objects that get passed to queries/mutations as variables - more work is to be done here for integration with projects like reason-apollo!

v0.0.1-beta.2

v0.0.1-beta.2

v0.0.1-beta.1

Testing release process