MichalLytek / MichalLytek/typegraphql-prisma
Complexity plugin support
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 918
- Forks
- 130
- PR merge metrics
- No merged PRs in 30d
Description
@MichalLytek I have been playing around with the code base and have been testing two new features that might be nice in typegraphql-prisma.
- Complexity plugin support
- Default value for `take` (required to properly determine complexity)
Together these can prevent memory overflow high CPU utilization by limiting how complex queries can be which is extremely useful when you have large databases.
_Originally posted by @wSedlacek in https://github.com/MichalLytek/typegraphql-prisma/issues/1#issuecomment-672975188_
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are identified. Start by clarifying the intended Complexity plugin integration and the default `take` behavior for generated TypeGraphQL/Prisma resolvers. Done should include defined query limits and validation that complex queries are constrained.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, typescript
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100