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
The render layer accepts a simple JSON format, making it easy to visualize **any** directed graph—not just package dependencies. You can hand-craft graphs for component diagrams, callgraphs, or pipe output from other tools.
107
+
108
+
### Minimal Example
109
+
110
+
```json
111
+
{
112
+
"nodes": [
113
+
{ "id": "app" },
114
+
{ "id": "lib-a" },
115
+
{ "id": "lib-b" }
116
+
],
117
+
"edges": [
118
+
{ "from": "app", "to": "lib-a" },
119
+
{ "from": "lib-a", "to": "lib-b" }
120
+
]
121
+
}
122
+
```
123
+
124
+
### Required Fields
125
+
126
+
| Field | Type | Description |
127
+
|-------|------|-------------|
128
+
|`nodes[].id`| string | Unique node identifier (displayed as label) |
129
+
|`edges[].from`| string | Source node ID |
130
+
|`edges[].to`| string | Target node ID |
131
+
132
+
### Optional Fields
133
+
134
+
| Field | Type | Description |
135
+
|-------|------|-------------|
136
+
|`nodes[].row`| int | Pre-assigned layer (computed automatically if omitted) |
137
+
|`nodes[].kind`| string | Internal use: `"subdivider"` or `"auxiliary"`|
138
+
|`nodes[].meta`| object | Freeform metadata for display features |
139
+
140
+
### Recognized `meta` Keys
141
+
142
+
These keys are read by specific render flags. All are optional—missing keys simply disable the corresponding feature.
0 commit comments