Fix BytesValue handling in FromJSON method #156
Closed
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
ebakoba
changed the title
|
Can we please merge this @stephenh ? |
ebakoba
force-pushed
the
fix-bytes-value-from-json
branch
from
11af1b0
to
41047c7
Compare
stephenh
added a commit
that referenced
this pull request
Nov 27, 2021
stephenh
added a commit
that referenced
this pull request
Nov 27, 2021
stephenh
added a commit
that referenced
this pull request
Nov 28, 2021
* Add proof-of-concept exact types. Fixes #156. * Extract Builtin. * Codegen. * Add expect error. * Codegen again. * Fix type registry.
|
🎉 This issue has been resolved in version 1.92.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
zfy0701
added a commit
to sentioxyz/ts-proto
that referenced
this pull request
Jan 5, 2023
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
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.
Resolves the issue raised in issue #155