OpenAPITools / OpenAPITools/openapi-generator
[BUG][typescript-fetch] "<" and ">" are getting rendered as < and > in GenericItemResponse.ts
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
Description
"<" and ">" are getting rendered as < and > in GenericResponseItem
openapi-generator version
5.3.1
Command line used for generation
-g typescript-fetch
additionalProperties=typescriptThreePlus=true,prefixParameterInterfaces=true
Example of generated GenericItemResponse.ts :
export interface GenericItemResponse {
/**
*
* @type {Array<MyType1> | Array<MyType2>}
* @memberof GenericItemResponse
*/
items: Array<MyType1> | Array<MyType2> | null;
/**
*
* @type {number}
* @memberof GenericItemResponse
*/
size: number;
}
export function GenericItemResponseFromJSONTyped(json: any, ignoreDiscriminator: boolean): GenericItemResponse {
if ((json === undefined) || (json === null)) {
return json;
}
return {
'items': Array<MyType1> | Array<MyType2>FromJSON(json['items']),
'size': json['size'],
};
}
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
Reproduce the issue with the reported typescript-fetch generator command and inspect the generated GenericItemResponse.ts output. Trace how the items type is rendered in the TypeScript fetch generator, then verify that angle brackets remain literal in both the JSDoc type and JSON conversion code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi, typescript
- Domain
- api, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100