Implementation question regarding editable generated files like resolver
- Dominant language
- Go
- Stars
- 10.8k
- Forks
- 1.3k
- Avg merge
- 2d 36m
- Merged PRs (30d)
- 26
Description
How is the editable functionality achieved for resolver?
I'm writing a custom protoc plugin and would love to be able to edit the output.
There doesn't seem to be any temp/lock files associated with generating the resolver.
I was wondering could anyone give an overview of how this functionality that allows file edits to be persisted across further generate re-runs? Or just point to where in the code roughly it happens
Contributor guide
Research direction
Look at the gqlgen code generation process, particularly how the resolver is generated and where editable files are handled. Start by examining the codegen package and the resolver generation logic. The goal is to understand the mechanism that allows edits to persist across re-runs, then document it for custom protoc plugin authors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devtools
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100