fix: fix account controller legacy polling #5321
Merged
+38
−46
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
Changes were made to accountTrackerController inside the @metamask/assets-controllers package.
The account tracker polling was executed on the constructor with the initialisation. This caused additional requests to be sent by the app, leading to performance issues.
Additionally, the accountTracker was still using legacy polling via the poll function. This function has now been removed, and a test has been added to prevent the creation of multiple polling instances.
These changes improve efficiency by reducing unnecessary network requests and ensuring the polling mechanism is properly controlled.
References
Changelog
@metamask/assets-controllers
Checklist