Skip to content

Version Packages #1330

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 8, 2025
Merged

Version Packages #1330

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 0 additions & 13 deletions .changeset/fix-operationid-starting-with-number.md
View file
Open in desktop

This file was deleted.

19 changes: 0 additions & 19 deletions .changeset/loud-dancers-shake.md
View file
Open in desktop

This file was deleted.

30 changes: 30 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,35 @@
# swagger-typescript-api

## 13.2.8

### Patch Changes

- [#1326](https://github.com/acacode/swagger-typescript-api/pull/1326) [`99b5f50`](https://github.com/acacode/swagger-typescript-api/commit/99b5f5055bfdf207d9dfe316ef8ff2490d474443) Thanks [@thejhh](https://github.com/thejhh)! - Fix TypeScript generation failure for operationIds starting with numbers

**What:** Fixed an issue where operationIds starting with numbers (e.g., "123getUser") would cause TypeScript generation to fail due to invalid identifier names.

**Why:** OperationIds that start with numbers are not valid JavaScript identifiers, causing syntax errors in the generated TypeScript code.

**How:** Modified the template logic to quote property names for invalid identifiers. OperationIds starting with numbers are now generated as quoted properties (e.g., `"123GetUser": ...`) instead of unquoted invalid identifiers.

This resolves GitHub issue #952.

- [#1008](https://github.com/acacode/swagger-typescript-api/pull/1008) [`c2d3e6a`](https://github.com/acacode/swagger-typescript-api/commit/c2d3e6aab97d57a8cd7788c8e2adc909bcf26e1f) Thanks [@frazar](https://github.com/frazar)! - Fix handling of FormData inputs in Fetch HTTP client

Previously, when users passed a `FormData` object directly to the Fetch
client's `multipart/form-data` formatter, it would incorrectly attempt to use
`Object.keys()` on the FormData instance, which returns an empty array. This
caused the FormData to be processed incorrectly.

The fix adds a type check to return FormData instances unchanged, allowing
users to have full control over FormData construction when needed whilst
maintaining backwards compatibility for object inputs. This aligns the Fetch
client behaviour with the existing Axios client implementation.

This resolves issues where users needed to send multipart requests with
multiple entries for the same key, which is only possible with direct FormData
manipulation.

## 13.2.7

### Patch Changes
Expand Down
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "swagger-typescript-api",
"version": "13.2.7",
"version": "13.2.8",
"description": "Generate the API client for Fetch or Axios from an OpenAPI Specification",
"homepage": "https://github.com/acacode/swagger-typescript-api",
"bugs": "https://github.com/acacode/swagger-typescript-api/issues",
Expand Down