fix: don't rely on explicit export of TransactionCtorFields type #205
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Please also ship metaplex-foundation/metaplex-program-library#507. |
lorisleiva
approved these changes
Jun 4, 2022
|
As discussed, I'm closing this PR since we are deprecating this SDK in favour of the new one. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is our bad. We:
In this PR I replace the recently-renamed
TransactionCtorFieldstype with a type that derives it, for all current and future versions of web3.js. This will not break again, no matter how many times the parameter gets renamed.Fixes #202.