-
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
Remove Is Reskinned Flag: Remove from user and notice sections - Attempt 2 #99354
Remove Is Reskinned Flag: Remove from user and notice sections - Attempt 2 #99354
Conversation
Jetpack Cloud live (direct link)
Automattic for Agencies live (direct link)
|
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 |
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: App Entrypoints (~17 bytes removed 📉 [gzipped])
Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used. Sections (~231 bytes removed 📉 [gzipped])
Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to. Async-loaded Components (~226 bytes removed 📉 [gzipped])
React components that are loaded lazily, when a certain part of UI is displayed for the first time. 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. |
6442e7b
to
ded6575
Compare
@oswian @jjchrisdiehl really appreciate a review on this PR :) |
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 completed a first pass over the code and have left a couple of small comments. I also tested a few different instances of the Notice
component and didn't spot any obvious issues relating to the changes.
However as the Notice
component is used so widely, I definitely recommend having familiar eyes review the changes before merging.
Also just for context -- I'm wondering why particular instances of Notice
deviate from the default theme. It doesn't seem ideal in terms of design consistency 🤔
@@ -43,7 +43,7 @@ export const TimeMismatchWarning: FC< ExternalProps > = ( { | |||
const dismissClick = () => dispatch( savePreference( dismissPreference, 1 ) ); | |||
|
|||
return ( | |||
<Notice status={ status } onDismissClick={ dismissClick }> |
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.
Should this instance of the notice actually use the default/dark theme, as it wasn't using the isReskinned
prop?
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.
Nice catch, distinctly remember seeing the is-reskinned
class in the snapshot when running tests here but looks like it was from my own changes.
@@ -269,7 +269,9 @@ export class JetpackConnectNotices extends Component { | |||
if ( noticeValues ) { | |||
return ( | |||
<div className="jetpack-connect__notices-container"> | |||
<Notice { ...noticeValues }>{ this.renderNoticeAction() }</Notice> |
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.
Similar again here. It didn't have the isReskinned
prop enabled, so is the theme="light"
is correct?
Good call out @oswian I raised this on p2! pdvytD-Yh-p2 |
52c4221
to
9b88a15
Compare
c0fe2bc
to
01b7ed3
Compare
@oswian given that now the approach is a themed based approach I think this is relatively safe to ship. |
Proposed Changes
dark
isReskinned
flag#Testing Instructions
/purchases/subscriptions/<site-id>
) -> and plan purchase page, make sure the dark themed notice appears.