docs: Clarify how to use tRPC in Next.js Route Handlers #5728
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #N/A
🎯 Changes
Make the example code clearer on how to use tRPC in Next.js App Router Route Handlers.
Why?
The existing example code is already correct, however it could cause some confusion, since it uses the
const x = y => z
syntax (which is not immediately clear that the function returnsz
especially for JavaScript beginners).In the Next.js Discord server, there has been at least one help question where the user tries to do this
and it doesn't work because the returned value of
fetchRequestHandler
is not returned again.This PR slightly improves the example code so that the need to re-return the value is made more apparent.
✅ Checklist