All fields are optional in generated messages for proto2 schemas
joemckenney opened this issue · comments
When using proto2 in a project, we expect the generated code to encode the optionality of a field in a message.
Currently, all fields in the generated messages are optional (which makes sense in proto3 but doesn't quite align with a proto2 schema).
Seems to be related to #414