You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Send binary data with error details by @akshayjshah in https://github.com/bufbuild/connect-go/pull/329 So that proxies can translate between the Connect and gRPC protocols without a schema, we've changed the Connect protocol to include base64-encoded binary data with error details. Any code sending error details must now create details with connect.NewErrorDetail instead of anypb.New. For code unmarshaling error details, the connect.ErrorDetail type has changed from an interface to a struct with a more-ergonomic Value() method.
Note that we will not make breaking changes in minor releases after connect-go reaches v1.0. We anticipate a stable release around October of 2022, shortly after Go 1.19 is released.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
What's Changed
Breaking Changes
So that proxies can translate between the Connect and gRPC protocols without a schema, we've changed the Connect protocol to include base64-encoded binary data with error details. Any code sending error details must now create details with
connect.NewErrorDetail
instead ofanypb.New
. For code unmarshaling error details, theconnect.ErrorDetail
type has changed from an interface to a struct with a more-ergonomicValue()
method.Note that we will not make breaking changes in minor releases after
connect-go
reaches v1.0. We anticipate a stable release around October of 2022, shortly after Go 1.19 is released.Full Changelog: bufbuild/connect-go@v0.2.0...v0.3.0
This discussion was created from the release v0.3.0.
Beta Was this translation helpful? Give feedback.
All reactions