You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 18, 2023. It is now read-only.
As of version 3.0.0 map fields are valid in protobuf messages. FieldUtils doesn't handle these properly, as it treats them as a standard scalar field and generates the wrong getter/setter names.
Example:
message Test {
map<int32, string> sample = 1;
}
The correct getter and setter for sample are putAllSample and 'getSampleMap`.
This change appears to be sufficient to get maps with scalar types for keys and values, but protobufs also allows nested complex types for values.
message Test {
map<int32, Nested> complexField = 1;
}
message Nested {
string name = 1;
}
It looks like both the default Mapper and Converter would need work to support this new category of fields.
The text was updated successfully, but these errors were encountered:
As of version 3.0.0 map fields are valid in protobuf messages.
FieldUtils
doesn't handle these properly, as it treats them as a standard scalar field and generates the wrong getter/setter names.Example:
The correct getter and setter for
sample
areputAllSample
and 'getSampleMap`.This change appears to be sufficient to get maps with scalar types for keys and values, but protobufs also allows nested complex types for values.
It looks like both the default Mapper and Converter would need work to support this new category of fields.
The text was updated successfully, but these errors were encountered: