MichalLytek / MichalLytek/typegraphql-prisma
Disable generation of resolvers, but keep inputs, args & models.
- Dominant language
- TypeScript
- Stars
- 918
- Forks
- 130
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
I rarely use the generated resolvers as I usually have some business logic associated with each action (send emails etc), so generating all the resolvers is not required for me and probably takes up extra time when generating them.
**Describe the solution you'd like**
Some option to disable generating the resolvers.
I still require the inputs, args and models to be generated.
**Describe alternatives you've considered**
Can't do anything now I dont think?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the Prisma generator entry point and the code paths that emit resolvers, inputs, args, and models. Check how generator options are defined and exercised, then verify that the chosen option omits resolvers while retaining the other generated outputs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, typescript
- Domain
- backend-api-design, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100