-
Notifications
You must be signed in to change notification settings - Fork 353
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
Parse reply helpers #502
Parse reply helpers #502
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work.
A few comments on improving checks on the production code (it works for most, but has some limits it doesn't error on).
And a few cleanup requests for the tests. Testing parse_protobuf_string
and parse_protobuf_bytes
as units is more important. You can ignore the "table test" setup comments for now if it is a lot of work. Can be follow up sometime, mainly a comment in general as I see you adopting this pattern (which I know well from Go)
9c6ad8f
to
3390286
Compare
Add high-level varint decoding tests
Fix protobuf string parser: message too short
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good stuff.
Let's merge.
A few code style comments it would be good to address in a simple follow up
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looked at most code, and following Ethan's approval.
Co-authored-by: Jakub Bogucki <[email protected]>
0c8b944
to
a442d7c
Compare
Closes #480.
Events helpers not implemented, but they don't require protobuf, so, can be deserialized directly. In any case, we can add them in a follow-up.