Remove BaseTransactionMessage from transaction-message feepayer functions#1136
Conversation
|
fd1f734 to
fabf81c
Compare
4530dbf to
9a794d2
Compare
fabf81c to
a924c27
Compare
BundleMonUnchanged files (136)
No change in files bundle size Final result: ✅ View report in BundleMon website ➡️ |
BundleMonUnchanged files (133)
No change in files bundle size Final result: ✅ View report in BundleMon website ➡️ |
|
Documentation Preview: https://kit-docs-n1pvydpid-anza-tech.vercel.app |
a924c27 to
8d313ba
Compare
9a794d2 to
40bbd3a
Compare
8d313ba to
18180b3
Compare
40bbd3a to
08981b2
Compare
18180b3 to
79da0ed
Compare
Merge activity
|
79da0ed to
abcb7e4
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