Skip to content

Conversation

salimtb
Copy link
Contributor

@salimtb salimtb commented Aug 22, 2025

…tests

Explanation

This PR implements

  • the enableAllPopularNetworks() to enable all popular networks
  • modifies the enableNetwork() function to use exclusive behavior, ensuring only one network is enabled per namespace at a time.

References

Checklist

  • I've updated the test suite for new or updated code as appropriate
  • I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
  • I've communicated my changes to consumers by updating changelogs for packages I've changed, highlighting breaking changes as necessary
  • I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes

@salimtb salimtb force-pushed the feat/enable-all-popular-networks branch from 79f67e9 to 1fa6612 Compare August 22, 2025 16:25
@amitabh94
Copy link
Contributor

Can we fix the PR description ?

@salimtb salimtb marked this pull request as ready for review August 22, 2025 16:38
@salimtb salimtb requested review from a team as code owners August 22, 2025 16:38
@salimtb salimtb merged commit 2746e05 into main Aug 22, 2025
231 checks passed
@salimtb salimtb deleted the feat/enable-all-popular-networks branch August 22, 2025 19:00
micaelae pushed a commit that referenced this pull request Aug 25, 2025
#6367)

…tests

## Explanation

This PR implements 

- the `enableAllPopularNetworks()` to enable all popular networks
- modifies the `enableNetwork()` function to use exclusive behavior,
ensuring only one network is enabled per namespace at a time.

<!--
Thanks for your contribution! Take a moment to answer these questions so
that reviewers have the information they need to properly understand
your changes:

* What is the current state of things and why does it need to change?
* What is the solution your changes offer and how does it work?
* Are there any changes whose purpose might not obvious to those
unfamiliar with the domain?
* If your primary goal was to update one package but you found you had
to update another one along the way, why did you do so?
* If you had to upgrade a dependency, why did you do so?
-->

## References

<!--
Are there any issues that this pull request is tied to?
Are there other links that reviewers should consult to understand these
changes better?
Are there client or consumer pull requests to adopt any breaking
changes?

For example:

* Fixes #12345
* Related to #67890
-->

## Checklist

- [ ] I've updated the test suite for new or updated code as appropriate
- [ ] I've updated documentation (JSDoc, Markdown, etc.) for new or
updated code as appropriate
- [ ] I've communicated my changes to consumers by [updating changelogs
for packages I've
changed](https://github.com/MetaMask/core/tree/main/docs/contributing.md#updating-changelogs),
highlighting breaking changes as necessary
- [ ] I've prepared draft pull requests for clients and consumer
packages to resolve any breaking changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants