Skip to content
Source on GitHubVisitors

Dependency graph

Draw named things and what depends on what, freely placed and connected.

Diagram · origin tag generic/dependencies · Business process & workflow notation

Availability

Availability per host
HostStateHow to get it
StandaloneAvailableInstall from v0.1.3826-alpha
DesktopNot yet releasedNot yet released
IntelliJ PlatformNot plannedNot planned
Visual Studio CodeNot plannedNot planned
EclipseNot plannedNot planned
ThinkRailNot plannedNot planned
NotionNot plannedNot planned
ClaudeNot plannedNot planned

What it is for

Dependency graph (named nodes and directed depends-on edges, freely placed and freely connected; `.dgr` — ADP's own YAML schema and extension, on the `generic/timeline` model with every time-related aspect removed: authored placement, directed depends-on edges drawn with an arrowhead, one command per edit); `dependency-graph` (specification removed from the tree; in history before `d573ad87`)

Why a specialized view helps

Dependencies are about direction and order; a dedicated tool keeps every edge directed and readable, in ADP's own .dgr format.

File formats

ExtensionFormatReadsWrites
.dgr.dgrYesYes

Screenshots

The service graph with labelled edges. Nothing selected.

Standalone, at a8616b3

What is visible: The service graph with labelled edges. Nothing selected.

Why it matters: Each service and store is one node and each edge carries its own label, so what depends on what, and why, can be read from the picture rather than pieced together from configuration.

Licence: Apache-2.0

Background

  • Follows the generic/timeline precedent: no standards body owns "a box depends on a box", so ADP defines the schema and owns the extension outright, keeping the document diffable text. Specified as a duplicate of the timeline module with every time-related aspect removed

Focus areas

Sources