OpenAPITools / OpenAPITools/openapi-generator
[REQ] Typescript Optional parameter when using 'useSingleRequestParameter'
Open
Nobody has claimed this yet.
Enhancement: Feature
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
When a single request parameter is used it is never optional, even if all the request parameter's properties are. I guess that would be a nice improvement.
Furthermore it could be interessting to not generate an object wraper for single parameters?
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 tracing the TypeScript generator's handling of the useSingleRequestParameter option. Clarify whether the requested change covers optional single-parameter objects, removing their wrapper, or both; done should include agreed behavior and coverage for the affected generated signatures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100