Timo Stamm

From #15: ```typescript export enum FieldKind { SCALAR, MAP, ENUM, MESSAGE } ``` The generated field information could use the same pseudo-inlined code [as RepeatType, etc.]: ```typescript kind: 1 /*FieldKind.SCALAR*/...

From #15: ```typescript export enum FieldKind { SCALAR, MAP, ENUM, MESSAGE } ``` The generated field information could use the same pseudo-inlined code [as RepeatType, etc.]: ```typescript kind: 1 /*FieldKind.SCALAR*/...

Support Enum / Enum value options

1

Protobuf has enum options. For example: ```proto extend google.protobuf.EnumOptions { bool enum_opt_bool = 2001; } extend google.protobuf.EnumValueOptions { bool enum_value_opt_bool = 3001; } enum AnnotatedEnum { option (spec.enum_opt_bool) = true;...

Protobuf has enum options. For example: ```proto extend google.protobuf.EnumOptions { bool enum_opt_bool = 2001; } extend google.protobuf.EnumValueOptions { bool enum_value_opt_bool = 3001; } enum AnnotatedEnum { option (spec.enum_opt_bool) = true;...

Protobuf has enum options. For example: ```proto extend google.protobuf.EnumOptions { bool enum_opt_bool = 2001; } extend google.protobuf.EnumValueOptions { bool enum_value_opt_bool = 3001; } enum AnnotatedEnum { option (spec.enum_opt_bool) = true;...

The Connect transport takes `binaryOptions` - rarely used options for the binary encoding - but never passed them to the serialization functions. This fixes it.

This is a starting for full support for proto2 extensions, generating a distinct symbol for each extension field. Note that it is a very incomplete draft that only investigates the...

This is a simplistic approach at supporting proto2 extensions. Instead of introducing a bespoke type that users attach to a message, generate the fields added by an extension right on...

Let's start with the 3.x release by making it master.