Skip to content

Fix for custom resolve support for DjangoFilterConnectionField (issue #30) #80

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 3 commits into from
Closed

Fix for custom resolve support for DjangoFilterConnectionField (issue #30) #80

wants to merge 3 commits into from

Conversation

drakon
Copy link

@drakon drakon commented Dec 26, 2016

See issue #30 for motivation and discussion.

Added the fix mentioned by @krailler (#30 (comment)).

@coveralls
Copy link

coveralls commented Dec 26, 2016 •
edited
Loading

Coverage Status

Coverage decreased (-11.7%) to 80.764% when pulling 7cbd5e2 on drakon:master into 4246cea on graphql-python:master.

@coveralls
Copy link

coveralls commented Dec 26, 2016 •
edited
Loading

Coverage Status

Coverage decreased (-11.7%) to 80.764% when pulling 121f943 on drakon:master into 4246cea on graphql-python:master.

@drakon
Revert "Remove qs"
6a7a097 
This reverts commit 121f943.
@coveralls
Copy link

Coverage Status

Coverage decreased (-11.7%) to 80.764% when pulling 6a7a097 on drakon:master into 4246cea on graphql-python:master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage decreased (-11.7%) to 80.764% when pulling 6a7a097 on drakon:master into 4246cea on graphql-python:master.

@pchinea pchinea mentioned this pull request Dec 30, 2016
Merged
@drakon drakon closed this Dec 30, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@drakon @coveralls