Fix regression where themeDetails are not persisted to appdata file#2447
Merged
fredrikekelund merged 3 commits intotrunkfrom Jan 22, 2026
Merged
Fix regression where themeDetails are not persisted to appdata file#2447fredrikekelund merged 3 commits intotrunkfrom
themeDetails are not persisted to appdata file#2447fredrikekelund merged 3 commits intotrunkfrom
Conversation
Collaborator
📊 Performance Test ResultsComparing db33316 vs trunk site-editor
site-startup
Results are median values from multiple test runs. Legend: 🟢 Improvement (faster) | 🔴 Regression (slower) | ⚪ No change |
fredrikekelund
commented
Jan 22, 2026
Comment on lines
+282
to
284
| // Update a site's details (name, custom domain, PHP version, etc). This function calls the | ||
| // `site set` CLI command and updates the `SiteServer` instance after the CLI completes. | ||
| export async function updateSite( |
Contributor
Author
There was a problem hiding this comment.
This function was previously used ambiguously (see #2360 (comment) and PR description). I've removed the last place where it was being used to update the appdata file (which it no longer did, anyway). I added this comment to prevent future confusion.
bcotrim
approved these changes
Jan 22, 2026
Contributor
bcotrim
left a comment
There was a problem hiding this comment.
LGTM 👍
The workflow is clearer and I didn't find any regressions
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related issues
Proposed Changes
We recently introduced a regression where
SiteDetails.themeDetailsobjects stopped being persisted to the appdata file. This caused two problems:Site Editor, etc). This happened becausethemeDetailsobject contained all empty values.SiteDetails.themeDetailsobject wasn't updated properly. Fix constant theme details refresh issue #2420 alleviated this problem, but it kept appearing due to the underlying regression.This PR fixes the problem by:
themeDetailsin a single function insrc/ipc-handlers.ts. Previously, there were multiple execution paths to achieve this, which I believe explains why this regression surfaced in the first place.updateSitecalls insrc/ipc-handlers.tsthat were using this function for an ambiguous purpose (maybe update the settings, but also update the appdata file).SiteDetails.persistThemeDetailsmethod that does what you'd expect (update thethemeDetailsobject of the site in the appdata file).thumbnail-load-errorto reset the loading state if there's an error when loading the thumbnail.Testing Instructions
npm start~/Library/Application\ Support/Studio/appdata-v1.json) and ensure that the site you just started has athemeDetailsobject that contains the values you'd expectPre-merge Checklist