Netflix / Netflix/dgs-codegen

feature: Prefix type names

Open
#323 6 comments 11 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

good first issue
Dominant language
Kotlin
Stars
217
Forks
116
PR merge metrics
No merged PRs in 30d

Description

For example, given the schema:

interface A {
  id: ID!
}

type B implements A {
  id: ID!
  b: String!
}

With a prefix of GQL_, would generate:

  • interface GQL_A
  • class GQL_B implements GQL_A

This would help when converting between database, RPC, and GraphQL objects sharing the same name for example

I know #21 and #132 exist, would a PR in the (distant) future be OK?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review related issues #21 and #132 before defining the approach. Use the schema example in this issue to trace how interface and type names are generated, including implemented interfaces. Done means a configurable prefix such as GQL_ is applied consistently to the generated names.

Written by the indexing model from the issue text.

Assessment

Tech stack
graphql, kotlin
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.