fix(docs): Mark the GET function callback as async #12750
Closed
+1
−1
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.
☕️ Reasoning
The issue was that Next.js expects route handlers to return a Promise (i.e., work asynchronously). Without marking the function as async, TypeScript detects a mismatch where the expected parameter type (which relies on a Promise) doesn't align with a synchronous return value. Adding async ensures the function returns a Promise, resolving the type error.
🧢 Checklist
🎫 Affected issues
📌 Resources