fix(types): Allow transaction to be null in Transactionable interface (#13092).#13093
Conversation
|
Hello! Thanks! |
You create a new branch off the
|
|
I tried running These errors doesn't seem to be related to the tests I added. |
|
@yjwong Hmm, that's weird, but since tests are passing on GitHub Actions, don't worry about it. Just in case, can you confirm what is your TS local version? |
|
@papb I found out why, I manually installed TypeScript 4.1.x using Seems like it's related to this change: https://devblogs.microsoft.com/typescript/announcing-typescript-4-2/#abstract-construct-signatures But that's probably a different issue altogether. |
|
🎉 This PR is included in version 6.5.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Pull Request check-list
Please make sure to review and check all of these items:
npm run testornpm run test-DIALECTpass with this change (including linting)?Description of change
When using TypeScript with
strictNullChecksenabled, we cannot passnulltotransaction, but this is actually allowed and used to execute in a non-transaction context when in an auto-transaction block.Closes #13092.
I wish for this change to also be backported to v5. How do I go about doing that?