Transforms allow for taking your existing OpenAPI spec and modifying it in some way before we generate your SDKs.

If an OpenAPI transform doesn’t change your spec, we now throw a diagnostic so that you know the transform is superfluous, and can be removed.

Transforms let you reshape your OpenAPI spec during SDK generation without editing the source file. Define transforms in your stainless.yaml config file, and Stainless applies them automatically.

Use transforms to:

• Fix incorrect types in auto-generated specs

• Add missing required fields while you fix the source spec

• Rename properties to avoid language conflicts

• Add Stainless metadata (x-stainless-naming, x-stainless-skip)

• Remove incorrect defaults or deprecated fields

Read more about transforms in our deep-dive post or the transforms guide.

The CLI generator now supports automatic pagination for paginated endpoints. In interactive terminals, results are sent to the user’s configured pager (such as $PAGER or less), with additional pages loaded as the user scrolls.

When output is piped to another tool or run in a non-TTY environment, results are streamed directly to standard output. The CLI also respects HTTP 429 (too many requests) responses and applies server-defined backoff policies, automatically throttling page requests to comply with backend rate limits.

Stainless generated C# SDKs now support .NET Standard 2.0 out-of-the-box.

This means you can use the SDKs:

• On Windows without installing a runtime

• In UWP, Azure Functions 1.x, Xamarin, and many other runtimes that implement .NET Standard 2.0

• In legacy codebases