jellyflow_runtime/runtime/connection/
mod.rs

1//! Renderer-neutral connection gesture helpers.
2//!
3//! Adapters own pointer capture and platform hit testing. The runtime owns deterministic
4//! connection activation and handle proximity policy that should feel like XyFlow across renderers.
5
6mod activation;
7mod connect;
8mod handles;
9mod indicator;
10mod reconnect;
11mod target;
12
13pub use activation::{ConnectionDragActivationInput, connection_drag_threshold_met};
14pub use connect::{
15    CONNECT_EDGE_TRANSACTION_LABEL, ConnectEdgeError, ConnectEdgeRequest, connect_edge_transaction,
16    connect_edge_transaction_with_edge_id,
17};
18pub use handles::{
19    ClosestConnectionHandle, ClosestConnectionHandleInput, ConnectionHandleCandidate,
20    ConnectionHandleRef, ConnectionHandleValidity, closest_connection_handle,
21    connection_handle_validity,
22};
23pub use indicator::{
24    ConnectionHandleIndicator, ConnectionHandleIndicatorInput, resolve_connection_handle_indicator,
25};
26pub use reconnect::{
27    RECONNECT_EDGE_TRANSACTION_LABEL, ReconnectEdgeError, ReconnectEdgeRequest,
28    reconnect_edge_transaction,
29};
30pub use target::{
31    ConnectionHandleConnection, ConnectionTargetCandidate, ConnectionTargetFromHandlesInput,
32    ConnectionTargetHandle, ConnectionTargetInput, ResolvedConnectionTarget,
33    resolve_connection_target, resolve_connection_target_from_handles,
34};
jellyflow_runtime/runtime/connection/mod.rs

jellyflow_runtime/runtime/connection/
mod.rs
