How to handle/use the generated datafetchers?
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 217
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Description
Hi there!
I've started to use DGS in a Spring Boot project and so far it works great. When generating code using the "codegen" it also creates "example" data fetchers (Can this be turned off?). What's a good/recommended pattern to use/extend those without overwriting them on the next codegen run? Extending the classes? Copy the generated classes? Disable the creation of the "datafetchers"?
Thanks in advance.
Best regards
ML
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the codegen handling for example data fetchers and the available configuration documented for generated output. Clarify whether generation can be disabled and which extension or preservation pattern is supported. Done means documenting a recommended workflow that remains safe across subsequent codegen runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin, spring-boot
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100