NDV components migrated to document store facade
NDV components in the editor are being updated to use a unified document store instead of directly accessing workflowObject, laying groundwork for CRDT support.
The NDV (Node Detail View) components in n8n's editor are being migrated from direct workflowObject access to a workflowDocumentStore facade pattern. This change affects node connection visualization, trigger panel logic, and expression editing — standardizing how components interact with workflow data.
By routing all access through the facade, the codebase becomes easier to reason about and maintain. The pattern also sets the stage for CRDT (Conflict-free Replicated Data Types), which will eventually allow real-time collaboration on workflows. Components get a cleaner interface; developers get a more predictable data flow.
This work touches four files in the NDV package: floating nodes display, sub-connections view, trigger panel, and the expression edit modal.
View Original GitHub Description
Summary
As part of the groundwork for introducing CRDT, this PR replaces direct workflowObject access in NDV components with workflowDocumentStore facade methods.
Related Linear tickets, Github issues, and Community forum posts
https://linear.app/n8n/issue/CAT-2692/migrate-ndv-panel-components-from-workflowobject-to
Review / Merge checklist
- PR title and summary are descriptive. (conventions) <!-- **Remember, the title automatically goes into the changelog. Use `(no-changelog)` otherwise.** -->
- Docs updated or follow-up ticket created.
- Tests included. <!-- A bug is not considered fixed, unless a test is added to prevent it from happening again. A feature is not complete without tests. -->
- PR Labeled with
Backport to Beta,Backport to Stable, orBackport to v1(if the PR is an urgent fix that needs to be backported)