[ISSUE] (TEPHRA-119) TransactionEditCodecV4 not getting used in deserialization

[Gary Helmling (JIRA)]

Gary Helmling created an issue

Tephra / TEPHRA-119 TransactionEditCodecV4 not getting used in deserialization Issue Type: Bug Assignee: Gary Helmling Components: core Created: 11/Aug/15 5:47 PM Priority: Major Reporter: Gary Helmling When TransactionEditCodecV4 was added it was not hooked in properly to be used in deserialization, so TransactionEditCodecV3 is still being used, leading to dropped fields. In addition, so the current TransactionEditCodec support duplicates code as well as the class references, making mistakes like this likely. We should refactor the TransactionEditCodec usage to fix this issue and avoid further problems in the future. Add Comment

This message was sent by Atlassian JIRA (v6.1.5#6160-sha1:a61a0fc)

[Gary Helmling (JIRA)]

Gary Helmling commented on an issue

Re: TransactionEditCodecV4 not getting used in deserialization PR for fix: https://github.com/caskdata/tephra/pull/74

Add Comment

Tephra / TEPHRA-119 TransactionEditCodecV4 not getting used in deserialization

When TransactionEditCodecV4 was added it was not hooked in properly to be used in deserialization, so TransactionEditCodecV3 is still being used, leading to dropped fields. In addition, so the current TransactionEditCodec support duplicates code as well as the class references, making mistakes like this likely.

We should refactor the TransactionEditCo...

[Gary Helmling (JIRA)]

Gary Helmling updated an issue

Tephra / TEPHRA-119 TransactionEditCodecV4 not getting used in deserialization

Change By: Gary Helmling Priority: Major Blocker

Add Comment

[Gary Helmling (JIRA)]

Gary Helmling resolved an issue as Fixed

Merged to develop

Tephra / TEPHRA-119 TransactionEditCodecV4 not getting used in deserialization

Change By: Gary Helmling Status: Open Resolved Fix Version/s: 0.6.2 Resolution: Fixed

Add Comment