Repository navigation
feat: Integrate the dual-editor in vanilla-web-component #369
Description
Description
Integrate @openworkflowspec/dual-editor in examples/vanilla-web-component, replacing the direct usage of @openworkflowspec/diagram-editor.
Motivation
Validate that the Dual Editor can be consumed correctly from a non-React host and that the package integration works in the existing vanilla Web Component example.
Proposed Implementation
- Replace the direct
@openworkflowspec/diagram-editorintegration with@openworkflowspec/dual-editor. - Update the Web Component wrapper and example as needed.
- Update the existing tests to cover the Dual Editor integration.
Definition of Done
- Implementation: Fully implemented according to the Open Workflow spec.
- Unit Tests: Comprehensive unit tests are included and passing.
- Integration Tests: Verified within the monorepo and target environments (Web/VS Code).
- Documentation: Updated README.md, ADRs, or official docs.
- Performance: No significant regression in editor responsiveness.
- Accessibility: UI changes comply with accessibility standards.
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
fantonangeli commentedon Oct 29, 2026
@kumaradityaraj when you update the Vanilla's README, could you please add these instruction for Shadow DOM consumers:
Shadow DOM integration
Monaco Editor has known issue when embedded inside Shadow DOM: diagnostic underlines appear, but their hover messages may not be visible.
As a temporary workaround, stop
mousemovepropagation on the editor's mount container:The container must be inside the Shadow Root and wrap the Text Editor.