Previously, the Protobuf serializer would gracefully handle values that had no explicit typecaster. That unexpectedly changed with the latest release, resulting an in an unknown type error being thrown for Protobuf fields without explicit corresponding Ruby types (i.e., enums, messages).
Update the Protobuf serializer to restore the previous behavior, along with specs to ensure it doesn't happen again.
newellista
commented
5 years ago
Previously, the Protobuf serializer would gracefully handle values that had no explicit typecaster. That unexpectedly changed with the latest release, resulting an in an unknown type error being thrown for Protobuf fields without explicit corresponding Ruby types (i.e., enums, messages).
Update the Protobuf serializer to restore the previous behavior, along with specs to ensure it doesn't happen again.