ClassicDataView

Connects DataView to Classic UI, with replaceable workspace and layout ports.

@quirekit/classic-editor · AGPL-3.0-only

Editor compatibility

Layer：Classic product integration

“Supported” means the product assembly above exists; interaction, host services and file formats retain their own conditions. See status and integration rules. Licensing is shown separately.

Installation

pnpm add @quirekit/classic-editor@alpha

This optional product extension belongs in createClassicEditor extensions and still follows the Core Extension contract.

import { ClassicDataView } from '@quirekit/classic-editor'

Use compatible versions available from your distribution source. This site uses the Alpha workspace. License labels come from package metadata; see support and licensing.

Integration by editor

These snippets use an existing host element named element. The host owns container sizing and persistence; call instance.destroy() on teardown. Avoid duplicating preset capabilities and supply required host ports before installation.

import { createClassicEditor } from '@quirekit/classic-editor'
import '@quirekit/classic-editor/styles.css'
import { ClassicDataView } from '@quirekit/classic-editor'

const instance = createClassicEditor({
  element,
  extensions: [ClassicDataView],
})

Configuration

These are extension-level defaults. Presets can override them; they are distinct from current document attributes. See configuration.

open

Open an authoring workspace for the captured target and return a disposable UI task. Recheck the target before asynchronous submission.

Type：(request: DataViewEditRequest, editor: QuireEditor): { close(): void; }

Default：open

layouts

Return host-owned layout-provider registrations for the data view.

Type：(): { layoutDependency: { kind: "document"; }; id: string; nodeTypes: readonly string[]; capabilities: readonly QuireLayoutProviderCapabilityKind[]; provider: QuireLayoutProvider; }[]

Default：() => [dataViewLayout()]

Commands and runtime

These commands are supplied directly by this extension. Availability depends on the installed schema, selection and protection policy; query editor.can() first.

These are parameter signatures. See commands and controls to connect UI while retaining one transaction/history authority.

Next steps

Return to all plugins, or read configuration to distinguish options, attributes and commands.

Continue with Classic quick start and configuration/lifetime. See product plugin development for your own UI and services.