ardatan / ardatan/graphql-tools
advise against using schema wrapping
- Dominant language
- TypeScript
- Stars
- 5.4k
- Forks
- 830
- Avg merge
- 10h 59m
- Merged PRs (30d)
- 45
Description
`wrapSchema` usually results in bad performance as it generates a proxy schema.
From looking at https://www.graphql-tools.com/docs/schema-wrapping it is unclear to me which use-cases I might wanna use `wrapSchema` and what I should prefer to use instead?
The page should start with an disclaimer and guidance on what to use, preferably with real-world examples.
E.g. For use-case X use `wrapSchema`, otherwise use Y.
Contributor guide
Research direction
Start by reviewing the schema-wrapping documentation page linked in the issue and the `wrapSchema` API guidance. Done means the page opens with a performance disclaimer, explains when `wrapSchema` is appropriate, recommends alternatives for other cases, and includes real-world examples.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, typescript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100