Stephen Haberman

> The first issue I encountered is that fields marked as optional > would not translate to a field: Type | undefined. I guess this makes sense...when ts-proto was first...

Ah yeah; I won't deny that--ts-proto's "strength" is that its collected a large array of knobs/flags over the years that, in theory, let users adapt the output to whatever their...

Fwiw @lukealvoeiro I was looking for any issues tagged with "proto2" to close out, after you landed #1007 ... seems like this one is still valid, i.e. an ask to...

Closing until we add a flag for pre-2020 runtimes.

Hi @f0rmat1k , sure if you wanted to add support for `outputJsonMethods=fromJSON`, so it becomes like `outputJsonMethods=true|false|fromJSON|toJSON"` that sgtm. Thanks!

Hi @moecasts , no, I don't think that's possible today... We can generate clients for Twirp, Grpc, Nice rpc, and NestJS, but it looks like you're using the `google.api.http` extensions,...

@erba fwiw I agree the `google.api.http` extensions are confusing, which frankly is kind of par-of-the-course for the whole protobuf/gRPC ecosystem. :shrug: Personally I've not used them, which is why ts-proto...

@jcready is right that schemas with two-way pointers would infinite loop. IIRC I've seen the Java protobuf output handles this by creating a static/shared "default foo" / "default bar" instances,...

Hm. Fwiw I'm not familiar with ROS, but when you mention: > Also, "all-are-optional" policy of protobuf Doesn't that make this feature less necessary / maybe more hassle than it's...

Hi @ablause ; this sounds somewhat similar to the issue that was recently fixed in: https://github.com/stephenh/ts-proto/pull/951 But that was for `Value` and this is for `Struct`s... I'm kinda guessing there,...