99designs/gqlgen

Can I have a common resolver for multiple interface implementations?

Open

#3,725 opened on Jun 6, 2025

View on GitHubContributor guide
 (1 comment) (1 reaction) (0 assignees)Go (1,250 forks)auto 404
help wanted

Repository metrics

Stars
 (10,737 stars)
PR merge metrics
 (PR metrics pending)

Description

I have a schema like this:

interface Result {
    title: String!
    description: String! @goField(forceResolver: true)
}

type Book implements Result {
    title: String!
    description: String! @goField(forceResolver: true)
    author: String!
    # ... other fields
}

type Article implements Result {
    title: String!
    description: String! @goField(forceResolver: true)
    section: String!
    # ... other fields
}

When I run the generator, it generates bookResolver and articleResolver, each one with its description field resolver. Is there a way I can generate a common resultResolver for them?

Contributor guide

Research direction
Explore gqlgen's code generation logic for interface resolvers. Look at the templates that generate separate resolver types for each implementation and investigate if they can be modified to generate a common resolver interface or type that can be shared across implementations. Consider the implications on the generated code and performance.
Tech stack
go
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60