Changeset View
Changeset View
Standalone View
Standalone View
src/docs/contributor/using_edges.diviner
@title Using Edges | @title Using Edges | ||||
@group developer | @group developer | ||||
Guide to the Edges infrastructure. | Guide to the Edges infrastructure. | ||||
= Overview = | = Overview = | ||||
Edges are a generic way of storing a relationship between two objects (like a | Edges are a generic way of storing a relationship between two objects (like a | ||||
Task and its attached files). If you are familiar with the Facebook associations | Task and its attached files). | ||||
framework, Phabricator Edges are substantially similar. | |||||
An edge is defined by a source PHID (the edge origin), a destination PHID | An edge is defined by a source PHID (the edge origin), a destination PHID | ||||
(the edge destination) and an edge type (which describes the relationship, | (the edge destination) and an edge type (which describes the relationship, | ||||
like "is subscribed to" or "has attached file"). | like "is subscribed to" or "has attached file"). | ||||
Every edge is directional, and stored alongside the source object. Some edges | Every edge is directional, and stored alongside the source object. Some edges | ||||
are configured to automatically write an inverse edge, effectively building | are configured to automatically write an inverse edge, effectively building | ||||
a bidirectional relationship. The strength of storing relationships like this | a bidirectional relationship. The strength of storing relationships like this | ||||
Show All 13 Lines |
Content licensed under Creative Commons Attribution-ShareAlike 4.0 (CC-BY-SA) unless otherwise noted; code licensed under Apache 2.0 or other open source licenses. · CC BY-SA 4.0 · Apache 2.0