Code gen always uses optional even for proto3 non-optional fields
jzjones opened this issue · comments
When explicitly querying for non-optional fields in a knit request, the resulting Typescript response type has those fields marked as optional. This only seems to apply to fields that are a message type, scalar fields seem to work as expected in this case.
Hey! can you share a reproducible example?