-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement Twirp protocol v7 #63
Comments
Thanks, @marioizquierdo. This has been on my list for a bit. I'm going to try to take a look soon |
btw, I really like the twirp-elixir implementation. I'm surprised how well it maps all the Twirp concepts to the Elixir style 💯 |
fishtreesugar
added a commit
to fishtreesugar/twirp-elixir
that referenced
this issue
Oct 11, 2021
part of Twirp protocol v7 keathley#63
zillou
added a commit
to zillou/twirp-elixir
that referenced
this issue
Jan 14, 2022
part of Twirp protocol v7 keathley#63 Co-authored-by: FTS <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Changes required to implement the new protocol:
resource_exhausted
should map to 429 (instead of 403).See Protocol v7 differences and the Go implementation v7.0.0 release notes for details.
The text was updated successfully, but these errors were encountered: