Stephen Haberman

So when `message.tags` is actually in message, it's pretty clear we should create a new `message.tags: []` on the instance and push to that. What's interesting is, what should we...

@lededje normally ts-proto `decode`-d data does not have any methods, so would be perfect to put into redux, however, for grpc-web, we currently have to add it here: ``` responseType:...

Hey @lededje sure, np, I'll leave the issue open just for others to find & maybe someone can find a way to fix it.

Ah shoot. Yeah... So, one of my pet goals with `ts-proto` was to get some resemblance of optional fields back into protobuf. I did this by treating proto primitives as...

I need a way to "@" the regular NestJS contributors, i.e. @ToonvanStrijp @iangregsondev @lukas-andre @jessequinn to get your thoughts/input on things like this as actual-NestJS-users. Are you guys following all...

@timostamm I believe that ts-proto itself faithfully implements that JSON mapping you reference, specifically for the `StringValue`/etc. wrapper types (but do point something out if it doesn't). AFAIU this issue...

@ofekshalom the gist is that ts-proto _already_ turns `string | undefined` to `{ value: string }` for you in its `Message.encode` methods, i.e.: ``` export const SimpleWithWrappers = { encode(message:...

@radarsu I'm not against that per se, other than worrying how much code might need to change (maybe not a lot, not sure), and ts-proto's already-a-lot-of-flags slippery slope. Although I...

@lucasmaehn awesome! Yes, this is the key we've been waiting for someone to just spend enough time digging to find. :-) In retrospect, that actually looks pretty easy to get...

Yeah, I've generally felt the same way, i.e. it doesn't seem great for every artifact to re-output codegen for every referenced proto. However, I'm not really sure what the alternative...