-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Blaze: Show Blaze in general section #20314
Conversation
Generated by 🚫 dangerJS |
You can test the changes in WordPress from this Pull Request by:
|
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.
Works as described 🚀
Left one small comment.
CGSize iconSize = CGSizeMake(BlogDetailGridiconSize, BlogDetailGridiconSize); | ||
UIImage *blazeIcon = [[UIImage imageNamed:@"icon-blaze"] resizedImage:iconSize interpolationQuality:kCGInterpolationHigh]; | ||
BlogDetailsRow *blazeRow = [[BlogDetailsRow alloc] initWithTitle:NSLocalizedString(@"Blaze", @"Noun. Links to a blog's Blaze screen.") | ||
accessibilityIdentifier:@"Blaze Row" | ||
image:[blazeIcon imageFlippedForRightToLeftLayoutDirection] | ||
imageColor:nil | ||
renderingMode:UIImageRenderingModeAlwaysOriginal | ||
callback:^{ | ||
[weakSelf showBlaze]; | ||
}]; | ||
blazeRow.showsSelectionState = NO; |
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] What do you think of extracting this to a helper that creates a Blaze row to avoid code duplication?
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.
Done! 10e18e7
You can test the changes in Jetpack from this Pull Request by:
|
FYI @mokagio 🙇♀️ |
Description
Shows the Blaze menu item in the general section. The general section is shown if the jetpack section isn't shown.
Note
The base branch for this PR will automatically update to
release/21.9
once #20290 gets merged intorelease/21.9
How to test
Regression Notes
Potential unintended areas of impact
n/a
What I did to test those areas of impact (or what existing automated tests I relied on)
n/a
What automated tests I added (or what prevented me from doing so)
n/a
PR submission checklist:
RELEASE-NOTES.txt
if necessary.