Closed kengu closed 3 years ago
@ejona86 / @mit-mit This is my first PR to grpc-dart, so I hope I've followed all steps required for a review.
@mraleph Do you have time to look at this PR?
@kengu I will try to find some time, maybe next week.
@kengu I will try to find some time, maybe next week.
Hi @mraleph, I'm currently testing this branch with a git-ref in pubspec.yaml, and it works as intended. I hope you find some time to make a review :pray:
@mraleph I see that dart format checks fails now. Running dart format --output=none --set-exit-if-changed .
locally does not fail. It seems like the format error was introduced by one of the merges from master into my branch about 12 days ago, see https://github.com/grpc/grpc-dart/actions/workflows/dart.yml
Trying to address it here: https://github.com/grpc/grpc-dart/pull/504
d'oh. Now there is another problem with envoy
package not available anymore through https://dl.bintray.com/tetrate/getenvoy-deb - unfortunately I don't think I will have enough time left in the day to fix this today. I will pick this up when I am back from sommerferien 🌴 in few weeks.
@kengu could you try rebasing on top of master? I think CI should be green now.
Thanks for the PR. Merged.
@mraleph Do you know when the next release of grpc-dart to pub.dev is scheduled? I still need this before I can publish my own packaged that depends on this change.
Released 3.0.1
This PR resolves #135.
Background Servers can return additional error information as
*Custom-Metadata
inTrailers
. These are not exposed inGrpcError
making it practically impossible to implement typed exception handling inClientInterceptor
s. Exposing trailers in error objects is supported in other implementations like csharp, and examples in the wild depends on custom trailers to communicate error information.Tests A new test "Call should throw with custom trailers" is added to verify that custom headers only are exposed.