-
Notifications
You must be signed in to change notification settings - Fork 23
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
metamask support #430
base: master
Are you sure you want to change the base?
metamask support #430
Conversation
bergauz
commented
Oct 28, 2019
•
edited
Loading
edited
private _web3Callable$: BehaviorSubject<Web3> = new BehaviorSubject(null); | ||
private _web3Payable$: BehaviorSubject<Web3> = new BehaviorSubject(null); | ||
private _web3Metamask$: BehaviorSubject<Web3> = new BehaviorSubject(null); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Switching back to Metamask specific naming seems backwards. Why don't we keep these general, for example:
walletInstalled$:
walletConfigured$:
_web3Payable$:
Then if/when we switch or add support for others, none of this needs to be updated.
(The user messages can stay metamask specific until we actually add more)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jmank88 can you check new code, wallet and metamask is different, pk is also wallet
Configuration cases to test:
|
@jmank88 if MM available there's no option to enter PK |
# Conflicts: # front/src/app/services/wallet.service.ts
What are we doing with this? |
No, if they stay on the page, leave the pk in the field. |