-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Adds gravatar wont load notice #99384
Conversation
Jetpack Cloud live (direct link)
Automattic for Agencies live (direct link)
|
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: Sections (~64 bytes added 📈 [gzipped])
Sections 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. |
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 |
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.
@@ -50,6 +50,11 @@ class DnsRecords extends Component { | |||
subtitleOverride: PropTypes.string, | |||
}; | |||
|
|||
getSelectedDomain = () => { |
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.
Do you think we can define a strict return type here to show what's expected?
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.
It's certainly possible, but I think doing so in this PR would be a bad idea. The file isn't currently Typescript, that would be a pretty major change to sneak in.
I did update two of the popup components to TS and added strict type checking, they were relatively safe to update.
I'm happy to create a followup task if you'd like that done as part of the Gravatar project, but I'd rather not mix it in with this PR
d06db64
to
5deb854
Compare
@@ -26,17 +36,18 @@ function RestoreDefaultARecordsDialog( { onClose, visible, defaultRecords } ) { | |||
}, | |||
]; | |||
|
|||
const message = defaultRecords | |||
? sprintf( |
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 couldn't find a path where this untranslated text was used, defaultRecords was always passed in as null, unless I'm missing something. Removing it seemed the best path forward, it's not translated anyway
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 parameter was used in the past, but not anymore
import { useI18n } from '@wordpress/react-i18n'; | ||
import type { ResponseDomain } from 'calypso/lib/domains/types'; |
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.
Converted this and the other dialog to TSX to support type checking
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 for this 🙂
@@ -303,12 +303,13 @@ function DnsMenuOptionsButton( { | |||
<RestoreDefaultARecordsDialog | |||
visible={ isRestoreARecordsDialogVisible } | |||
onClose={ closeRestoreARecordsDialog } | |||
defaultRecords={ 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.
This was the only instance of RestoreDefaultARecordsDialog I could find, and it's always passing in Null, so I removed it as a prop from the component
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!
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.
LGTM! Tested with a Gravatar domain and a regular domain and works great! Left just one minor comment.
@@ -303,12 +303,13 @@ function DnsMenuOptionsButton( { | |||
<RestoreDefaultARecordsDialog | |||
visible={ isRestoreARecordsDialogVisible } | |||
onClose={ closeRestoreARecordsDialog } | |||
defaultRecords={ 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.
Good catch!
import { useI18n } from '@wordpress/react-i18n'; | ||
import type { ResponseDomain } from 'calypso/lib/domains/types'; |
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 for this 🙂
@@ -26,17 +36,18 @@ function RestoreDefaultARecordsDialog( { onClose, visible, defaultRecords } ) { | |||
}, | |||
]; | |||
|
|||
const message = defaultRecords | |||
? sprintf( |
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 parameter was used in the past, but not anymore
client/my-sites/domains/domain-management/dns/restore-default-cname-record-dialog.tsx
Outdated
Show resolved
Hide resolved
…cname-record-dialog.tsx Co-authored-by: leonardost <[email protected]>
This Pull Request is now available for translation here: https://translate.wordpress.com/deliverables/17235744 Some locales (Hebrew, Japanese) 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. Hi @StevenPartridge, could you please edit the description of this PR and add a screenshot for our translators? Ideally it'd include all of the following strings:
Thank you in advance! |
Translation for this Pull Request has now been finished. |
Related to # https://github.com/Automattic/nomado-issues/issues/1244
Proposed Changes
Why are these changes being made?
Testing Instructions
I'm still testing this, might need to adjust instructions a little bit
Pre-merge Checklist