-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Conversation
… add-fee-details-rpc
… add-fee-details-rpc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks overall good, would be good if someone can look closer into the serde details as well.
… add-fee-details-rpc
… add-fee-details-rpc
… add-fee-details-rpc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good to me
Co-authored-by: Guillaume Thiolliere <gui.thiolliere@gmail.com>
at some point I wonder if those two RPC shouldn't be merged, or just the new RPC have all information so that we don't break RPCs. But I'm ok like this. |
^^ the refactor that also affects the runtime code is minimal, but still, I think this is the correct next step. Correct me otherwise. |
… add-fee-details-rpc
… add-fee-details-rpc
… add-fee-details-rpc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We also don't bump the version of the runtime api. As it will only return error when calling the RPC and the runtime api doesn't exist, I'm fine with it.
… add-fee-details-rpc
bot merge |
Trying merge. |
This PR adds a new RPC
payment_queryFeeDetails
which returns the details of the final fee, there are no changes to the existing payment RPC.Close #7691