Skip to content
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

There is no way of setting supportChains when supportedChains is different than wagmi config #406

Closed
0x33dm opened this issue Jun 24, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@0x33dm
Copy link

0x33dm commented Jun 24, 2024

Describe the bug

I'm working on a project where my dapp where users will interact only with 2 networks but turns out some of the information displayed on the screen are coming from other networks.

The problem then arrises when I'm connected to one of those other networks, the app won't show the pop up asking users to switch chains.

Expected behavior

Have an option to set the supportedChains manually overriding the list that ( i believe ) is being automatically fetched from the Wagmi Context.

@0x33dm 0x33dm added the bug Something isn't working label Jun 24, 2024
@0x33dm
Copy link
Author

0x33dm commented Jun 28, 2024

sorted by creating a different config for the other requests from the "not globally supported chains" instead of using global config.

@0x33dm 0x33dm closed this as completed Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant