Ranvier Dev Assist
한국어 문서
Ranvier Dev Assist is a development-assist extension for Ranvier projects.
It helps you validate circuit structure before runtime, navigate source quickly,
and review node-linked diagnostics in the IDE loop.
- Publisher:
cellaxon
- Extension ID:
cellaxon.ranvier-vscode
- Marketplace:
https://marketplace.visualstudio.com/manage/publishers/cellaxon
What It Does
- Visualizes circuits from
schematic.json
- Node click/select -> source jump (
source_location)
- Highlights nodes mapped to the active editor file
- Provides a sidebar panel (
Ranvier Circuit Nodes) for structure navigation
- Runs
Run Schematic Export from the extension UI
- Shows node-level diagnostics overlays from
diagnostics.json (webview + sidebar)
- Projects mapped node diagnostics into VSCode Problems panel
Quick Demo
Node click -> source jump:

Setup for a Ranvier Project
1) Add Ranvier dependencies
cargo add ranvier
cargo add tokio --features full
cargo add anyhow
2) Install Ranvier CLI and generate schematic
Install Ranvier CLI once:
cargo install ranvier-cli
Then run from workspace root:
ranvier schematic basic-schematic --output schematic.json
The extension reads:
<workspace-root>/schematic.json
<workspace-root>/diagnostics.json (optional)
3) Use in VSCode
- Command Palette ->
Ranvier: Open Circuit View
- Open
Ranvier Circuit Nodes in the Ranvier sidebar
- Click a node (webview/panel) to jump to source
- Use
Run Schematic Export to refresh schematic.json
- Use
Refresh Diagnostics to refresh diagnostics overlay
- Use
Ranvier: Refresh Circuit Data for manual full refresh
- Review file-level diagnostics in the Problems panel (
source: ranvier:*)
- Use
Ranvier: Reveal Circuit Node From Current Line to jump back from editor line to circuit focus
- Use
Ranvier: Go To Next Node Issue / Ranvier: Go To Previous Node Issue to navigate node-linked issues
- Default shortcuts:
Ctrl+Alt+N / Ctrl+Alt+P (macOS: Cmd+Alt+N / Cmd+Alt+P)
- If shortcuts conflict, override keys in VSCode
keybindings.json (see deploy guide section Keyboard Shortcuts (Team Override)).
- Team template file:
vscode/.vscode/keybindings.recommended.json (copy to your user keybindings.json).
- Optional profile templates:
keybindings.vim.json, keybindings.jetbrains.json, keybindings.mac.json.
Example diagnostics.json:
{
"diagnostics": [
{
"node_id": "inspect",
"severity": "error",
"message": "Inspector path timeout",
"source": "runtime"
},
{
"node_id": "ingress",
"severity": "warning",
"message": "Slow branch selected",
"source": "lint"
}
]
}
Required fields:
node_id (or nodeId)
severity (error, warning, info)
message
source
Settings:
ranvier.diagnostics.inputPath (default: diagnostics.json)
Recommended Team Loop (Before PR)
- Regenerate
schematic.json when Ranvier flow changes
- Verify node/edge changes in circuit view
- Confirm source-jump for changed key nodes
- Confirm active-file highlight matches expected nodes
- Record circuit impact summary in PR when needed
Commands
Ranvier: Open Circuit View
Ranvier: Refresh Circuit Data
Ranvier: Run Schematic Export
Ranvier: Reveal Node Source
Ranvier: Refresh Diagnostics
Ranvier: Reveal Circuit Node From Current Line
Ranvier: Go To Next Node Issue
Ranvier: Go To Previous Node Issue
Shortcut Conflict FAQ
General Conflict
- Q:
Ctrl+Alt+N/P does not work on my setup.
A: Open VSCode Keyboard Shortcuts and check conflicts, then override in keybindings.json using the team snippet from deploy guide.
Vim Conflict
- Q: Vim extension consumes the shortcut first.
A: Use a different chord (for example
Ctrl+Shift+Alt+N/P) and keep when: "editorTextFocus && !editorReadonly".
JetBrains Keymap Conflict
- Q: JetBrains keymap extension already uses a similar binding.
A: Remap Ranvier commands to an unused pair and document the team standard in your workspace guide.
macOS Global Shortcut Conflict
- Q: macOS global shortcut conflicts with
Cmd+Alt+N/P.
A: Rebind to another combo (for example Cmd+Shift+Alt+N/P) in VSCode keybindings.json.
Supported source mapping fields:
source_location
sourceLocation
metadata.source_location
metadata.sourceLocation
Supported edge endpoint fields:
source / target
from / to
Release/Operations Reference
docs/03_guides/vscode_extension_deploy.md