Skip to content

arch: split ownership of content-panel definitions #270

Description

@cursor

Problem

Panel definitions are split across two homes, making ownership unclear and encouraging features to depend directly on shell internals.

  • Files panels live in features/files/ and import shell APIs from components/layout/content-panel/
  • Peer panels (terminal, diff, browser) live under components/layout/content-panel/panels/
  • Registration happens in the composition root (routes/__root.tsx)

Severity

P3

Suggested fix

Pick one convention:

  • Move filesPanel / filePanel under components/layout/content-panel/panels/ and keep only view logic in features/files/, or
  • Move all panel definitions into their owning features and keep components/layout/content-panel/ as host infrastructure only.

Features should not need to reach into shell panel wiring beyond what the composition root imports.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions