Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jon/fix/fio-tx-saved-data #827

Merged
merged 4 commits into from
Sep 5, 2024
Merged

Jon/fix/fio-tx-saved-data #827

merged 4 commits into from
Sep 5, 2024

Conversation

Jon-edge
Copy link
Contributor

@Jon-edge Jon-edge commented Aug 31, 2024

CHANGELOG

Does this branch warrant an entry to the CHANGELOG?

  • Yes
  • No

Dependencies

none

Description

none

Copy link
Contributor

@peachbits peachbits left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This may resolve the unstaking bug but I think the refactor introduced new bugs for other transaction types.

src/fio/FioEngine.ts Outdated Show resolved Hide resolved
src/fio/FioEngine.ts Outdated Show resolved Hide resolved
src/fio/FioEngine.ts Outdated Show resolved Hide resolved
src/fio/FioEngine.ts Outdated Show resolved Hide resolved
src/fio/FioEngine.ts Outdated Show resolved Hide resolved
@Jon-edge Jon-edge force-pushed the jon/fix/fio-tx-saved-data branch 7 times, most recently from 5ba131c to 3468750 Compare September 4, 2024 22:26
Copy link
Contributor

@peachbits peachbits left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Much better! Only two minor issues then it looks good to go

@@ -2139,11 +2147,9 @@ export const parseAction = ({
networkFee = '0'
} else {
networkFee = isRecipient ? `-${fioAmount}` : fioAmount
networkFee = '0'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks like a typo

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah bad merge conflict resolution, good catch

}

nativeAmount = data.to === actor ? `${fioAmount}` : `-${fioAmount}`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think these two lines should be removed from the previous commit

@Jon-edge Jon-edge force-pushed the jon/fix/fio-tx-saved-data branch 5 times, most recently from b2faa3f to ca9387b Compare September 5, 2024 21:11
Retaining all existing functionality
Previously, unstake txs only stored the reward action amount.
Unstake txs now correctly total the reward action amount + unstake amount.
We no longer need to process multiple txs to accurately get fees for sending funds
@Jon-edge Jon-edge merged commit 8dd3310 into master Sep 5, 2024
2 checks passed
@Jon-edge Jon-edge deleted the jon/fix/fio-tx-saved-data branch September 5, 2024 21:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants