Editor State

The EditorState is the heart of ProseMirror. It’s a complete, immutable snapshot of your editor at any moment in time. Understanding how state works is crucial for building features and debugging issues.

What is EditorState?

EditorState is an immutable object that contains everything about your editor:

The document - All content and structure
The selection - Cursor position or text selection
Plugin state - Data maintained by plugins
Stored marks - Active formatting for next input

Immutability is key: You never modify an EditorState. Every change creates a new state through a transaction.

Creating the Initial State

In Euclides, the state is created in EditorEngine.create() (editor-engine.ts:20):

import { EditorState } from "prosemirror-state";
import { EuclidesEditorSchema } from "./schema/euclides-schema";
import { buildPlugins } from "./plugins/euclides-plugins";

static create(element: HTMLElement, stateService: EditorStateService): EditorView {
  const state = EditorState.create({
    // The Schema establishes document rules
    schema: EuclidesEditorSchema,

    /* 
     * Plugins extend editor behavior:
     * - Keyboard shortcuts
     * - History (undo/redo)
     * - Custom logic
     * - Sync with EditorStateService (Angular)
     */
    plugins: buildPlugins(stateService)
  });

  return new EditorView(element, {
    state,
    attributes: { class: 'euclides-editor' }
  });
}

This creates a state with:

An empty document (following the schema’s rules)
A selection at the start (position 0)
All plugins initialized

The Three Core Components

1. Document

The document is a tree structure of nodes defined by your schema:

// Accessing the document
const doc = state.doc;

// Document properties
console.log(doc.type.name);        // "doc" (root node)
console.log(doc.content.size);     // Number of nodes
console.log(doc.textContent);      // All text concatenated

// Iterate through children
doc.forEach((node, offset, index) => {
  console.log(`Node ${index}: ${node.type.name}`);
});

The document:

Must always match the schema rules
Cannot be partially invalid
Is never directly modified

2. Selection

The selection represents the cursor or highlighted text:

const selection = state.selection;

// Selection properties
console.log(selection.from);       // Start position
console.log(selection.to);         // End position
console.log(selection.empty);      // True if cursor (not range)

// Get selected text
const selectedText = state.doc.textBetween(
  selection.from,
  selection.to
);

// Check what's around the selection
const $from = selection.$from;     // "Resolved" position
console.log($from.parent.type.name);  // Parent node type
console.log($from.depth);          // Nesting depth

The $ prefix (like $from) indicates a resolved position - a position that knows its context in the document tree. This is a ProseMirror convention.

3. Plugins

Plugins are initialized with the state and can store their own data. Euclides uses several plugins (euclides-plugins.ts:31):

export function buildPlugins(stateService: EditorStateService) {
  return [
    buildEuclidesKeymap(EuclidesEditorSchema),  // Custom keyboard shortcuts
    keymap(baseKeymap),                         // Base ProseMirror shortcuts
    history(),                                  // Undo/redo functionality
    buildHistoryStatePlugin(stateService),      // Sync with Angular
  ];
}

Each plugin can:

React to transactions
Store its own state
Intercept events
Provide commands

Transactions: The Only Way to Change State

A Transaction (tr) is a description of changes to apply to a state. Transactions are the only way to create a new state.

Creating a Transaction

// Start with current state
const tr = state.tr;

// Make changes
tr.insertText("Hello", 1);           // Insert at position 1
tr.delete(5, 10);                    // Delete from 5 to 10
tr.addMark(1, 5, schema.marks.bold); // Apply bold

// Apply the transaction
const newState = state.apply(tr);

The original state is unchanged! You must use newState going forward. In practice, the EditorView handles this for you.

Example: Applying a Link

Here’s how Euclides applies a link mark (euclides-rich-editor.component.ts:106):

applyLink(url: string) {
  const { state, dispatch } = this.view;
  const linkInfo = getLinkRange(state);

  const href = url.startsWith('http')
    ? url
    : 'https://' + url;

  if (linkInfo) {
    const { start, end, link } = linkInfo;

    // Create transaction
    dispatch(
      state.tr
        .removeMark(start, end, state.schema.marks['link'])
        .addMark(
          start,
          end,
          state.schema.marks['link'].create({
            href,
            title: link.attrs['title']
          })
        )
    );
  } else {
    const from = state.selection.from;

    const tr = state.tr.insertText(href, from);
    tr.addMark(
      from,
      from + href.length,
      state.schema.marks['link'].create({ href, title: href })
    );

    dispatch(tr);
  }

  this.view.focus();
  this.closePopover();
}

This transaction:

Removes any existing link mark
Adds a new link mark with updated href
Dispatches through dispatch() to apply it

The Dispatch Function

The dispatch function is provided by EditorView:

const { state, dispatch } = view;

// Create and apply transaction
dispatch(state.tr.insertText("Hello"));

When you call dispatch(tr):

Plugins get to see and modify the transaction
A new state is created
The EditorView updates to show the new state
Plugin appendTransaction hooks can add follow-up changes

EditorStateService: Bridge to Angular

Euclides uses an Angular service to expose editor state to components (editor-state.service.ts:4):

import { Injectable, signal } from '@angular/core';

@Injectable({ providedIn: 'root' })
export class EditorStateService {
  canUndo = signal(false);
  canRedo = signal(false);
}

This service:

Uses Angular signals for reactivity
Gets updated by plugins when state changes
Allows toolbar buttons to enable/disable based on state

History State Plugin

The buildHistoryStatePlugin watches for state changes and updates the service:

// Simplified example of what the plugin does
function buildHistoryStatePlugin(stateService: EditorStateService) {
  return new Plugin({
    view() {
      return {
        update(view) {
          const { state } = view;
          
          // Check if undo/redo are available
          stateService.canUndo.set(undo(state));
          stateService.canRedo.set(redo(state));
        }
      };
    }
  });
}

Now Angular components can react:

<button 
  [disabled]="!editorStateService.canUndo()"
  (click)="undo()">
  Undo
</button>

State Updates Flow

Here’s the complete flow when the user types:

Working with State in Commands

Commands are functions that take state and optionally dispatch:

type Command = (
  state: EditorState,
  dispatch?: (tr: Transaction) => void,
  view?: EditorView
) => boolean;

The component calls commands through the service (euclides-rich-editor.component.ts:41):

toggleBold() {
  if (this.editorCommandsService.toggleBold(this.view)) {
    this.view.focus();
  }
}

toggleAlign(align: string) {
  if (this.editorCommandsService.setTextAlign(align, this.view))
    this.view.focus();
}

A typical command implementation:

// In EditorCommandsService
toggleBold(view: EditorView): boolean {
  const { state, dispatch } = view;
  const markType = state.schema.marks.strong;
  
  // toggleMark is a ProseMirror command
  return toggleMark(markType)(state, dispatch);
}

Commands return true if they succeeded (state changed) or false if they couldn’t apply (e.g., mark not allowed in current position).

State Inspection Patterns

Check Active Marks

const { $from, $to } = state.selection;
const boldMark = state.schema.marks.strong;

const isBold = boldMark.isInSet(state.storedMarks || $from.marks());

Check Current Node Type

const { $from } = state.selection;
const currentNode = $from.parent;

if (currentNode.type === state.schema.nodes.heading) {
  console.log(`Heading level: ${currentNode.attrs.level}`);
}

Get Node at Position

const pos = 10;
const resolvedPos = state.doc.resolve(pos);
const nodeAtPos = resolvedPos.parent;

console.log(`Node type: ${nodeAtPos.type.name}`);

Undo/Redo with History

The history() plugin tracks state changes (euclides-rich-editor.component.ts:72):

import { undo, redo } from 'prosemirror-history';

undo() {
  if (undo(this.view.state, this.view.dispatch))
    this.view.focus();
}

redo() {
  if (redo(this.view.state, this.view.dispatch))
    this.view.focus();
}

The history plugin:

Stores previous states
Groups rapid changes (like typing) into single undo steps
Provides undo and redo commands
Can be configured with depth limits

History works automatically because EditorState is immutable. Old states are naturally preserved!

State vs Props

Be careful to distinguish:

EditorState - ProseMirror’s immutable state
Component state - Angular component properties

Example from the component (euclides-rich-editor.component.ts:82):

// Angular component state (mutable)
showLinkPopover: boolean = false;
currentLink: string = '';

// ProseMirror state (immutable, in this.view)
openLinkPopover() {
  const { state } = this.view;  // EditorState
  
  const linkInfo = getLinkRange(state);
  this.currentLink = linkInfo?.link.attrs['href'] ?? '';
  this.showLinkPopover = true;  // Component state
}

Why Immutability Matters

Undo/Redo is Free

Since old states are preserved, undo is just “use the previous state”. No need to track inverse operations.

Time-Travel Debugging

You can store states and jump to any point in history. Invaluable for debugging complex interactions.

Predictable Updates

No hidden mutations. Every change is explicit through transactions, making code easier to reason about.

Concurrent Editing

Immutability makes collaborative editing possible. Changes are applied as transformations, not direct edits.

Plugin Composition

Multiple plugins can inspect and modify the same transaction without stepping on each other’s toes.

Common Patterns

Pattern: Command with Dispatch

function myCommand(state: EditorState, dispatch?: Dispatch): boolean {
  // Check if command can execute
  if (!canExecute(state)) {
    return false;
  }
  
  // If dispatch provided, execute
  if (dispatch) {
    const tr = state.tr;
    // ... make changes to tr
    dispatch(tr);
  }
  
  return true;
}

Pattern: Get Selection Content

const { from, to } = state.selection;
const selectedText = state.doc.textBetween(from, to);
const selectedFragment = state.doc.slice(from, to).content;

Pattern: Update Node Attributes

const { $from } = state.selection;
const pos = $from.before($from.depth);
const node = $from.parent;

const tr = state.tr.setNodeMarkup(
  pos,
  null,  // Keep same type
  { ...node.attrs, textAlign: 'center' }  // Update attrs
);

dispatch(tr);

Best Practices

Never Mutate

Never modify state directly. Always create transactions.

Check Before Dispatch

Commands should return false if they can’t execute, true if they can.

Batch Changes

Make multiple changes in one transaction, not separate transactions.

Use Commands

Prefer built-in commands over manual transaction building when possible.

Next Steps

Architecture

See how state fits into the overall architecture

Schema

Learn how schema defines document structure

Nodes vs Marks

Understand content vs formatting

Get Started

Core Concepts

Components

Guides

What is EditorState?

Creating the Initial State

The Three Core Components

1. Document

2. Selection

3. Plugins

Transactions: The Only Way to Change State

Creating a Transaction

Example: Applying a Link

The Dispatch Function

EditorStateService: Bridge to Angular

History State Plugin

State Updates Flow

Working with State in Commands

State Inspection Patterns

Check Active Marks

Check Current Node Type

Get Node at Position

Undo/Redo with History

State vs Props

Why Immutability Matters

Common Patterns

Pattern: Command with Dispatch

Pattern: Get Selection Content

Pattern: Update Node Attributes

Best Practices

Never Mutate

Check Before Dispatch

Batch Changes

Use Commands

Next Steps

Architecture

Schema

Nodes vs Marks

Build docs developers (and LLMs) love

Get Started

Core Concepts

Components

Guides

Documentation Index

​What is EditorState?

​Creating the Initial State

​The Three Core Components

​1. Document

​2. Selection

​3. Plugins

​Transactions: The Only Way to Change State

​Creating a Transaction

​Example: Applying a Link

​The Dispatch Function

​EditorStateService: Bridge to Angular

​History State Plugin

​State Updates Flow

​Working with State in Commands

​State Inspection Patterns

​Check Active Marks

​Check Current Node Type

​Get Node at Position

​Undo/Redo with History

​State vs Props

​Why Immutability Matters

​Common Patterns

​Pattern: Command with Dispatch

​Pattern: Get Selection Content

​Pattern: Update Node Attributes

​Best Practices

Never Mutate

Check Before Dispatch

Batch Changes

Use Commands

​Next Steps

Architecture

Schema

Nodes vs Marks

Build docs developers (and LLMs) love

What is EditorState?

Creating the Initial State

The Three Core Components

1. Document

2. Selection

3. Plugins

Transactions: The Only Way to Change State

Creating a Transaction

Example: Applying a Link

The Dispatch Function

EditorStateService: Bridge to Angular

History State Plugin

State Updates Flow

Working with State in Commands

State Inspection Patterns

Check Active Marks

Check Current Node Type

Get Node at Position

Undo/Redo with History

State vs Props

Why Immutability Matters

Common Patterns

Pattern: Command with Dispatch

Pattern: Get Selection Content

Pattern: Update Node Attributes

Best Practices

Next Steps