-
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
Themes: Add current-theme query component #5361
Conversation
Replaces the old-style fetcher component.
85aa01e
to
fcc292a
Compare
The (visual) current theme component isn't updated for me when activating a theme on a Jetpack site, and even the thanks modal display's the previous theme's name :-( |
Actually, not just on Jetpack sites... |
case THEME_ACTIVATE: | ||
return state.set( 'isActivating', true ); | ||
case THEME_ACTIVATED: | ||
return state | ||
.set( 'isActivating', false ) | ||
.set( 'hasActivated', true ) | ||
.setIn( [ 'currentThemes', action.site.ID ], action.theme ); | ||
.setIn( [ 'currentThemes', action.siteId ], action.theme ); |
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.
@ockham: this is the problem—overzealous trimming of site
usage. Fixing...
fixed in b2ba232 |
Loving it. Squash it, 🚢 it! Aside — Can we incorporate |
Yeah, was mulling that over myself, definite next step. Thanks for review :) |
Replaces the old-style fetcher component.
A query component to replace the old-style fetcher component. Will make it very easy to determine current theme properly in theme sheets (#5285)
No visual changes
To Test
Expected: the CURRENT THEME bar works as previously
Things to check:
localStorage.clear();
in console then refresh