Additional context
It would probably be best if Metamask would wait till onInstall callback finishes before resolving enable function (which would allow us to throw rpc errors in case of invalid configuration).
I don't think this is relevant for the current state of the system, and any configuration internal to a snap should be handled by the snap itself after being enabled via its own JSON-RPC interface.
What problem are you trying to solve? Snap for different chains should be configurable for different networks (testnet1, testnet2, mainnet).
Describe the solution you'd like I would propose adding params to snap installation on app side:
And on snap side:
Additional context It would probably be best if Metamask would wait till
onInstall
callback finishes before resolving enable function (which would allow us to throw rpc errors in case of invalid configuration).