Switch to github.com/dcodeIO/ProtoBuf.js? about ts-protoc-gen HOT 6 CLOSED

I think dcodeIO/ProtoBuf.js is more js-like than google's,
such as creating a message directly from a js object, without invoking a lot of setXXXX
so, it's good to have an option for generating target, I'll choose dcodeIO's first.

from ts-protoc-gen.

How big is the output from this lib though ?

Also is it able to use grpc-web and websockets ?

from ts-protoc-gen.

Websockets or grpc-web shouldn't have an impact as this doesn't make any assumptions about the transport layer (gRPC & gRPC web separate deserialization from transport) e.g. grpcweb+json or grpc+flatbuffers are perfectly valid. My expectation would be that a static compiled serializer would be the same or smaller than a dynamic one.

from ts-protoc-gen.

I guess it's possible but need some changes. since grpc-web transport layer used some google-protobuf Message interface functions, i.e. deserializeBinary() serializeBinary(), which should be changed to encode() decode() for dcodeIO/ProtoBuf.js, or just add deserializeBinary() serializeBinary() as alias functions of encode() decode().

from ts-protoc-gen.

from ts-protoc-gen.

For now, I believe that it is beneficial for the community to have the option of using either Protobuf.js on it's own or going with ts-protoc-gen. I think we should not be implementing protobuf js as a build target at this point.

I'm gonna close this for now. If you have a good usecase, please do let us know.

from ts-protoc-gen.