Feature Flags

@lyfie/luthor uses feature flags to control what each preset can do, without forking runtime logic.

Source of truth

Canonical keys are defined in packages/luthor/src/presets/extensive/extensions.tsx as EXTENSIVE_FEATURE_KEYS.

type FeatureFlag =
  | 'bold'
  | 'italic'
  | 'underline'
  | 'strikethrough'
  | 'fontFamily'
  | 'fontSize'
  | 'lineHeight'
  | 'textColor'
  | 'textHighlight'
  | 'subscript'
  | 'superscript'
  | 'link'
  | 'horizontalRule'
  | 'table'
  | 'list'
  | 'history'
  | 'image'
  | 'blockFormat'
  | 'code'
  | 'codeIntelligence'
  | 'codeFormat'
  | 'tabIndent'
  | 'enterKeyBehavior'
  | 'iframeEmbed'
  | 'youTubeEmbed'
  | 'floatingToolbar'
  | 'contextMenu'
  | 'commandPalette'
  | 'slashCommand'
  | 'emoji'
  | 'draggableBlock'
  | 'customNode'
  | 'themeToggle';

Default behavior

ExtensiveEditor starts with all feature flags enabled (DEFAULT_FEATURE_FLAGS).

Disable selectively:

<ExtensiveEditor
  featureFlags={{
    image: false,
    table: false,
    customNode: false,
    commandPalette: false,
  }}
/>

Preset enforcement

Some presets enforce specific flags to protect preset contracts:

• LegacyRichEditor: keeps metadata-heavy features off (table, image, embeds, custom nodes, draggable, palette/slash, emoji, theme toggle).
• SlashEditor: enforces slashCommand: true and commandPalette: false.
• HeadlessEditorPreset: keeps a lightweight metadata-friendly profile.
• SimpleEditor: hardcodes a minimal visual-only chat input profile.

Why enforcement exists

Preset contracts must stay stable. If a preset promises markdown/html-native behavior or slash-first behavior, enforced flags prevent accidental drift.

Feature groups

• Typography:
  • fontFamily, fontSize, lineHeight
• Inline formatting:
  • bold, italic, underline, strikethrough, subscript, superscript, codeFormat, textColor, textHighlight
• Document structure:
  • blockFormat, list, horizontalRule, table, tabIndent, enterKeyBehavior
• Rich content:
  • image, iframeEmbed, youTubeEmbed, customNode
• Productivity UI:
  • history, commandPalette, slashCommand, floatingToolbar, contextMenu, draggableBlock, themeToggle, emoji
• Code workflows:
  • code, codeIntelligence

Full flag reference

Contributor rules

• Add new flags only in EXTENSIVE_FEATURE_KEYS.
• Reflect the flag in DEFAULT_FEATURE_FLAGS.
• Wire the flag into extension assembly in buildExtensiveExtensions(...).
• Update preset-specific policies if needed.
• Update docs that describe preset behavior.