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
Copy file name to clipboardExpand all lines: site/app/docs/_configDocs/Edges.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,8 @@ title: Edges
7
7
8
8
<p></p>
9
9
10
+
By default, edges do not require an ID, only a source and target. If, however, there are multiple edges that share the same source and target, a unique ID will be required.
Copy file name to clipboardExpand all lines: site/app/docs/_documentation/GraphJSON.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ GraphJSON is a JSON object that contains two objects, **nodes** and **edges**:
21
21
The **nodes** and **edges** objects are arrays of the individual nodes and edges that will be represented in the Graph visualization.
22
22
23
23
## Nodes and Edges
24
-
The only requirement for node objects is that they receive an **id** key that is unique (in the scope of the GraphJSON). The only requirement for edge objects is that they receive a **source** and **target** key that correspond to the source and target nodes.
24
+
The only requirement for node objects is that they receive an **id** key that is unique (in the scope of the GraphJSON). The only requirement for edge objects is that they receive a **source** and **target** key that correspond to the source and target nodes. If there are multiple edges with identical source and targets, those edges MUST have a unique id.
25
25
26
26
## Features
27
27
Alchemy.js has a number of features that rely on the underlying data. Most of the below features are supported by the example GraphJSON that follows.
0 commit comments