-
Notifications
You must be signed in to change notification settings - Fork 14
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
allow accounts[0] to be undefined #236
Comments
A possible related feature would be to provide some means of reinitializing |
So then Alchemy would have to check if the default account exists or not? |
would love to have arc.js auto detect account changes |
Yes, the application (Alchemy) would need to check if the default account exists. No more exception in that case. I will create a new ticket on creating a Pub/Sub event for when the account changes. |
When the user finally sets the default account, the application will have to re-invoke InitializeArcJs. You can use the existing Arc.js subsystem for watching for account changes. |
Allow accounts[0] to be undefined. Issue a logged warning instead of throwing an exception.
This allows for cases where arc.js is used in read-only situations.
When undefined, don't set a default user in
Utils.requireContract
.The text was updated successfully, but these errors were encountered: