proto-loader: Output functions to serialize and deserialize messages #2970
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
murgatroid99
force-pushed
the
proto-loader_serialize_deserialize
branch
from
141bdc8 to
9294c03
Compare
murgatroid99
force-pushed
the
proto-loader_serialize_deserialize
branch
2 times, most recently
from
d0ddfd6 to
30e7287
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This implements the change described in grpc/proposal#503 for both the runtime generator and the TypeScript generator. This doesn't add any types to the API, it just makes the serialize and deserialize functions more generally usable. It breaks the API by changing the
MessageTypeDefinitiontype signature, so I bumped the version.