archify-vscode-ext/CHANGELOG.md

Changelog

0.10.3 — 2026-11-07

• Sync button in the title bar. Every Archify page (and .archify text editors) has a Sync button top right, next to Open in Text Editor: sign in, share a model, join one, set the server address. The status bar entry stays for those who show the status bar. archify.sync.titleButton: false hides the button.

0.10.2 — 2026-11-07

• Fixed: going back from Source to Model, Diagram or View left the YAML editor on the page under the picture when nothing had been edited. It now hides at once.

0.10.1 — 2026-11-06

• Archify Sync is easier to find. In workspaces with Archify files, Archify Sync sits in the status bar. Click it for a menu: sign in, share a model, join one, set the server address, open the settings. It shows the server you are signed in to, and the live state once a model is shared. archify.sync.statusBar: false hides it; nothing else changes without a server.
• Server address as a setting. archify.sync.server (empty by default, for example https://archify.example.com) is used by sign-in, share and the menu without asking. In the workspace settings it gives a whole project the same server. Archify | Set Sync Server Address… sets it.

0.10.0 — 2026-11-06

• Archify Sync (optional). Several people edit one model at once through a server you run yourself (archify-vscode-ext-sync); the files stay ordinary files on each disk. Commands: Sign in to Sync Server…, Share Model…, Copy Invite Link, Join Shared Model…, Publish Version…, Versions…, Stop Syncing Model…. Sign-in through the browser (PKCE), sessions in VS Code's secret storage, an Archify Sync account provider. Edits from editors, pages, Git and agents go out at once; others' edits arrive in open editors with undo intact. Everything is kept on the machine first, so work goes on offline and merges later. Teammates' cursors show as named carets in the Source view and in VS Code's text editors, and stay on their word while others type. The status bar shows who is here; the model page gets a Shared section with people, the file each has open, and the latest versions with Compare and Restore.
• Without a server nothing changes: the sync code is a separate bundle that loads only when a model in the workspace is shared, after a sign-in, or when a sync command or invite link is used.

0.9.3 — 2026-11-04

• Fixed: on a main.archify page in Source, Graph did nothing, and Model then showed the Graph page instead of the model. Graph now leaves Source and opens at once, and Model on the Graph page comes back to the model, not to Source.

0.9.2 — 2026-10-27

• Source view. Every Archify page can show its file's YAML in place: Diagram | Graph | Source on diagrams (the old Diagram | Graph switch, now on every diagram; Graph only inside a model), Model | Graph | Source on main.archify, View | Source on registry and decision pages, and Source on the Graph page too. The YAML opens in an editor inside the page, under its toolbar and heading, in the page's own colours: line numbers, folding, brackets, multiple cursors, undo and redo, ⌘S/Ctrl+S saves. Problems are underlined as you type, listed under the editor (click the count to go to the next one) and counted on the Source segment, also while the picture shows. Completion and hover come from the schema of the file, with nothing else installed. Edits go to the VS Code document, so the tab's dirty dot, save, Git and the text editor stay in step. Diagram (or Model, View) brings the picture back as it was left; anything rendered meanwhile shows then.
• 2D | 3D now sits left of the view switch (it says how the picture is drawn, the switch what is shown) and hides while Source shows; the 3D stage stops drawing meanwhile.
• Schema checks without the YAML extension. .archify files are checked against the extension's schema on the YAML as written, at once and with readable messages (Unknown key "lable" in connections[4].) on the key or value concerned; archify validate runs once the schema is satisfied. .archify-registry files are checked against the registry schema for the first time (types, unknown keys, ids). The decision schema is no longer handed to the YAML extension: decision files use the decision key twice by design, which it reported as an error in every file.
• Commands. Archify | Show Source switches the focused page to its Source view. The old behaviour, the YAML in VS Code's text editor beside the page, is Archify | Open in Text Editor, which is now the editor-title button.
• Registry and decision pages are text editors of their files (as diagram pages already were), so edits made there make the tab dirty and save with it.
• Fixed: a YAML error in a registry or decision file was reported on its first line instead of where it is.
• Fixed: an unhandled "Webview is disposed" error when a diagram closed while it was rendering. On main.archify pages with a diagram, the model heading no longer runs under the toolbar in narrow editors.

0.9.1 — 2026-10-23

• No functional change. Republished so that Open VSX carries the release: the 0.9.0 upload there was held under review while the root-at-skic namespace was still unverified, and a held upload is not released by the later ownership grant.

0.9.0 — 2026-10-21

• Model graph. A Model | Graph switch on the main.archify page (next to Export when the file has a diagram, top right otherwise) replaces the page with the whole model as one graph: every element any diagram draws plus every registry element, every connection between them, each once, drawn with Cytoscape.js in Archify's type colours. Registry elements have a solid border, inline ones a dashed border. Decisions and registry files are nodes as well: a decision is a tag coloured by status with dotted links to the elements and connections it is about and dashed links to what it supersedes; a registry links to the elements it defines. Layered layout by type (clients left, data right, registries above, decisions below, orthogonal connections) or a force layout; hover lights up an element and its connections; the dotted decision and registry links are shown by default; Links switches them to the selected element only. Drag, zoom, Fit, Labels, a dark/light theme toggle of its own (remembered, and shared with the diagram pages' theme key), legend chips that hide a type (decisions and registries included), Export PNG. The choice is remembered per file; the graph updates in place as the model changes.
• Queries. A query box narrows the graph: database, type:backend, diagram:0200-*, decision:<id>, uses:api, near:api,2, from:web to:db (shortest path), unused, shared, -shared, type:decision, type:registry; terms AND together, a leading - excludes; decisions and registries follow their elements into a result, and walks never pass through them; the count reads "9 of 14 elements"; ? lists the forms and runs an example on click.
• Side panel. An element shows its description, type, registry file and line (Registry opens it), the diagrams that draw it, its connections and its decisions, each one click away; Neighbours queries around it. A connection shows its labels, diagrams and decisions. A decision node shows its status, text, the elements and connections it is about and Open decision; a registry node the elements it defines and Open registry.
• Entry points. On a diagram page inside a model the switch reads Diagram | Graph and opens the graph narrowed to diagram:<that diagram>. New command Archify | Open Model Graph in the editor title, the Command Palette and the Explorer menu, wherever Open Model is.
• Diagram summaries in the model index now carry every node and edge of a diagram (shared and inline), which the graph is built from.

0.8.1 — 2026-10-20

• Archify | New Registry… on a folder (also File → New File… and the Command Palette) creates an .archify-registry file from the template and opens it.
• The Archify entries in the Explorer menu and File → New File… come in the order New Model, New Registry, New Diagram, New Decision.

0.8.0 — 2026-10-19

• Architecture decisions. A model can hold decisions: one *.archify-decision file each, anywhere under the model root, with an id (unique in the model), title, status, date, the registry elements and diagrams it is about, supersedes, and prose for context, decision and consequences.
• Diagrams point at decisions with decisions: [<id>] on the diagram, on a component, node or participant, and on a connection, edge, flow, transition or message. The key is stripped before Archify renders. Unknown ids, and the key outside a model, are reported in Problems. Completion, hover and go-to-definition for decision ids; in decision files the same for elements, diagrams and supersedes.
• Where they show. A Decisions panel on the main.archify page (one list, live decisions first, superseded and rejected dimmed and last). A Decisions rail panel under a diagram with the decisions it points at or that name it; hovering a row lights up the node or connection it is attached to, clicking opens the decision. A decision view when a .archify-decision file is opened: status, date, context, decision, consequences, related decisions, the elements as cards, the diagrams with where the decision is attached. Decisions also appear on element cards and in the element dialog.
• Authoring. Archify | New Decision… on a folder inside a model creates a decision file from a template, with the id taken from the title. Editor schema for decision files and the new decisions key. A decision outside a model opens, but the page and Problems say it has lost its model.
• The three New Model examples carry decisions. Model page: the registry files panel is titled Registries.

0.7.1 — 2026-10-19

• No generated cards. The cards 0.7.0 generated under model diagrams from registry descriptions are gone; they repeated the Elements panel. The description now shows as the tooltip of the element's row in the Elements panel. Hand-written cards: are unchanged.
• Model page, Registry panel: lists the registry files of the model, one collapsible header per file with its element count and an Open button that opens the registry view; expand a file to see its elements as cards. Before, all elements of all files were shown in one grid.

0.7.0 — 2026-10-19

• Models: a folder with a main.archify at its top is a model, a set of diagrams that belong together. Opening main.archify shows the model page: name and description, the overview diagram if the file has one, the diagrams grouped by folder (click to open), and the registry with where each element is used.
• Registry: *.archify-registry files define shared elements once; diagrams draw them with ref: <id> plus position, and may override label, sublabel and tag. Hover, go-to-definition and completion on ref; unknown names, forbidden overrides, duplicate ids and broken registries in Problems. Registry edits re-render open diagrams.
• Registry view: .archify-registry files open as their elements (cards). Clicking an element opens a dialog with its description, the registry line that defines it and the diagrams that use it; the same dialog opens from the registry cards on the model page. Show Source opens the YAML beside the view.
• Elements and Connectors: the node index under a diagram is titled Elements; a new Connectors panel lists every connection (from → to, label), highlights it on hover and keeps it highlighted on click.
• Model page panels: Diagrams and Registry are collapsible panels; inside Diagrams every folder has its own collapsible header above its diagram cards. Open or closed is remembered.
• Cards: a model diagram without cards of its own gets Archify cards from the registry descriptions of the elements it draws; the model page shows the registry as the same cards, each with the diagrams it is used in.
• Links: diagram: on a registry element or a component points at the diagram that explains it; double-click the node (2D view) to open it.
• New Model…: right-click a folder and choose Archify | New Model… (also in File → New File… and the Command Palette) to start from one of three complete C4 examples: C4 - Standard Web App, C4 - E-Shop, C4 - Event-Based Integration. Each creates a model folder with main.archify, a registry and context, container and component diagrams, named after the folder you choose, and opens the model page.
• New commands Archify | Open Model (editor title, Command Palette and the Explorer menu of .archify and .archify-registry files); New Diagram… → Model (main.archify) template for an empty model; editor schema for registries and the new keys; example model in examples/online-shop.

0.6.2 — 2026-10-19

• Sponsor button: the extension now declares a sponsor link, so VS Code's Extensions view and the Marketplace page show Sponsor (Buy Me a Coffee). The README has a Support section with the same link.

0.6.1 — 2026-10-12

• The 3D menu is replaced by a 2D | 3D switch next to Export: the filled half is the view you are in, one click flips it.
• The 3D-only controls moved to the bottom-right dock next to PATH and LENS: STACK (levels by kind, on or off), TOP (from above), and the zoom stepper's middle button reads RESET in 3D instead of a 2D zoom level.
• Nothing is greyed out any more, and no menu stays open over the diagram after a choice.

0.6.0 — 2026-10-11

• 3D view: a 3D ▾ menu in the diagram toolbar, styled like Archify's own menus, switches any diagram to 3D. Nodes become raised blocks topped with the node as Archify draws it, relationships become lit pipes along Archify's routes, and the canvas, frames, lanes and legend form the floor. Works for all five diagram kinds, in every theme and style.
• The menu also holds Levels (Flat, or Stacked by kind) and Camera (Reset view, From above).
• Animation follows 2D: the 3D view mirrors Archify's own animations live: the trace when the diagram opens (replayed when 3D is chosen), node pulses, the hover trace, and the Semantic Passport, Path and Lens flows. Live off and reduced motion keep it still.
• In 3D, clicking a block focuses it as in 2D (Semantic Passport, fading); hover shows the one-hop trace; trackpad scrolling pans, pinch and the mouse wheel zoom; the zoom buttons and +/-/0 move the camera; Export → 3D view saves a PNG.
• Performance: the 3D view draws only when something moves (no GPU use while idle), uses lighter textures and pixel density, and the hidden 2D diagram is no longer painted. Hover and animations never rebuild textures.
• New setting archify.defaultView (2d or 3d). Each open diagram remembers its view, camera and levels.
• The source code is reorganised by job (commands/, views/, webview/, archify/, sources/, language/, util/); no change in behaviour.

0.5.2 — 2026-10-10

• Right-click menus: the Archify commands (Archify | New Diagram…, Archify | Open Preview, Archify | Render to HTML File…, Archify | Open in HTML Viewer) now sit in their own section at the very bottom of the Explorer and editor-tab menus, instead of between New File, New Folder and the other built-in entries.
• All commands are named "Archify | …", the same in right-click menus, the editor title bar and the Command Palette: Archify | New Diagram… (was New Diagram Archify…), Archify | Open Preview, Archify | Open Preview to the Side, Archify | Render to HTML File…, Archify | Open in HTML Viewer, Archify | Open in Browser, Archify | Refresh Preview, Archify | Show Source.

0.5.1 — 2026-10-07

• Clearer descriptions: the Marketplace description, README and messages now say plainly that diagrams are .archify files in YAML. Archify's own JSON files (*.architecture.json, …) and rendered HTML are described as also supported, in their own section.
• The rendered-HTML editor is now called Archify HTML Viewer (was Archify Diagram Viewer, the same name as the extension), and its command Open in Archify HTML Viewer.
• Messages: "open a .archify diagram first"; an empty or broken .archify file asks for valid YAML, not JSON.

0.5.0 — 2026-10-04

• Brand completion: after brand: in .archify files and Archify JSON sources, the editor suggests the 107 built-in brand IDs with their product names. Aliases and product names match too (kafka → apache-kafka, postgres → postgresql).
• Unknown brands are underlined on their own line. Archify reports these without a location, so they used to appear at the top of the file.

0.4.1 — 2026-10-04

• The new-diagram command is now titled New Diagram Archify… everywhere, including the Explorer folder menu, where it read New Diagram….

0.4.0 — 2026-10-04

• New Diagram… (Explorer folder menu, File → New File…, Command Palette): pick Architecture, Workflow, Sequence, Data Flow, Lifecycle or Everyday Plan, enter a name, and a small valid .archify (YAML) file is created from a template and opened as a diagram. Title and output file follow the name.

0.3.0 — 2026-09-30

• .archify files are YAML. They are parsed as YAML and handed to the renderer as JSON. Older JSON .archify files still open, since JSON is valid YAML.
• Clicking a .archify file opens the diagram: the new Archify Diagram editor is the default for *.archify. Show Source opens the YAML beside it, and the diagram follows your edits.
• YAML syntax errors are reported in the Problems panel. Archify validation problems point at the matching YAML line.
• Schema completion for .archify works through the YAML extension (redhat.vscode-yaml), via yamlValidation.

0.2.0 — 2026-09-30

• .archify files: Archify JSON diagram sources with their own extension. They open as JSON, preview with the same button and keys, report problems, and get completion from the schema of their diagram_type.
• Render to HTML and Open in Browser name the output after the diagram (web.archify → web.html).
• examples/hello.archify starter diagram.
• Marketplace icon and README screenshot.

0.1.0 — 2026-09-30

• Live preview for Archify JSON sources (architecture, workflow, sequence, dataflow, lifecycle), re-rendered as you type.
• Read-only Archify viewer for rendered .html files, reloaded when the file changes.
• Problems panel diagnostics from archify validate, mapped to the JSON location.
• JSON schema completion and hover for *.architecture.json, *.workflow.json, *.sequence.json, *.dataflow.json and *.lifecycle.json.
• Source-evidence links open the referenced file and lines in the editor.
• Viewer exports (PNG, SVG, share card, …) save through a VS Code save dialog.
• Render to HTML file and open in browser commands.
• Bundles the Archify 3.0.1 renderer; runs on VS Code's own Node runtime.