Consolidate workbench layout & views/panel persistence #61777
Labels
debt
Code quality issues
layout
General VS Code workbench layout issues
*out-of-scope
Posted issue is not in scope of VS Code
workbench-state
UI state across restarts
Milestone
Once the workbench layout is driven by the grid widget (#50853) I suggest we also revisit how layout information and view/panels are persisted.
Today we are leveraging the following keys (some global, some workspace):
Sidebar
workbench.sidebar.activeviewletid
workbench.sidebar.width
workbench.sidebar.hidden
Panel
workbench.panelpart.activepanelid
workbench.panel.width
workbench.panel.height
workbench.panel.hidden
workbench.panel.pinnedpanels
workbench.panel.sizebeforemaximized
workbench.panel.location
Activity Bar
workbench.activity.pinnedviewlets
workbench.activity.placeholderviewlets
Layout
editorpart.centeredview
workbench.centerededitorlayout.active
workbench.zenmode.active
Splash
parts-splash-data
View Related
scm.views
viewservice.workbench.view.{id}.enablement
{view-id}.numberOfVisibleViews
(e.g.workbench.view.explorer.numberofvisibleviews
){view-id}.state
(e.g.workbench.explorer.views.state
){view-id}.state.hidden
(e.g.workbench.explorer.views.state.hidden
)viewservice.*
I think I would prefer a model where we maybe have just one top level key for this information and then update that when the layout changes. Or at least try to consolidate some keys that belong together.
@sandy081 maybe you yould update the View Related section and outline what purpose these keys serve and if they are required in the future. I am a little bit lost to understand the semantics of the keys you introduced.
The text was updated successfully, but these errors were encountered: