Closed ecp4224 closed 1 month ago
Attention: Patch coverage is 80.00000%
with 1 line
in your changes missing coverage. Please review.
Project coverage is 78.14%. Comparing base (
d2c776d
) to head (bc466f6
). Report is 1 commits behind head on main.
Files with missing lines | Patch % | Lines |
---|---|---|
...ider/extensionProviderHelpers/handleBatchMethod.ts | 80.00% | 1 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
@christopherferreira9 Can you take a look at this PR to make sure everything is good with metamask_batch since we recently had regression?
Working nicely. Checked:
We have some unit tests failing, can you give it a look @ecp4224 ? We'll then be creating a new release with this change targeting 0.29.1
.
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
Explanation
This PR fixes a bug where the extension provider invokes the
metamask_batch
request logic correctly, but then also sends ametamask_batch
request again. This (at best) causes the requests to be sent individually, then all at once or (at worst) causingmetamask_batch
to break entirely if the extension doesn't support the RPCCurrently, the latter case happens. The requests are sent individually, but then errors because it then tries to send
metamask_batch
and the extension doesn't support thatWith the fixed logic in
handleBatchMethod
, the extension and SDK return the correct resultThis PR also updates the unit tests for
handleBatchMethod
to be more robust to ensure this behavior doesn't regress.References
This likely closes #1045
Checklist