-
Notifications
You must be signed in to change notification settings - Fork 2k
Hosting Dashboard: Add reset password in Settings Database #103691
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
Conversation
Jetpack Cloud live (direct link)
Automattic for Agencies live (direct link)
|
client/dashboard/app/style.scss
Outdated
| } | ||
|
|
||
| h1 { | ||
| h1:not( .components-modal__header-heading ) { |
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 really happy about this change, any better ideas?
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.
Hmm... maybe move these existing CSS to https://github.com/Automattic/wp-calypso/blob/0a063059234e6cccc1f61843ecbe34e1b8cfb97f/client/dashboard/components/page-header/style.scss 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.
I think that's a fair change. Updated in c404fa4.
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.
cc: @youknowriad
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.
we're using an h1 in a modal, is that really what we want? Aren't we supposed to have only one h1 in a page?
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.
Ok, I see the message about modal forcing h1. That's probably fair.
The downside I see with the change to move to page header, is that the page-header is probably a reusable component that can be extracted to the components package, and defining the h1 styles seems like an "application layer" thing that the reusable component should be agnostic about.
That said, it's not a big deal at the moment, there are multiple solutions here including a "theme" package for DS. The change is fine for now.
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.
Perhaps the modal h1 should also use brand font? cc: @jasmussen @jameskoster for 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.
Unsure of the semantics, but yes I could personally see all headings being subject to branding on the font level. I think there's a technical/component reusability question to answer as to how to best do this.
|
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: App Entrypoints (~143 bytes added 📈 [gzipped]) DetailsCommon code that is always downloaded and parsed every time the app is loaded, no matter which route is used. Sections (~46 bytes added 📈 [gzipped]) DetailsSections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to. Legend What is parsed and gzip size?Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory. Generated by performance advisor bot at iscalypsofastyet.com. |
client/dashboard/app/style.scss
Outdated
| } | ||
|
|
||
| h1 { | ||
| h1:not( .components-modal__header-heading ) { |
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.
Hmm... maybe move these existing CSS to https://github.com/Automattic/wp-calypso/blob/0a063059234e6cccc1f61843ecbe34e1b8cfb97f/client/dashboard/components/page-header/style.scss instead? 🥲
| }: ResetPasswordModalProps ) { | ||
| const [ isRestoring, setIsRestoring ] = useState( false ); | ||
|
|
||
| const handleRestore = async () => { |
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.
Nit: there is no await here for the async
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.
Good catch, removed the leftover code in c404fa4.
1b6b34e to
c404fa4
Compare
|
This PR modifies the release build for the following Calypso Apps: For info about this notification, see here: PCYsg-OT6-p2
To test WordPress.com changes, run |
| font-size: $font-size-medium; | ||
| } | ||
|
|
||
| h1 { |
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.
Any rationale about this change?
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.
| } | ||
|
|
||
| .client-dashboard-components-page-header__heading { | ||
| font-family: var( --dashboard-h1__font-family ); |
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.
These header components aim to be promoted in @automattic/components and should not use dashboard css vars. I'm keeping this for now in #103555, but we should update during the component's move to the other package.
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 assuming you're saying we shouldn't use dashboard CSS vars. In that case, I lean towards reverting this particular change and see how we feel about having the modal h1 using the branding font as well.
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, sorry. I missed typing the not above (update now 😄 ).
|
This Pull Request is now available for translation here: https://translate.wordpress.com/deliverables/17513118 Some locales (Hebrew) have been temporarily machine-translated due to translator availability. All other translations are usually ready within a few days. Untranslated and machine-translated strings will be sent for translation next Monday and are expected to be completed by the following Friday. Thank you @taipeicoder for including a screenshot in the description! This is really helpful for our translators. |
|
Translation for this Pull Request has now been finished. |

Ref DOTCOM-13253
Proposed Changes
This PR implements the reset database password functionality.
Why are these changes being made?
Hosting Dashboard.
Testing Instructions
Pre-merge Checklist