-
Notifications
You must be signed in to change notification settings - Fork 3
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(ConnectWalletForm): ask consent for automatic key addition #637
Conversation
Extension builds preview
|
47a3974
to
ef86b18
Compare
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.
test-e2e
ecdf16c
to
fe6d3b4
Compare
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.
test-e2e
@sidvishnoi Looks good. My only comment is if we can centre the message and buttons in the pop up |
Final: @RabebOthmani |
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.
Looks good!
<AutoKeyAddConsent | ||
onAccept={() => { | ||
autoKeyAddConsent.current = true; | ||
// saveValue('autoKeyAddConsent', true); |
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.
Probably related to my comment above - saving this preference.
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.
Yeah, I'm not sure if we want to save, but I kept the code here in case we decide to.
Or, maybe we can ask for consent once per wallet address? Like we'll store the wallet address instead of true
there.
If it's false, we most likely want to ask again, as that's a happier path for user (in case they find adding key manually is too much after seeing that input).
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.
Context
Changes proposed in this pull request
Screencast.from.02-10-24.09.22.43.PM.IST.webm