An editor service gateway turns a request such as “open this resource” into a concrete editor, target group, and opening action. The caller stays deliberately thin: the explorer passes the resource and options, while the gateway resolves editor type, falls back to text handling, and delegates to an editor group. section 4.2
Use the gateway as the boundary between intent and implementation:
- Explorer UI requests an opening operation without reading files or rendering text. section 4.2
- Editor resolution selects specialized editors, such as a Markdown preview, or falls back to a text editor. section 4.2
- The selected editor group manages tabs and panes, keeping tab state separate from DOM rendering. section 4.2
Clicking a file in the explorer
A file click calls openEditor with the resource and options such as preserveFocus, pinned, and source. The gateway resolves the editor, chooses a group, and lets downstream loading handle memory buffers, backups, or disk data. section 4.2
