This is a RC for v210.0.0. See changelog for more details
@metamask/queued-request-controller@5.1.0
[5.1.0]
Changed
Batch processing now considers both origin and networkClientId, ensuring requests targeting different networks are processed separately. (#4718)
Incoming requests to enqueueRequest now must include a networkClientId; an error is thrown if it's missing. This was previously a required part of the type but since consumers like the extension do not have extensive typescript coverage this wasn't definitively enforced. (#4718)
As discussed in our call, I think 6.0.0 would be good because of the breaking change with the request.networkClientId enforcement, but it's not really a big deal. 5.1.0 is fine
Explanation
This is a RC for v210.0.0. See changelog for more details
[5.1.0]
Changed
networkClientId
, ensuring requests targeting different networks are processed separately. (#4718)enqueueRequest
now must include anetworkClientId
; an error is thrown if it's missing. This was previously a required part of the type but since consumers like the extension do not have extensive typescript coverage this wasn't definitively enforced. (#4718)