feat: v11 goals & suggestion box
Problem
> 🚀 v11 is available to use and ready for production: https://trpc.io/docs/migrate-from-v10-to-v11 Summary The main goal of v11 is to improve our own quality-of-life by removing v9-support as it makes the codebase very messy. Work will be done in the `next`\-branch Ideas welcome from the community of API-decisions you think we should revisit. We plan not to delete anything which hasn't previously been marked as `@deprecated` (if we rename, we'll do an alias) Discord chat: https://discord.com/channels/867764511159091230/1057652120473575505 Plan Before official alpha [X] Delete v9 support #3494 [X] Recover test coverage from the above -- it dropped down to 93% -- see https://app.codecov.io/gh/trpc/trpc/pull/3494 [x] Deprecate and rename: Remove `Proxy` from naming of functions. We have `Untyped` that is for the untyped. e.g: `createTRPCProxyClient` -> `createTRPCClient` #4932 [x] Look over all `@deprecated` and delete accordingly (#5026) [X] Move from using string paths to tuples in `react-query` [ ] Look if there are any open issues that we want to do that might entail breaking features [ ] Consider if we wanna do them or wait for v12 - maybe we start exporting some stuff specifically for plugins [x] Turn `TRPCError.cause` to `unknown` [x] #5188 [x] Once we've created a `@trpc/core`-package, we need to look at extensions using tRPC and make a way to extend tRPC for libraries - #5308 [x] #5210 [ ] Make sure things that are exported in `@trpc/client
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Implement v11 Migration and Feature Review Process
The transition from v10 to v11 has introduced several changes that require community input on API decisions and the removal of outdated support. The lack of a structured process for collecting suggestions and reviewing existing features has led to uncertainty regarding which features to keep or modify.
Awaiting Verification
Be the first to verify this fix
- 1
Create a Community Feedback Form
Develop a structured feedback form to collect community suggestions on API decisions and features that might need revisiting. This form should be accessible via the documentation site and linked in the Discord channel.
N/AN/A - 2
Review Open Issues for Breaking Changes
Conduct a thorough review of all open issues in the repository to identify any that may entail breaking changes. Document these issues and categorize them based on their impact and necessity for v11.
bashgit fetch origin && git checkout next && git checkout -b review-breaking-changes - 3
Establish a Feature Review Committee
Form a committee consisting of core contributors and community members to evaluate the suggestions collected from the feedback form and the identified issues. Schedule regular meetings to discuss and prioritize these suggestions.
N/AN/A - 4
Implement Suggested Changes
Based on the committee's discussions, implement the agreed-upon changes in the `next` branch. Ensure that all changes are documented and that any deprecated features are clearly marked.
bashgit commit -m 'Implement community suggestions for v11' && git push origin next - 5
Communicate Changes to the Community
Once changes are implemented, communicate the updates to the community through Discord and the documentation site. Provide a summary of changes and encourage further feedback.
N/AN/A
Validation
Confirm that the feedback form is live and accessible, review the meeting notes from the committee, and ensure that all implemented changes are reflected in the documentation. Monitor community feedback for additional suggestions.
Sign in to verify this fix
Environment
Submitted by
Alex Chen
2450 rep