Stephanie DiBenedetto
Stephanie DiBenedetto
It looks like there are some half implemented features that are causing problems.
I'm currently looking at some packaging issues and can take a look at this.
We need to verify if this is still an issue (likely so given the dates). Thank you for the detailed repro instructions and explanation.
According to the [official protobuf spec](https://protobuf.dev/programming-guides/proto2/#maps-features), map iteration order is undefined. To my knowledge, some implementations do implement insertion order while others (notably golang) do not. This is something we...
@dependabot rebase
@dependabot rebase
Is your intent here to get a JSON representation of your message? We unfortunately [do not support](https://github.com/protocolbuffers/protobuf-javascript/blob/main/docs/index.md#messages) the proto3 JSON format. In this library, `toObject` is something we recommend folks...
I'm grpc_tools_node_protoc_ts, so I can't speak to what it's doing. Yes, basically you'll have something like: ``` const msg = OptTest.deserializeBinary(bytes) msg.getName(); // will be default value for string, "",...
This basically works with C++ protos and communicate via sending typed arrays back and forth. We should document how to do this.
Hi, are you encountering an issue that this change fixes? We are aware of a bug in BinaryDecoder around over reading, but this isn't the fix we have internally for...