ADITO Code Preview
ADITO Code Preview makes linked YAML artifacts behave like normal code definitions in VS Code. It understands both explicit project paths and the symbolic names used by artifact files in yaml-reference.
For example, these values resolve to their matching YAML files:
Entity:
entity: Absence_entity
Views:
editView: AbsenceEdit_view
Parent:
parent: /contexts/Absence/entity/Absence_entity.entity.yaml
Source:
recordContainer: db
How references are resolved
/contexts/Absence/...yaml is treated as project-root relative. The extension searches upward from the current file, so projects nested inside a larger workspace still work.
./other.yaml and ../other.yaml are resolved relative to the current YAML file.
- Symbolic values such as
Absence_entity are matched against filenames such as Absence_entity.entity.yaml.
- When a symbolic name occurs more than once, files in the current context are ranked first. All remaining candidates are available in Peek.
- Only AOD and YAML targets are indexed; ordinary scalar values remain ordinary text when no matching artifact exists.
Navigating references
ADITO Code Preview plugs into VS Code's standard definition providers, so the built-in navigation commands work on every resolved reference.
Hover
Open a YAML file and hover a linked value. The hover shows the resolved file and a read-only preview of its YAML content.
Go to Definition
Press F12 to jump directly to the target file. This runs the standard VS Code command editor.action.revealDefinition (Go to Definition).
Peek Definition
Press Alt+F12 to open the target in VS Code's Peek editor without leaving the current file. This runs the standard VS Code command editor.action.peekDefinition (Peek Definition). Peek is a built-in VS Code feature, so you can edit the target inline and save with Ctrl+S (Cmd+S on macOS). Press Escape to close Peek and remain in the original YAML file.
For a Peek window that stays open while navigating its results, the VS Code setting below is useful:
"editor.stablePeek": true
Open in editor
Alt+click (Option+click on macOS) the value to open its existing target normally.
Navigating into node_modules
Both Go to Definition and Peek Definition also work for references that point into the node_modules folder, as long as those files are not excluded by the files.exclude setting. If a folder is excluded, its files are not indexed and cannot be resolved.
Note: Editing files inside node_modules through Peek is risky, because the changes are usually overwritten on the next install.
It may happen that VS Code excludes node_modules from workspace searches, so its files are not indexed. To make references into node_modules resolvable, set the pattern to false in files.exclude:
{
"files.exclude": {
"**/node_modules": false
}
}
Setting the value to true keeps node_modules out of the index, and references into that folder cannot be resolved.
Keeping the index fresh
If files are added by an external generator and do not appear immediately, run ADITO Code Preview: Refresh Reference Index from the Command Palette.
Settings
aditoCodePreview.caseSensitive: require exact name case (default: true).
aditoCodePreview.maxResults: cap ambiguous Peek results (default: 20).
files.exclude: omit generated or dependency folders from the YAML reference index.
aditoCodePreview.showWorkflowHover: show the short navigation hint.
aditoCodePreview.hoverPreviewLines: number of target lines shown in the hover (default: 24).
- The extension defaults
editor.multiCursorModifier to ctrlCmd, so Alt/Option+click opens definitions and Ctrl/Cmd+click adds a cursor. An explicit user setting takes precedence.