Skip to content

Conversation

@dcalhoun
Copy link
Member

What?

Organize editor setup logic.

Why?

Reduce duplication. Improve readability.

How?

  • Colocate related logic.
  • Add JSDocs for functions.
  • Extract platform-detection logic.

Testing Instructions

Smoke test the editor.

Accessibility Testing Instructions

N/A, no user-facing changes.

Screenshots or screencast

N/A, no user-facing changes.

@dcalhoun dcalhoun added the [Type] Code Quality Issues or PRs that relate to code quality label Nov 29, 2025
Node.js ESM stictly follows the ECMAScript spec, which requires module
file endings. Vite, however, is more forgiving. We could consider
updating all project imports for consistency.
@dcalhoun dcalhoun force-pushed the refactor/organize-editor-setup branch from 6b6532b to c5c8bdd Compare November 29, 2025 12:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[Type] Code Quality Issues or PRs that relate to code quality

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants