refactor: future-proof getInstalledWallets
#51
Merged
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.
Future starknet wallets should be automatically handled using this method, independent of the way they're set on the
window
object.A question remains: what if multiple wallets don't define an
id
? Currently only one of them would be keyed as "undefined" in thiswallets
object, overwriting the others. Since the key set onwindow
is already unique for each wallet, why not use that as identifier?