-
Notifications
You must be signed in to change notification settings - Fork 291
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
Add Sign in with Google Settings View screen. #9685
Conversation
Build files for 2c114eb have been deleted. |
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.
Thanks @tofumatt – perhaps I'm missing an important detail but it seems like the infra related to the site registration setting could be simplified. Otherwise left a few other points throughout.
assets/js/modules/sign-in-with-google/components/settings/SettingsView.js
Outdated
Show resolved
Hide resolved
assets/js/modules/sign-in-with-google/components/settings/SettingsView.js
Outdated
Show resolved
Hide resolved
assets/js/modules/sign-in-with-google/components/settings/SettingsView.js
Outdated
Show resolved
Hide resolved
assets/js/modules/sign-in-with-google/components/settings/SettingsView.js
Outdated
Show resolved
Hide resolved
assets/js/modules/sign-in-with-google/components/settings/SettingsView.stories.js
Outdated
Show resolved
Hide resolved
assets/js/modules/sign-in-with-google/components/settings/SettingsView.stories.js
Outdated
Show resolved
Hide resolved
<SettingsNotice | ||
type={ TYPE_WARNING } |
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.
Not sure what happened here, but this looks quite different from the design
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 just used the Notice
component so I figured it was a mismatch between the components and Figma, but I can make some adjustments 🤔
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.
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'm guessing we weren't really using it elsewhere, but there are a few instances. A bit concerning that it looks so off and we haven't noticed it elsewhere 🤔
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.
My instinct is always to use our base components as they are, and have issues to modify them, but this change was small so I made it here.
Same! Let's open a follow-up issue to make sure our base components match the current designs so that we avoid introducing inconsistency.
assets/js/modules/sign-in-with-google/datastore/anyoneCanRegister.js
Outdated
Show resolved
Hide resolved
Co-authored-by: Evan Mattson <[email protected]>
Co-authored-by: Evan Mattson <[email protected]>
Co-authored-by: Evan Mattson <[email protected]>
…to settings-view-9477.
Size Change: +1.32 kB (+0.07%) Total Size: 1.88 MB
ℹ️ View Unchanged
|
I'm not sure I follow, the badges are using the exact same components: https://github.com/google/site-kit-wp/blob/92c4bd10e1b6f4e90c8817c0b4da4e1060ba4010/assets/js/components/settings/SettingsActiveModule/Header.js#L173-L192 And the only CSS for the Nothing to do with margins, etc. I didn't make any changes to those styles components here, at any rate 🤔 |
I guess it's not implemented here so we can leave it alone, and I'll raise it on the bug bash board instead 👍 |
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.
Thanks @tofumatt – this is super close and much cleaner now. Nothing major left, so I'll push a few small corrections and this should be G2G 👍
const generalSettingsURL = useSelect( | ||
( select ) => | ||
`${ select( CORE_SITE ).getAdminURL() }options-general.php` | ||
); |
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.
That's odd, I thought we could do this with this selector, but we can't without using some legacy behavior I guess. Let's at least construct this more properly :)
const generalSettingsURL = useSelect( | |
( select ) => | |
`${ select( CORE_SITE ).getAdminURL() }options-general.php` | |
); | |
const generalSettingsURL = useSelect( | |
( select ) => | |
new URL( 'options-general.php', select( CORE_SITE ).getAdminURL() ).href | |
); |
<div className="googlesitekit-settings-module__meta-items"> | ||
<div className="googlesitekit-settings-module__meta-item"> | ||
<h5 className="googlesitekit-settings-module__meta-item-type"> | ||
{ __( 'One tap sign in', 'google-site-kit' ) } |
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.
"One Tap" should be capitalized https://developers.google.com/identity/gsi/web/guides/features
{ __( 'One tap sign in', 'google-site-kit' ) } | |
{ __( 'One Tap sign in', 'google-site-kit' ) } |
<SettingsNotice | ||
type={ TYPE_WARNING } |
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.
My instinct is always to use our base components as they are, and have issues to modify them, but this change was small so I made it here.
Same! Let's open a follow-up issue to make sure our base components match the current designs so that we avoid introducing inconsistency.
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.
Great, thanks @tofumatt !
Summary
Addresses issue:
PR Author Checklist
Do not alter or remove anything below. The following sections will be managed by moderators only.
Code Reviewer Checklist
Merge Reviewer Checklist