chore: Remove useRequestQueue toggle to turn on/off Per Dapp Selected Network Feature
#4941
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
adonesky1
force-pushed
the
ad/remove-request-queue-toggleability
branch
from
c4089a8
to
3196bc4
Compare
adonesky1
force-pushed
the
ad/remove-request-queue-toggleability
branch
from
3196bc4
to
fc955bd
Compare
|
@metamaskbot publish-preview |
|
Preview builds have been published. See these instructions for more information about preview builds. Expand for full list of packages and versions. |
adonesky1
changed the title
useRequestQueue toggle to turn on/off Per Dapp Selected Network Feature
7 tasks
mcmire
reviewed
Nov 21, 2024
jiexi
reviewed
Nov 22, 2024
| // if the request queue feature is turned off, or this method is not a confirmation method | ||
| // bypass the queue completely | ||
| if (!useRequestQueue() || !shouldEnqueueRequest(req)) { | ||
| // if this method is not a confirmation method bypass the queue completely |
There was a problem hiding this comment.
Suggested change
| // if this method is not a confirmation method bypass the queue completely | |
| // if this method is not a confirmation method then bypass the queue completely |
nit. not important
jiexi
approved these changes
Nov 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Explanation
The "Select networks for each site" preference toggle on the experimental settings page has been live for many releases now since the toggle has been turned on by default. We meant to remove it a while ago.
This PR removes the togglability of per dapp selected network from the
SelectedNetworkControllerandQueuedRequestMiddlewareThe extension to integrate this change will also have to implement a migration to remove this state.
Another reason we should remove this now is that having this setting turned off is causing a bug to result with
wallet_switchEthereumChainand the interaction between the new chain permissions feature and the absence of queuing.References
Extension PR w/ preview builds of this PR (plus full removal of the toggle): MetaMask/metamask-extension#28577
When integrated in the extension will resolve this issue: MetaMask/metamask-extension#28441
Changelog
@metamask/queued-request-controllercreateQueuedRequestMiddlewareno longer expects auseRequestQueueproperty in its param options.@metamask/selected-network-controlleruseRequestQueuePreferenceoronPreferencesStateChangeparamsChecklist