-
-
Notifications
You must be signed in to change notification settings - Fork 190
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
Release/258.0.0 #4979
Release/258.0.0 #4979
Conversation
Removed dependencies detected. Learn more about Socket for GitHub ↗︎ 🚮 Removed packages: npm/@metamask/selected-network-controller@19.0.0 |
145df02
to
b8a597b
Compare
|
||
### Removed | ||
|
||
- `createQueuedRequestMiddleware` no longer takes a `useRequestQueue` parameter. All requests are now queued if `shouldEnqueueRequest(req)` returns true. ([#4941](https://github.com/MetaMask/core/pull/4941)) |
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.
Removing this option will cause a type error if a client is still attempting to pass it, so should we mark it as a breaking change and release it under 8.0.0?
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.
Ah yes I suppose thats true. I'm used to doing this in JS in extension so never get these errors 😅
|
||
### Removed | ||
|
||
- The `SelectedNetworkController` constructor no longer expects a `useRequestPreference` boolean nor an `onPreferencesStateChange` listener. Removal of these parameters means that `domains` state will always be added for sites that are granted permissions. ([#4941](https://github.com/MetaMask/core/pull/4941)) |
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.
Similar as above, removing these options will cause type errors if they're still attempting to be passed. Should we release this under 20.0.0?
f01e72b
to
0b5e6f5
Compare
0b5e6f5
to
8907fc7
Compare
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.
Looks good! Two suggested additions, then I can approve this
Co-authored-by: Mark Stacey <markjstacey@gmail.com>
Co-authored-by: Mark Stacey <markjstacey@gmail.com>
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.
LGTM!
## Changelog ### `@metamask/queued-request-controller` ## 7.1.0 ### Removed - `createQueuedRequestMiddleware` no longer takes a `useRequestQueue` parameter. All requests are now queued if `shouldEnqueueRequest(req)` returns true. ([#4941](#4941)) ### `@metamask/selected-network-controller ## 19.1.0 ### Removed - The `SelectedNetworkController` constructor no longer expects a `useRequestPreference` boolean nor an `onPreferencesStateChange` listener. Removal of these parameters means that `domains` state will always be added for sites that are granted permissions. ([#4941](#4941)) --------- Co-authored-by: Mark Stacey <markjstacey@gmail.com>
Changelog
@metamask/queued-request-controller
7.1.0
Removed
createQueuedRequestMiddleware
no longer takes auseRequestQueue
parameter. All requests are now queued ifshouldEnqueueRequest(req)
returns true. (#4941)`@metamask/selected-network-controller
19.1.0
Removed
SelectedNetworkController
constructor no longer expects auseRequestPreference
boolean nor anonPreferencesStateChange
listener. Removal of these parameters means thatdomains
state will always be added for sites that are granted permissions. (#4941)