Remove BaseTransactionMessage from fee payer signer function#1138
Remove BaseTransactionMessage from fee payer signer function#1138mcintyre94 merged 2 commits intomainfrom
Conversation
|
e58d0ca to
f34da79
Compare
8342c4b to
591e4e4
Compare
f34da79 to
d7e6464
Compare
BundleMonUnchanged files (136)
No change in files bundle size Final result: ✅ View report in BundleMon website ➡️ |
|
Documentation Preview: https://kit-docs-l5upi00th-anza-tech.vercel.app |
d7e6464 to
c25035a
Compare
591e4e4 to
b59f5dc
Compare
c25035a to
71e3551
Compare
b59f5dc to
401bd1f
Compare
71e3551 to
4e513fa
Compare
651c2cd to
487cd67
Compare
Merge activity
|
487cd67 to
4d1e8e4
Compare
|
Because there has been no activity on this PR for 14 days since it was merged, it has been automatically locked. Please open a new issue if it requires a follow up. |
Problem
Our
TransactionMessagefunctions operate onBaseTransactionMessageinstead ofTransactionMessage, which limits the ability to type narrow the resulting transaction messagesSummary of Changes
TransactionMessagein input/output typesPart of a stack that eventually supersedes #1103