Skip to content

Preset system: delete legacy door/window presets UI #339

@wass08

Description

@wass08

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

  • git grep -E "PresetsPopover|presets-context|getDoorPresetData|getWindowPresetData" returns zero matches in pascalorg/editor
  • Opening a door in the editor shows the regular parametric inspector with no popover trigger
  • Same for window
  • bun typecheck passes
  • No regression in the door/window parametric editing flow (sliders, dropdowns, dimensions still work)

Blocked by

None - can start immediately.

Metadata

Metadata

Assignees

No one assigned

    Labels

    cleanupTask related to ensure the code stays clean long termready-for-agentReady for an autonomous agent to pick up

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions