docs: change API route example file extension to .ts and add JS example with switcher prop #83044
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.
For Maintainers
What?
Changed the API route example in the documentation to use
.ts
file extension for the TypeScript example since it uses TypeScript types.Added a JavaScript example with
.js
extension using theswitcher
prop to provide both TypeScript and JavaScript variants in the docs.Why?
The existing example used a
.js
extension but included TypeScript-specific type annotations which is inconsistent and could confuse users.Providing both TypeScript and JavaScript examples improves clarity and usability, catering to a broader audience.
How?
pages/api/hello.ts
.pages/api/hello.js
using theswitcher
property.