Stephen Haberman

Hi @geritol ; I'm not really an expert on grpc-gateway, but it sounds like it's similar to grpc-web (which ts-proto does support), but with more flexibility in how the service...

Hi @jaysonwu991 , I personally don't use either grpc-web or grpc-gateway, so honestly am not sure of the gap between support/features for both. I know ts-proto uses are using grpc-web...

Hi @jeffnsquared ; I'm wondering if maybe wire does not expect the field to be serialized at all when empty. You can see an example of how ts-proto encodes a...

@vimmerru if you're using the default output, you can use the `context` option that will add a go-style `ctx` param to the service methods (I think only the `outputServices=default` output...

@turulix honestly I'm somewhat surprised you're seeing `DataLoader`s in your schema output; that was a cute/novel feature I'd added to ts-proto a long time ago, and it requires schemas following...

Hi @LauGaHo ; I don't believe we have a way to disable the wrapper -> JS native type mapping. You could work on a config option/PR, which from your other...

Even for ^, the boolean flag would only be latch forward, from `false` to `true`, and if we wanted to move back from `true` to `false`, we'd need to re-calc...

Another use case: ``` readonly numberOfTimesUsed: ReactiveField = hasReactiveField( "numberOfTimesUsed", { allowances: {}, constraints: {} }, (ci) => ci.allowances.get.length + ci.constraints.get.length, ); ``` Where the # of children could be...

I neat API for ^ might be a `hasReactiveQueryField`: ``` readonly numberOfTimesUsed: ReactiveField = hasReactiveQueryField( "numberOfTimesUsed", { allowances: {}, constraints: {} }, (ci) => em.findCount(GPCI, { ...find... }); ); ```...

`hasReactiveQueryField` landed and seems like a pretty good approach for now. It's not super-delta-/incremental-fancy, but that's probably better actually.