Skip to main content

NodeOrPortMapping

Base view mapping for nodes and ports (and groups, since they extend nodes)

Extends

Extended by

Type Parameters

E

E

N

N

EVT

EVT

Properties

allowLoopback?

optional allowLoopback: boolean

Whether or not to allow edges from this vertex back to itself. Defaults to true. This flag will not prevent an edge from a port back to the node/group to which it belongs - for that, see allowVertexLoopback.

Overrides

VertexMapping.allowLoopback


allowVertexLoopback?

optional allowVertexLoopback: boolean

Whether or not to allow edges from a port back to the vertex it belongs to. Defaults to true.

Overrides

VertexMapping.allowVertexLoopback


anchorPositionFinder?

optional anchorPositionFinder: AnchorPositionFinder<any>

Optional function to call on connection drop, to determine the location for the target anchor for the new connection. Returning null from this indicates no preference, and VisuallyJs will use its own computed value.

Inherited from

VertexMapping.anchorPositionFinder


anchorPositions?

optional anchorPositions: ObjectAnchorSpec[]

Optional array of anchor positions to use.

Inherited from

VertexMapping.anchorPositions


edgeType?

optional edgeType: string

Type to assign to edges connected to this vertex as a source.

Inherited from

VertexMapping.edgeType


events?

optional events: EVT

Optional map of event bindings.

Inherited from

VertexMapping.events


maxConnections?

optional maxConnections: number

Maximum number of connections this vertex supports. Default is 1. A value of -1 means no limit.

Inherited from

VertexMapping.maxConnections


mergeStrategy?

optional mergeStrategy: string

When merging a type description into its parent(s), values in the child for connector, anchor and anchors will always overwrite any such values in the parent. But other values, such as overlays, will be merged with their parent's entry for that key. You can force a child's type to override every corresponding value in its parent by setting mergeStrategy:'override'.

Inherited from

VertexMapping.mergeStrategy


parameters?

optional parameters: Record<string, any>

A map of parameters that the template engine will merge with the backing data when rendering the vertex.


parent?

optional parent: string | string[]

Optional ID of one or more edge definitions to include in this definition. The child definition is merged on top of the parent definition(s). Circular references are not allowed and will throw an error.

Inherited from

VertexMapping.parent


template?

optional template: string

Template to use for a vertex of this type. This is only for 'vanilla' VisuallyJs: if you are using an integration such as React/Angular/Vue/Svelte, you will not need to provide this. If you provide this and also templateId, this will take precedence.


templateId?

optional templateId: string

ID of the template to use for a vertex of this type. This is only for 'vanilla' VisuallyJs: if you are using an integration such as React/Angular/Vue, you will not need to provide this. This parameter is distinct from template in that when you provide templateId you are expecting VisuallyJs to resolve the template for you, either from a templates block in a render call, or by looking for a script element in the DOM with the appropriate ID. If you provide this and also template, template will take precedence.


templateIdResolver()?

optional templateIdResolver: (data, ui, model, object) => string

A function that can resolve the ID of the template to use for the given vertex. This is an advanced configuration that is not often needed, and is only for 'vanilla' VisuallyJs. This function will take precedence over both template and templateId.

Parameters

data

ObjectData

ui

UICore<E>

model

VisuallyJsModel

object

Vertex

Returns

string