-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(pods): fix simulation errors when no tokenId is provided [BOOST-4097] #448
Conversation
🦋 Changeset detectedLatest commit: 1b7f211 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - it is getting the most recent token ID now. As a follow-on if we see more fails I still think it would make sense to iterate through the tokenIds when the simulate fails and tokenId hasn't been set but we can pull that lever based on subsequent issues SG?
packages/pods/src/Pods.test.ts
Outdated
expect(fee.projectFee).toEqual(parseEther('0')) | ||
expect(fee.actionFee).toEqual(parseEther('0.0007')) | ||
|
||
// const { actionFee, projectFee } = await getFees(mintParams) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cleanup
Previously this would receive an error when no tokenId was provided due to their not being a certain function
nextTokenId
not being available on the ABI.There can still be issues if the latest tokenId is not in a mintable state.
fixes BOOST-4097