Luke Hodkinson 9ef31d849d Use maybe_queryset in DjangoFilterConnectionField ... In our projects we've found a need to inherit from DjangoFilterConnectionField in order to customize the queryset. When passing the queryset into "connection_resolver", an error was raised about "get_queryset" not existing. This is due to the assumption that the "base_manager" is always a manager. Using "maybe_queryset" resolves the issue.		2017-10-25 15:06:48 +11:00
..
debug	Code adapted to new resolver API	2017-07-28 09:43:27 -07:00
filter	Use maybe_queryset in DjangoFilterConnectionField	2017-10-25 15:06:48 +11:00
management	add indent support for graphql_schema command	2016-10-17 15:08:04 +08:00
rest_framework	Fixed flake	2017-09-01 00:52:57 -07:00
templates/graphene	Fix missing operation_name warning	2016-11-11 14:35:41 -05:00
tests	Code adapted to new resolver API	2017-07-28 09:43:27 -07:00
__init__.py	Updated dev version	2017-09-01 01:19:22 -07:00
compat.py	Fix compatibility with pypy	2017-06-23 12:48:32 +01:00
converter.py	Merge branch 'master' into fix-deprecation-warnings	2017-08-29 22:33:10 -07:00
fields.py	Code adapted to new resolver API	2017-07-28 09:43:27 -07:00
form_converter.py	Fixed all tests and flake issues	2017-07-24 23:42:40 -07:00
forms.py	Isolated Graphene Django in a new package	2016-09-17 16:31:17 -07:00
registry.py	Fixed all tests and flake issues	2017-07-24 23:42:40 -07:00
settings.py	Added RELAY_CONNECTION_MAX_LIMIT and RELAY_CONNECTION_ENFORCE_FIRST_OR_LAST settings	2017-04-15 02:15:17 -07:00
types.py	Code adapted to new resolver API	2017-07-28 09:43:27 -07:00
utils.py	Remove usages of deprecated field.rel	2017-08-14 14:01:04 +01:00
views.py	Updated graphiql version for new versions	2017-07-13 15:14:06 -07:00