Name and Version
0.46.1
What steps will reproduce the bug?
- Open open_api_core.yaml
- Check the
display_name, description, intro fields on Application, Model, ToolSet, Interceptor (and their *Data variants)
- It's defined as $ref to LocalizedValue: { localeMap, plainValue }
- Generate TS SDK from this spec — display_name becomes { localeMap?, plainValue? }
What is the expected behavior?
display_name, description and intro fields should be typed as a plain string or a locale map (e.g. { "en": "text" }), since that's what core actually returns. In OpenAPI this should be oneOf: [string, object], not a ref to LocalizedValue.
What do you see instead?
display_name, description and intro fields is typed as { localeMap, plainValue } object, which doesn't match the real response and produces wrong types in the generated SDK.
Also inconsistent: ExternalService uses plain string for the same kind of field, while other schemas use LocalizedValue.
Additional information
No response
Name and Version
0.46.1
What steps will reproduce the bug?
display_name,description,introfields on Application, Model, ToolSet, Interceptor (and their *Data variants)What is the expected behavior?
display_name,descriptionandintrofields should be typed as a plain string or a locale map (e.g. { "en": "text" }), since that's what core actually returns. In OpenAPI this should beoneOf: [string, object], not a ref to LocalizedValue.What do you see instead?
display_name,descriptionandintrofields is typed as { localeMap, plainValue } object, which doesn't match the real response and produces wrong types in the generated SDK.Also inconsistent: ExternalService uses plain string for the same kind of field, while other schemas use LocalizedValue.
Additional information
No response