You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All SDKs (TypeScript v0.6.0, Python v0.5.0, Go v0.5.0) now use a consistent `params` field name for request bodies instead of operation-specific names like `destinationCreate` or `destinationUpdate`.
67
+
All SDKs (TypeScript v0.6.0, Python v0.5.0, Go v0.5.1) now use a consistent `params` field name for request bodies instead of operation-specific names like `destinationCreate` or `destinationUpdate`.
68
68
69
69
:::note[Examples]
70
70
Examples shown in TypeScript, but changes apply to all SDKs (TypeScript, Python, Go).
All SDKs (TypeScript v0.6.0, Python v0.5.0, Go v0.5.0) response structure has changed. Paginated responses (like events lists) now return data directly on the response object instead of nested under a `result` property.
123
+
All SDKs (TypeScript v0.6.0, Python v0.5.0, Go v0.5.1) response structure has changed. Paginated responses (like events lists) now return data directly on the response object instead of nested under a `result` property.
124
124
125
125
:::note[Examples]
126
126
Examples shown in TypeScript, but changes apply to all SDKs (TypeScript, Python, Go).
Previously, all SDKs (TypeScript, Go, and Python) used `nextCursor`/`prevCursor` (or `next_cursor`/`prev_cursor` in Python) for pagination fields due to a shared overlay that renamed these fields to avoid Python's built-in `next()` function conflict.
172
172
173
-
With this release, we've separated the pagination overlay to be Python-specific. TypeScript v0.6.0 and Go v0.5.0 now use `next` and `prev` for pagination fields (both query parameters and response properties), matching the OpenAPI specification. Python v0.5.0 continues using `next_cursor` and `prev_cursor` consistently to avoid conflicts with Python's built-in `next()` function.
173
+
With this release, we've separated the pagination overlay to be Python-specific. TypeScript v0.6.0 and Go v0.5.1 now use `next` and `prev` for pagination fields (both query parameters and response properties), matching the OpenAPI specification. Python v0.5.0 continues using `next_cursor` and `prev_cursor` consistently to avoid conflicts with Python's built-in `next()` function.
174
174
175
175
:::note[Examples]
176
176
Examples shown in TypeScript, but changes apply to TypeScript and Go SDKs. Python SDK uses `next_cursor`/`prev_cursor` instead.
0 commit comments