Stephen Haberman

Hi @JakobJingleheimer ; we genuinely appreciate the offer to VC! If we were stuck on some super-intricate Node internals issue, it would be invaluable. That said, I don't think there's...

> change to the migrations/schema We use [node-pg-migrate](https://salsita.github.io/node-pg-migrate/) to manage our db schema, so each time we need a new column / new table / etc, we write a `migrations/(timestamp)-add-author-first-time.ts`...

Hi @shohoney ; I had to do a big of digging, but that option was added to solve this issue: https://github.com/stephenh/ts-proto/issues/492 Which is actually a Next.js issue with `getServerSideProps`. I...

Hi @deser ; at first I thought that was our default `oneof` output, in that the fields stay top-level, but, right, we don't technically do the `|`... That might be...

What do you expect the type for your `OuterMessage` to look like? > it will take considerable amount of time from myself Yep, that's how open source goes. :-)

I was thinking it'd be something like: ``` type OuterMessage = {} | {inner_message : InnerMessage } type InnerMessage = { string_value: string } | { int_value: number } ```...

> Yes, there's also possibility to put shared props into its own common interface, > but that might affect performance, so duplicating is probably ok I'm not sure why you...

Hi @StevenACoffman ! I'm not an expert on connect-rpc, but lately we do sit on top of `@buf/protobuf` anyway for our underlying encode/decode methods, so I would thinks this should...

Ah yeah, I kinda remember that going by, but hadn't deeply looked into their new v2 bindings. I agree it would be worth a readme entry/note with a short tldr...

Fwiw @vaxerski , I agree with @definitelynotrazu that this issue could probably be closed as done, and any additional work tracked via new/separate issues. As a new user wandering into...