What to build
Retire the legacy door/window-only preset feature in the editor UI. A unified preset system is replacing it across both repos (see pascalorg/private-editor:plans/community-preset-system.md, Phase 0). The editor side of that cleanup is this issue.
Delete the PresetsPopover component, its supporting presets-context, and the getDoorPresetData / getWindowPresetData callbacks plus popover triggers wired into the door and window panels. The popover today supports save/apply/rename/delete/community-toggle for door+window presets and is hardcoded to those two kinds — none of it survives. No backward-compat shim.
materialPreset field on door/window schemas stays as-is: it's a parametric field, not part of the legacy preset system, and will naturally ride into the new preset node_data when those kinds become presettable through the unified system.
Coordinate timing with the community-side cleanup PR (pascalorg/private-editor) — the popover queries the community-side API, so this PR should land first to avoid leaving a popover wired to a deleted backend.
Acceptance criteria
Blocked by
None - can start immediately.
What to build
Retire the legacy door/window-only preset feature in the editor UI. A unified preset system is replacing it across both repos (see
pascalorg/private-editor:plans/community-preset-system.md, Phase 0). The editor side of that cleanup is this issue.Delete the
PresetsPopovercomponent, its supportingpresets-context, and thegetDoorPresetData/getWindowPresetDatacallbacks plus popover triggers wired into the door and window panels. The popover today supports save/apply/rename/delete/community-toggle for door+window presets and is hardcoded to those two kinds — none of it survives. No backward-compat shim.materialPresetfield on door/window schemas stays as-is: it's a parametric field, not part of the legacy preset system, and will naturally ride into the new presetnode_datawhen those kinds become presettable through the unified system.Coordinate timing with the community-side cleanup PR (
pascalorg/private-editor) — the popover queries the community-side API, so this PR should land first to avoid leaving a popover wired to a deleted backend.Acceptance criteria
git grep -E "PresetsPopover|presets-context|getDoorPresetData|getWindowPresetData"returns zero matches inpascalorg/editorbun typecheckpassesBlocked by
None - can start immediately.