-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Listening events on v4 is not working #6082
Conversation
Bundle StatsHey there, this message comes from a github action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
View detailed bundle breakdownAdded No assets were added Removed No assets were removed Bigger No assets were bigger Smaller No assets were smaller Unchanged
|
Deploying with
|
Latest commit: |
4c0ba61
|
Status: | ✅ Deploy successful! |
Preview URL: | https://0f5e0a35.web3-js-docs.pages.dev |
Branch Preview URL: | https://ok-5989-listening-events-on.web3-js-docs.pages.dev |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## 4.x #6082 +/- ##
==========================================
+ Coverage 87.62% 87.68% +0.05%
==========================================
Files 199 199
Lines 7566 7578 +12
Branches 2045 2054 +9
==========================================
+ Hits 6630 6645 +15
+ Misses 936 933 -3
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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.
Could we please have tests for the added logic?
Yes. I am working on it. but unfortunately, it will be not browser+metamask test, just unit test |
if ( | ||
data && | ||
jsonRpc.isResponseWithNotification( | ||
data as unknown as JsonRpcSubscriptionResult | JsonRpcNotification<Log>, | ||
) | ||
) { | ||
this._processSubscriptionResult(data?.params.result); |
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.
Judging from this 1.x code, it seems like this code is to support legacy providers while data.data.result
(what you have marked as // for old providers
) is to support EIP-1193
However, to handle the legacy provider, it would appear that we're missing an event listener for data
event, as messageListener
is only triggered for message
events
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.
thanks. I've added support for old providers and change comment
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.
Otherwise looks good, thank you
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.
@avkos update change log before merging
Co-authored-by: Wyatt Barnes <me@wyatt.email>
Description
Fixes #5989
Please include a summary of the changes and be sure to follow our Contribution Guidelines.
Type of change
Checklist:
npm run lint
with success and extended the tests and types if necessary.npm run test:unit
with success.npm run test:coverage
and my test cases cover all the lines and branches of the added code.npm run build
and testeddist/web3.min.js
in a browser.CHANGELOG.md
file in the root folder.