feat: Prepare request query and body in Server Routes according to route types
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 3.3k
- Forks
- 214
- Avg merge
- 13h 22m
- Merged PRs (30d)
- 18
Description
🆒 Your use case
I already use generics in route definitions, so other parts know what query and body API router expects.
Issue in Nuxt and links to issues in other projects: https://github.com/nuxt/nuxt/issues/23009
🆕 The solution you'd like
I'd like dev tools to read this annotations and prepare query and body form with expected structure.
🔍 Alternatives you've considered
No response
ℹ️ Additional info
No response
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.
Research direction
Start by reading the linked Nuxt issue and tracing how Server Routes are defined with query and body generics. Done means devtools can derive those annotations and present request query and body forms with the expected structure; the issue names no files or tests, so the relevant entry points must first be located.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100