Add support for multiple response types in the generated client, including handling JSON deserializable types, empty bodies, streams of bytes, and upgraded connections.
This change addresses the following issues:
- Multiple response types not supported (#344)
- Path to GitHub client (#395)
Generated methods return `ResponseValue<reqwest::Upgrade`, which may be
passed to a websocket protocol implementation such as
`tokio_tungstenite::WebSocketStream::from_raw_stream(rv.into_inner(), ...)`
for the purpose of implementing against the raw websocket connection, but
may later be extended as a generic to allow higher-level channel message
definitions.
Per the changelog, consumers will need to depend on reqwest 0.11.12 or
newer for HTTP Upgrade support, as well as base64 and rand if any
endpoints are websocket channels:
```
[dependencies]
reqwest = { version = "0.11.12" features = ["json", "stream"] }
base64 = "0.13"
rand = "0.8"
```
Co-authored-by: lif <>
- add the start of a client support crate
- add support for pre/post request hooks with consumer-specific data
- suggest type names for parameter and response types in case those
types are unnamed
- handle more reference types by resolving them properly
- improve optional parameter generation
Geoffrey Garrett
Adam Leventhal
Joshua M. Clulow
John Vandenberg
Everett Pompeii
Dillen Meijboom
Artem Medvedev
liffy