Fix compatibility with graphql-core v3.2

See #83

Creating a new version instead of v0.9.2 because a test was failing so it may break things for some people.

Support for Graphene 3

Add support for Graphene 3.

BREAKING CHANGE

Graphene 2 is no longer supported. You can use v0.8, which will be maintained for fixes.

Support for graphene-django 2.7+

@juyrjola fixed a compatibility issue with the newest version graphene-django (2.7+) at #39.

v0.6.1

• Added the support of the latest graphene-django release (v2.6.0) - #32 by @dex4er
• Made the name fetching from resolver work for relay connections - #33 by @OmegaDroid

Support of objects in connections

• Optional inputs no longer raise an error when user provides null
• Fields having for input a type inheriting from InputObjectType no longer raise an error
• Dropped support for django 1.9, 1.10 and Python 3.4

Support of objects in connections

#22 added the support of objects and nested objects inside connection fields.

Allowing to pass objects as arguments, this will parse and pass as arguments (tuple):

['10', {'price': {'gte': '1000'}}]

For example, when implementing filter objects, like this:

input PriceRangeInput {
  gte: Float
  lte: Float
}

input ProductFilterInput {
  price: PriceRangeInput
}

type Query {
  products(filter: ProductFilterInput): ProductCountableConnection
}

Queried like this:

query CategoryProducts($id: ID!) {
  category(id: $id) {
    products(first: 10, filter: {price: {gte: 1000}}) {
      edges {
        node {
          id
        }
      }
    }
  }
}