1.57.0
(fix): Snippets for examples that omit an optional request body now pass nil for the body
parameter instead of dropping the argument, which produced snippets that did not compile.
(feat): Add a respectOptionalRequestBody option. When enabled, an endpoint whose request body the API
does not require sends no body and no Content-Type header once the caller leaves that body out,
including when the request wrapper is passed with a nil Body. Examples that supply no body stop
rendering an empty body such as Body: &acme.RefundRequest{}. The option defaults to false, so
existing SDKs send exactly what they always have.
1.56.1
(fix): Fix the initial offset for offsetSemantics: item-index. Item-index offsets address records
rather than pages, so pagination now starts at 0 instead of 1, which previously skipped the
first record of every collection. This applies to both query-parameter and request-body offsets.
Page-index semantics continue to start at 1.
(fix): Fix offset pagination emitting code that does not compile. With offsetSemantics: item-index
and a step, the pager read results before declaring it (undefined: results), and the
offset increment now matches the page type (int, int64, float64). Endpoints whose offset
is a required (non-optional) query parameter also emitted an invalid assignment to a request
field (request.Offset := ...) under either offset semantics, and now seed the initial offset
from the request (next := request.Offset).
1.56.0
(feat): Add the enableRequestBodyPagination configuration option, which generates auto-pagination for
endpoints whose cursor or offset is a top-level request body property (e.g.
cursor: $request.cursor). These endpoints previously generated a regular method that returned
the response body, so the option defaults to false to preserve the existing return types.
Pagination configured with a nested request body property (e.g. cursor: $request.pagination.cursor)
remains unsupported.