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 lifecycle;
11mod reconnect;
12mod target;
13
14pub use activation::{ConnectionDragActivationInput, connection_drag_threshold_met};
15pub use connect::{
16    CONNECT_EDGE_TRANSACTION_LABEL, ConnectEdgeError, ConnectEdgeRequest, connect_edge_transaction,
17    connect_edge_transaction_with_edge_id,
18};
19pub use handles::{
20    ClosestConnectionHandle, ClosestConnectionHandleInput, ConnectionHandleCandidate,
21    ConnectionHandleRef, ConnectionHandleValidity, closest_connection_handle,
22    connection_handle_validity,
23};
24pub use indicator::{
25    ConnectionHandleIndicator, ConnectionHandleIndicatorInput, resolve_connection_handle_indicator,
26};
27pub use lifecycle::{
28    ConnectionEndIntent, ConnectionLifecycleResult, ConnectionLifecycleState, new_connection_start,
29    resolve_connection_lifecycle,
30};
31pub use reconnect::{
32    RECONNECT_EDGE_TRANSACTION_LABEL, ReconnectEdgeError, ReconnectEdgeRequest,
33    reconnect_edge_transaction,
34};
35pub use target::{
36    ConnectionHandleConnection, ConnectionTargetCandidate, ConnectionTargetFromHandlesInput,
37    ConnectionTargetHandle, ConnectionTargetInput, ResolvedConnectionTarget,
38    resolve_connection_target, resolve_connection_target_from_handles,
39};
jellyflow_runtime/runtime/connection/mod.rs

jellyflow_runtime/runtime/connection/
mod.rs
