Results 591 comments of Stephen Haberman

> separate package on npm ("ts-proto-core"?) with just the well-known types in it Yeah, I think this is a good idea. Maybe something like `@ts-proto/google-protobuf-descriptor`, `@ts-proto/google-protobuf-wrappers` etc. And maybe anything...

> so they were all generated together Right, that is a big wrinkle, i.e. how would ts-proto "know" (for either the well-known types or internal company types) "which types from...

@paralin cool, that makes sense... in theory @pcj 's #597 would allow setting up `-Mgoogle.protobuf=@aperturerobotics/ts-proto-common-types` to achieve what you want? > I was thinking it might make sense to instead...

@paralin sure, I understand the desire, but link me to the options that protobuf-go supports? Just scanning their docs, I see maybe three or four (`-M`, some path stuff)... Afaict...

Hey @gitn00b1337 yeah, `nestJs` is sort of a meta-flag for other things. You can see how it's handled here: https://github.com/stephenh/ts-proto/blob/main/src/options.ts#L120 Oh shoot, yeah and then here: https://github.com/stephenh/ts-proto/blob/main/src/main.ts#L201 So we do...

Hey @LazloN5 , ts-proto doesn't have any support for extensions at the moment; if you'd like to hack on it, that'd be great!

@alecthomas yeah, that is a good point. We'd only needed protobuf/twirp for our rpc/services, so was all we've implemented so far... The service impl code is fairly straightforward: https://github.com/stephenh/ts-proto/blob/master/src/main.ts#L725 And...

Hey @isherman apologies for the really late reply here. It'd be awesome if you could poke around at this. Per the protobuf.js PRs, I think that shouldn't be a problem,...

@Toofifty shoot! Sorry for not responding to your comment sooner. Per your question: > all: FooBar.FOO_BAR_BAZ = "FOO_BAR_BAZ" will generate FooBar.BAZ = "BAZ" > members: FooBar.FOO_BAR_BAZ = "FOO_BAR_BAZ" will generate...

@HypeillingerChillinger we've bumped the version of typescript; can you try the latest version of ts-proto and see if that fixes the error with `useExactTypes`? Thanks!