You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run CALM: Open Preview, go to the Docify preview, and click the CALM Hub API node, which has details.detailed-architecture set to calm-hub-detail.architecture.json.
When clicking on CALM model elements tree structure in navigation panel, the CALM Hub API view from calm-3.json is shown, not calm-hub-detail.architecture.json.
Expected Result:
Clicking CALM Hub API should open calm/architecture/calm-hub-detail.architecture.json, and the VS Code extension preview should retarget to the detailed architecture document.
Actual Result:
The preview stays focused on calm-3.json and only re-shows the current parent architecture instead of displaying the detailed-architecture target document. The child architecture is not shown in the preview after the click.
No exception or stack trace was observed for the original bug behavior. The issue presents as incorrect navigation/preview behavior rather than a thrown error.
Environment:
VSCode: 131.0
VS Code extension: calm-vscode-plugin version 0.6.0. The issue also shows up with the 0.7.0 version that is in the repo but not released.
I assume URL and file references in details.detailed-architecture are valid.
The issue is specifically about node-level details.detailed-architecture navigation from the VS Code extension preview. In calm/architecture/calm-3.json, the CALM Hub API node points to calm-hub-detail.architecture.json, but clicking that node in the Docify preview reselects or rerenders the parent document instead of navigating to the child document.
A last note, use of details.detailed-architecture in timeline moment navigation works as expected, i.e., displays the referenced file. I was expecting the same behavior when details.detailed-architecture is in a CALM json file.
Here is video demonstrating the issue (Turn on sound to hear narration):
2026-08-01.13-09-21.mov
State of my local repo where the issue surfaces.
$ git log -n 5 --oneline
25be3b52 (HEAD -> main, upstream/main, upstream/HEAD, origin/main, origin/HEAD) fix: resolve open CodeQL code scanning alerts (75-79) (#2919)
4dbb561e docs: embed live CALM architecture diagram via @finos/calm-docusaurus-plugin (#2909)
0852651a Merge pull request #2917 from rocketstack-matt/fix/security-deps-npm-2026-07-30
7c06bf40 chore(deps): patch npm brace-expansion DoS across all resolved major lines
Bug Report
Steps to Reproduce:
calm/architecture/calm-3.json.CALM: Open Preview, go to the Docify preview, and click theCALM Hub APInode, which hasdetails.detailed-architectureset tocalm-hub-detail.architecture.json.CALM Hub APIview fromcalm-3.jsonis shown, notcalm-hub-detail.architecture.json.Expected Result:
Clicking
CALM Hub APIshould opencalm/architecture/calm-hub-detail.architecture.json, and the VS Code extension preview should retarget to the detailed architecture document.Actual Result:
The preview stays focused on
calm-3.jsonand only re-shows the current parent architecture instead of displaying thedetailed-architecturetarget document. The child architecture is not shown in the preview after the click.No exception or stack trace was observed for the original bug behavior. The issue presents as incorrect navigation/preview behavior rather than a thrown error.
Environment:
calm-vscode-pluginversion0.6.0. The issue also shows up with the0.7.0version that is in the repo but not released.Additional Context:
Used the VSCode Extenstion Multi-Document Navigation as basis for this test.
I assume URL and file references in
details.detailed-architectureare valid.The issue is specifically about node-level
details.detailed-architecturenavigation from the VS Code extension preview. Incalm/architecture/calm-3.json, theCALM Hub APInode points tocalm-hub-detail.architecture.json, but clicking that node in the Docify preview reselects or rerenders the parent document instead of navigating to the child document.A last note, use of
details.detailed-architecturein timeline moment navigation works as expected, i.e., displays the referenced file. I was expecting the same behavior whendetails.detailed-architectureis in a CALM json file.Here is video demonstrating the issue (Turn on sound to hear narration):
2026-08-01.13-09-21.mov
State of my local repo where the issue surfaces.