Skip to content

Possible ambiguous GraphQL request logging #63

@ubiuser

Description

@ubiuser

Based on the gqlgen lifecycle example presented in https://github.com/99designs/gqlgen/blob/ddd825ef62f1fa7cbc0824c1696f72a3c67d78e0/graphql/handler.go#L45, multiple responses can be sent for the same subscription operation, which means

gh.AroundResponses(GqlLoggingMiddleware)
should probably use AroundOperations instead of AroundResponses to avoid multiple log lines for the same request.

Metadata

Metadata

Assignees

Labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions