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
Add back-end protocol 3 support #9
Comments
@ai let's jump into protocol v4? |
Yeap. Having Protocol 4 will be the best. You can start adding 4 to PR for 3. |
@ai I'll create new one. Let's release gem with protocol 3. What do you think? |
@anaumov @dreikanter yeap, it is better to release gem for 3 and then release for 4. |
@anaumov @ai I will release V3 support as a separate gem version on RubyGems later this week. Since #11 is already merged to master, it would be nice to have V4 support implementation on a separate branch to simplify further merge process. BTW, do we have breaking changes between V3 and V4 protocols? |
Yeap V4 is not compatible with V3 |
Version 3 of back-end protocol bring changes:
password
→secret
["error", meta.id, stack]
must contain action ID.meta.id
) the server should answer 500 HTTP codeThe text was updated successfully, but these errors were encountered: