Use graphql.HasOperationContext in arangodb assembler #1659
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.
Description of the PR
It seems we're not entering the logic to determine what graphql fields are present in some of the arangodb methods. This is because we are checking
ctx.Value("graphql").(graphql.OperationContext)
which isn't actually present. This is because the operation context is stored using the valueoperation_context
as seen here. Instead of doing this logic here, we can just call theHasOperationContext
function provided by thegqlgen
library.PR Checklist
-s
flag togit commit
.make generate
has been runcollectsub
protobuf has been changed,make proto
has been run