feat(client): accept preconfigured reqwest clients (#99)

[lightsofapollo]

Generated HTTP clients currently create their own reqwest transport, preventing callers from supplying TLS identities, trusted roots, proxy settings, or other client configuration. Add HttpClient::with_client(reqwest::Client) and, when middleware configuration is generated, with_client_and_config(client, ...) so HTTP and SSE requests use a caller-provided transport through the existing middleware stack.

Existing new(), Default, and with_config(...) signatures and defaults are preserved. Operations whose Rust names collide with the new constructors receive the existing numeric suffix; this is the only generated API compatibility caveat. No new runtime dependencies or configuration migrations are required.

Closes #99.

Validation:

• 720 all-feature nextest tests passed (7 skipped), plus doctests.
• Formatting, Clippy with warnings denied, and rustdoc with warnings denied passed.
• Generated runtime coverage exercises all four retry/tracing combinations, custom transport headers on HTTP and SSE requests, retry defaults and explicit retries, response limits, and operation-name collisions.
• Generated native and WASM client compilation passed.
• Anthropic and OpenAI compilation and schema round trips passed: 4,984 samples across 1,333 component schemas.
• All 56 corpus diffs contain the same constructor-only change in client.rs; models and dependency files are unchanged. The corpus manifest was refreshed and verified.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
openapi-to-rust	Ready	Preview	Oct 6, 2026 12:11am UTC