-
Notifications
You must be signed in to change notification settings - Fork 142
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: add button to get extension #417
Conversation
Hey! If you'd like to test out the changes in this PR, check out our demo app. https://deploy-preview-417--authenticator-demo.netlify.com/ |
Size Change: 0 B Total Size: 418 kB ℹ️ View Unchanged
|
@@ -0,0 +1,228 @@ | |||
import * as React from 'react'; |
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.
Debating whether this belongs in ui. Is it domain-agnostic? 🤔 Maybe, I guess. But could also be seen as specific to this feature, thus belonging in app
.
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 see the argument for that! I've kind of liked simply throwing all new icons into UI, it just lets us work in one place. Would be curious to hear @aulneau 's opinion.
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.
I am generally in favor of all icons being in the ui lib, because they truly are generic, typically at least. It helps force consistency for iconography. I don't think we lose anything by adding it.
@@ -0,0 +1,233 @@ | |||
import * as React from 'react'; |
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.
Is your IDE auto completing React as a * import? It's a default export anyway right?
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.
No - whenever I make a new icon, I copy/paste the first few lines from an existing icon file, which must have also had this. I'll update!
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.
@hstove Should we move this back to development if it's in draft still? Or is it ready to assign reviewers? |
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.
I think for icons generally I prefer to use solid colored ones, and treat them as color="currentColor" so that they will take on whatever color we want them to. I'd be concerned about these icons working well in a light/dark mode environment.
Ok, that makes sense. So is that an argument for keeping this in |
273a582
to
4cae627
Compare
Update: I refactored all the |
ebd09fe
to
e54bdd7
Compare
Ok, I reverted the |
6082603
to
c1409fa
Compare
c1409fa
to
facf669
Compare
facf669
to
f3f67fc
Compare
f3f67fc
to
04579ad
Compare
@timstackblock it looks like you accidentally closed this PR, instead of the issue! I'm re-opening it, and I've added the extension button to the 'sign in' popup, which relates to #471 |
Deploy previewsDeploy previews for blockstack-app and blockstack-test-app are ready! Built with commit 92855f2. |
04579ad
to
3c611ea
Compare
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 3c611ea:
|
Adds a button to the bottom of the 'choose account' screen to get the extension.
Figma designs
Right now, when you click the button, nothing happens. We don't have the extension published, yet.