Add a typetest for types flowing through transaction message functions#1139
Conversation
🦋 Changeset detectedLatest commit: 0e7de2b The changes in this PR will be included in the next version bump. This PR includes changesets to release 43 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
4c779df to
8342c4b
Compare
530dfbe to
9308170
Compare
8342c4b to
591e4e4
Compare
BundleMonUnchanged files (136)
No change in files bundle size Final result: ✅ View report in BundleMon website ➡️ |
|
Documentation Preview: https://kit-docs-bkq5fpacd-anza-tech.vercel.app |
9308170 to
be1d465
Compare
591e4e4 to
b59f5dc
Compare
| '@solana/instruction-plans': minor | ||
| '@solana/transactions': minor | ||
| '@solana/signers': minor | ||
| '@solana/kit': minor |
There was a problem hiding this comment.
Flagging this - I think this is debatable on minor or major. TransactionMessage is compatible with BaseTransactionMessage, so app code isn't going to break. But if you have functions/types that use BaseTransactionMessage you may need to change them to use TransactionMessage in order to be compatible with our helper functions.
be1d465 to
dfb68fb
Compare
b59f5dc to
401bd1f
Compare
dfb68fb to
fe00744
Compare
f4ff4f7 to
cecbf6d
Compare
fe00744 to
d5eb6f5
Compare
d5eb6f5 to
2c5861f
Compare
651c2cd to
487cd67
Compare
Merge activity
|
2c5861f to
0e7de2b
Compare
|
🔎💬 Inkeep AI search and chat service is syncing content for source 'Solana Kit Docs' |
|
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. |


This PR adds a new typetest that does the following:
decompileTransactionMessageFetchingLookupTablesNote that we don't have any typetests like this that combine functionality from multiple packages. I've put this in
packages/kit/__typetests__/scenarios, but don't feel strongly about where it should live. I do think it's important to have this as part of the repo though because it would be very easy to introduce a regression.Supersedes #1103, by avoiding the need to introduce assertion functions