-
Notifications
You must be signed in to change notification settings - Fork 240
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
[SDK] Fix deploy transaction listener for all deploy types sdk.deployer.addDeployListener()
#494
Conversation
…dDeployListener()`
🦋 Changeset detectedLatest commit: c6455c7 The changes in this PR will be included in the next version bump. This PR includes changesets to release 5 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 |
Size Change: +202 B (0%) Total Size: 3.62 MB ℹ️ View Unchanged
|
Thanks @joaquim-verges . Still i need to go deeper in understanding all the huge code there :) So i tried to make a not invasive fix in order to break nothing.... so thank you for your PR and happy to help in any way... I forked and checked this new version. The problem is the tx hash is only coming at the end of deployment. But still need a solution to provide "submitted" event before wait for confirmations. The whole reason for this is to get the transaction hash early on, so we can react... in edge cases like user leaving the dapp, or his connections breaks etc... this way ... we know what transaction to follow when we get back.... so the idea is to:
I created a new PR with the fix for this, please check and let me to know Thanks. |
This now works with all deploy types - factory/proxy/direct
API is simpler too:
sdk.deployer.addDeployListener((event) => console.log(event)}