HubRouting enum

Defines how a Cell.hub decides which spoke (child cell) should receive an incoming signal.

The HubRouting strategy acts like a traffic controller, reading the "address" (the Pulse.type) on a signal to determine its destination.

When to use

• Think of a Cell.hub as a post office and HubRouting as the sorting logic. Depending on the mode, the hub can look for an exact name, a zip code (prefix), or broadcast to everyone.
• exact: When you have one-to-one mapping (e.g., 'command.save' goes only to the 'save' spoke).
• prefix: When you have hierarchical categories (e.g., all signals starting with 'auth.' go to the Auth module).
• pattern: When you need flexible wildcard matching (e.g., 'user.*.success').
• multicast: When multiple parts of your app need to react to the same signal simultaneously.

How it works

When a pulse is HubHandle.emitted to the hub, the hub looks at the Pulse.type. It then loops through its registered spokes and applies the chosen routing strategy to find a match.

Non‑obvious

• Priority: If multiple spokes match in a non-multicast mode, the one with the highest priority wins.
• Longest-Prefix: In prefix mode, the hub automatically selects the most specific match (e.g., 'user.login.success' will prefer a spoke named 'user.login' over a spoke named 'user').

Example

// Setting up a prefix-based router
final router = Cell.hub(
  routing: HubRouting.prefix,
  spokes: {
    'auth': authHandler,
    'auth.login': loginHandler, // This will be preferred for 'auth.login'
  },
);