-
Notifications
You must be signed in to change notification settings - Fork 5k
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
web3 middleware #6951
web3 middleware #6951
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
Changeset
View detailed bundle breakdownAdded No assets were added Removed No assets were removed Bigger
Smaller No assets were smaller Unchanged
|
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.
Benchmark
Benchmark suite | Current: 87294d1 | Previous: 6c075db | Ratio |
---|---|---|---|
processingTx |
8828 ops/sec (±4.82% ) |
9301 ops/sec (±4.81% ) |
1.05 |
processingContractDeploy |
39328 ops/sec (±5.18% ) |
39129 ops/sec (±7.62% ) |
0.99 |
processingContractMethodSend |
18771 ops/sec (±9.50% ) |
19443 ops/sec (±5.19% ) |
1.04 |
processingContractMethodCall |
39649 ops/sec (±6.16% ) |
38971 ops/sec (±6.34% ) |
0.98 |
abiEncode |
43277 ops/sec (±6.71% ) |
44252 ops/sec (±6.92% ) |
1.02 |
abiDecode |
30120 ops/sec (±7.66% ) |
30419 ops/sec (±8.89% ) |
1.01 |
sign |
1529 ops/sec (±3.13% ) |
1656 ops/sec (±4.08% ) |
1.08 |
verify |
377 ops/sec (±0.69% ) |
373 ops/sec (±0.78% ) |
0.99 |
This comment was automatically generated by workflow using github-action-benchmark.
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## 4.x #6951 +/- ##
==========================================
+ Coverage 87.37% 91.96% +4.58%
==========================================
Files 197 215 +18
Lines 7548 8223 +675
Branches 2059 2217 +158
==========================================
+ Hits 6595 7562 +967
+ Misses 953 661 -292
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.
Seems great! beside Oleksii's points.
However, I think it would be the best to use this feature in a plugin before we make it available in the next release. In order to see it in action and see if we need some changes that we can do without casing a breaking changes in the subsequent releases. So, can we for example set it as experimental till we try it inside some real case? And later we mark it as a read-to-use feature?
I also thought same to not include this in next release and test it with Swisstronik usecase, so in case any breaking changes required we can do before merging it ,I think we should merge this PR after next release ( and for next sprint's release ). I'll update and close implementation issue and created next issue for tracking above. |
Description
#6864
#6963
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.