@joint/react
    Preparing search index...

    Interface GraphProps

    interface GraphProps {
        cellModel?: typeof Cell;
        cellNamespace?: unknown;
        children?: ReactNode;
        graph?: Graph<Attributes, ModelSetOptions>;
        initialElements?: (GraphElement | Element<Attributes, ModelSetOptions>)[];
        initialLinks?: (GraphLink<string> | Link<Attributes, ModelSetOptions>)[];
        store?: Store;
    }

    Hierarchy (View Summary)

    Index

    Properties

    cellModel? cellNamespace? children? graph? initialElements? initialLinks? store?

    Properties

    cellModel?: typeof Cell

    Custom cell model to use. It's loaded just once, so it cannot be used as React state.

    https://docs.jointjs.com/api/dia/Cell

    cellNamespace?: unknown

    Namespace for cell models. It's loaded just once, so it cannot be used as React state. When added new shape, it will not remove existing ones, it will just add new ones. So { ...shapes, ReactElement } elements are still available.

    { ...shapes, ReactElement }

    https://docs.jointjs.com/api/shapes

    children?: ReactNode

    Children to render.

    graph?: Graph<Attributes, ModelSetOptions>

    Graph instance to use. If not provided, a new graph instance will be created.

    https://docs.jointjs.com/api/dia/Graph

    new dia.Graph({}, { cellNamespace: shapes })
    initialElements?: (GraphElement | Element<Attributes, ModelSetOptions>)[]

    Initial elements to be added to graph It's loaded just once, so it cannot be used as React state.

    initialLinks?: (GraphLink<string> | Link<Attributes, ModelSetOptions>)[]

    Initial links to be added to graph It's loaded just once, so it cannot be used as React state.

    store?: Store

    Store is build around graph, it handles react updates and states, it can be created separately and passed to the provider via createStore function.

    createStore

    Settings

    Member Visibility

    On This Page

    Properties