OpenAPITools / OpenAPITools/openapi-generator
[Req][typescript-angular]Renaming options? parameter in client API services.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
Description
The default options? parameter in generated client service files has the possibility of conflicting with request parameters
options?: {httpHeaderAccept?: 'application/json', context?: HttpContext}
openapi-generator version
7.0.0-SNAPSHOT
Suggest a fix/enhancement
Provide additionalProperties to edit the name as to prevent conflict
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 locating the generated TypeScript Angular client service files and the generator entry point that defines the default options? parameter. Trace how additionalProperties are passed into this generator and determine the expected configurable parameter name. Done means generated services can avoid conflicts with request parameters while retaining the current default behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100