-
Notifications
You must be signed in to change notification settings - Fork 58
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
feat: allow login to non-db contracts #185
Conversation
Before this commit, each time updateAccount was triggered the VM checked if the selector was connected - i.e. had an access key - to a contract different from SocialDB, and proceed to logout the user if that was the case. This commit removes this constraint, allowing users to connect to both SocialDB and other contracts.
this PR solves issue #184 |
Don't remove the change, but make it configurable instead. This is desired behavior for default gateways that only use it with a single contract |
@evgenykuzyakov yes, that makes sense. I reverted my changed and added a check for a config flag. |
chore: specify which contract is allowed to be logged-in
changed the code based on @charleslavon request, now the |
I meant to push to this pr, not merge to dev. I'll push another change shortly. |
Before this commit, each time updateAccount was triggered the VM checked if the selector was connected - i.e. had an access key - to a contract different from SocialDB, and proceed to logout the user if that was the case.
This commit removes this constraint, allowing users to connect to both SocialDB and other contracts.