search

connectrpc / connectrpc.com

Docs, governance, and RFCs for Connect: Protobuf RPC that works.
https://connectrpc.com
Apache License 2.0
15 stars 18 forks source link

Soften the language regarding error codes and HTTP codes with the Connect unary protocol #149

Closed jhump closed 4 months ago

jhump commented 4 months ago

None of the actual client implementations require that the Connect RPC code and the HTTP code are aligned (which is actually good since it allowed us to improve the mappings (#130) without it being a breaking change in practice).

This updates the language in the spec to make it a little more clear that a client should not necessarily treat it as an error if the Connect RPC code and HTTP status code do not agree. Admittedly, this is a rather subtle single word change. We could be even more explicit about what clients should do. But I think that might be better saved for a future document that provides a more behavior-focused spec (vs. protocol/wire-format-focused), which can also include guidance and requirements about other things that are today only codified in conformance test expectations.

vercel[bot] commented 4 months ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
connect ✅ Ready (Inspect) Visit Preview Mar 13, 2024 7:08pm