feat(api): add list-indexes endpoint, remove sandboxes#50
Conversation
There was a problem hiding this comment.
Auto-generated SDK update. New list_indexes_collection endpoint and IndexEntryResponse/ListIndexesPageResponse models follow the established generator pattern; modules are registered correctly; sandbox endpoint/model removal is complete with no dangling references in src/; version bump is consistent across Cargo.toml and the configuration user-agent. No issues found.
|
|
||
| ### Removed | ||
|
|
||
| - Sandbox endpoints and their models (`sandboxes_api`, `Sandbox`, `SandboxResponse`, `CreateSandboxRequest`, `UpdateSandboxRequest`, `ListSandboxesResponse`, `DeleteSandboxResponse`), following their removal from the Hotdata OpenAPI spec. |
There was a problem hiding this comment.
super nit: the regeneration also dropped the public namespace field from WorkspaceDetail and WorkspaceListItem (and from their ::new() signatures), which is a breaking change for any consumer constructing or reading those structs. Worth calling out explicitly in the ### Removed section rather than folding it into the generic "Regenerated the client" line, so downstream users notice it. (not blocking)
Regenerated from the updated Hotdata OpenAPI spec (bumps the crate to
0.1.3).Added
list_indexes_collection(GET /v1/indexes) inhotdata::apis::indexes_api— lists indexes across every table in a database, scoped by theX-Database-Idheader — with theIndexEntryResponseandListIndexesPageResponsemodels.Removed
sandboxes_api,Sandbox,SandboxResponse,CreateSandboxRequest,UpdateSandboxRequest,ListSandboxesResponse,DeleteSandboxResponse), following their removal from the spec.Source: hotdata-dev/www.hotdata.dev#224