This is a follow up to #18, and fixes #16 (properly).
This fix involved some reverse engineering of the should_merge attribute on TSP.ArchiveInfo, which appears to indicate that the messages within should be merged together (usually with one being merged into the message at index base_message_index). The contents of the message to be merged seems to be a partially serialized protobuf of a sub-message of the base message's type, corresponding with the field number indicated by the optional diff_field_path parameter.
MrXsc
commented
4 years ago
This is a follow up to #18, and fixes #16 (properly).
This fix involved some reverse engineering of the
should_mergeattribute onTSP.ArchiveInfo, which appears to indicate that the messages within should be merged together (usually with one being merged into the message at indexbase_message_index). The contents of the message to be merged seems to be a partially serialized protobuf of a sub-message of the base message's type, corresponding with the field number indicated by the optionaldiff_field_pathparameter.