v0.3.0

Release v0.3.0 improves the streaming API for bidi and server streaming calls, renames ConnectError to ConnectException to match JVM conventions, and supports passing a separate OkHttp client for use in streaming calls.

What's Changed

API Improvements

• Rework ConnectError to ConnectException by @jzbrooks in #120
• Improve API for bidi and server streaming calls by @pkwarren in #130

Other changes

• Allow separate client for streaming calls by @pkwarren in #128
• Update dependencies and fix javadoc artifacts by @pkwarren in #127
• Use a more specific type for error callbacks by @jzbrooks in #132
• Treat warnings as errors in tool and library code by @jzbrooks in #133

New Contributors

• @jzbrooks made their first contribution in #120

Full Changelog: v0.2.0...v0.3.0

API Updates

com.connectrpc.http.HTTPResponse

• error renamed to cause.

com.connectrpc.BidirectionalStreamInterface

• resultChannel renamed to responseChannel. The channel now returns the response messages from the stream (canceling the channel with a ConnectException if an error occurs).

com.connectrpc.ClientOnlyStreamInterface

• receiveAndClose now returns the response message instead of a message wrapped in the ResponseMessage type. The method will throw a ConnectException on error.

com.connectrpc.ConnectError

• Renamed to ConnectException.
• Changed to extend Exception instead of Throwable.

com.connectrpc.ResponseMessage.Failure

• error renamed to cause.

com.connectrpc.ServerOnlyStreamInterface

• resultChannel renamed to responseChannel. The channel now returns the response messages from the stream (canceling the channel with a ConnectException if an error occurs).

com.connectrpc.StreamResult.Complete

• error renamed to cause.