Correct bad logic in optimization of single-object GraphQL endpoints #1120
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: #1112
The optimization implementation in #769 for single-object GraphQL queries (e.g.
device,circuit, as opposed to list queriesdevices,circuits) was incorrect - graphene-django-optimizer acts on querysets, not single objects, so we need to optimize a.filter(pk=pk)queryset instead of a.get(pk=pk)single object.It appears that we didn't have any unit test coverage for single-object GraphQL queries, so I've added a couple of them and verified that this issue is caught by one of the added tests.