GTW-9643: make client color schemes read-only & non-persistent & don't set scheme when installing the plugins on host

they shouldn't be changed from the host side anyway & they are already non-persistent, but proper scheme state will help them not get erased on plugin changes.

GitOrigin-RevId: 7fcfdb73d92d62b73ea49232a57af9c512503cfc
This commit is contained in:
Maria Filipanova
2024-09-20 11:14:52 +02:00
committed by intellij-monorepo-bot
parent 92c0d908c9
commit b77f693c7f

View File

@@ -7,6 +7,7 @@ import com.intellij.ide.plugins.DynamicPluginListener
import com.intellij.ide.plugins.IdeaPluginDescriptor
import com.intellij.ide.ui.LafManager
import com.intellij.ide.ui.UIThemeProvider
import com.intellij.idea.AppMode
import com.intellij.openapi.application.EDT
import com.intellij.openapi.components.Service
import com.intellij.openapi.components.service
@@ -52,7 +53,7 @@ internal class LafDynamicPluginManager(private val coroutineScope: CoroutineScop
manager.updateLafComboboxModel()
// when updating a theme plugin that doesn't provide the current theme, don't select any of its themes as current
if (!manager.autodetect && (!isUpdatingPlugin || newItem.id == themeIdBeforePluginUpdate)) {
if (!AppMode.isRemoteDevHost() && !manager.autodetect && (!isUpdatingPlugin || newItem.id == themeIdBeforePluginUpdate)) {
scheduleLafChange(newItem.theme.get())
}
}