fix(bug): handle lengthToFee given runtime v9190 #900
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes: #899
This PR properly handles our
perByte
parameter passed intocalc_fee
when calculating a partialFee. With v9190TransactionByteFee
has been replaced withLengthToFee
. What this updates aims to do is handle both properly within a new class method calledgetPerByte
.The PR that introduced this change in polkadot: paritytech/polkadot#5028