MichalLytek / MichalLytek/type-graphql
Towards TypeGraphQL v2.0
@MichalLytek is already working on this.
Since Feb 8, 2023.
- Dominant language
- TypeScript
- Stars
- 8.1k
- Forks
- 672
- PR merge metrics
- No merged PRs in 30d
Description
## TypeGraphQL v2.0
The 2.0 release won't be a rewrite from scratch nor a breaking change in the existing API 👀
Basically, two main goals of this release are:
1) GraphQL v16 upgrade - this is a peer dependency, so it forces bumping version to a new major release ⚠️
2) fixes, features and cleanups that might break compatibility in some edge cases
The 1) is mostly done (#1331) however it might need some attention around examples that might not work properly or still need updating deps (e.g. Apollo Server v4).
About the rest, all is described in the changelog:
https://github.com/MichalLytek/type-graphql/blob/master/CHANGELOG.md#unreleased
We're also working with @carlocorradini on reviving the repo and tools configuration that went out-of-date since the project was born 5 years ago, like TSLint has died and Gulp is not used anymore. See the work on #1400.
This should allow external contributors to work on the codebase, implement other fixes and features.
The current state of the art is published as a beta release - `npm i type-graphql@next`:
https://www.npmjs.com/package/type-graphql/v/2.0.0-beta.1
Stay tuned for more info! 📻
PS No ETA yet, the beta releases are stable enough to be used by users.
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.
Assessment
This issue has not been assessed yet.