feat: add support for unknown fields #473
Merged
Conversation
This file contains 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
# Conflicts: # README.markdown # src/main.ts # src/options.ts
stephenh
approved these changes
Jan 15, 2022
stephenh
pushed a commit
that referenced
this pull request
Jan 15, 2022
# [1.101.0](v1.100.1...v1.101.0) (2022-01-15) ### Features * add support for unknown fields ([#473](#473)) ([3bb9472](3bb9472))
|
🎉 This PR is included in version 1.101.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Implements unknown fields as discussed in #437 behind the
unknownFieldsfeature flag.I had to resort to using undocumented API for writing the proto, as it's apparently unintended to be able to just write out arbitrary bytes to the buffer:
The test makes sure that decoding -> encoding -> decoding works.