FluxFlow.Components.Timers.Composition 1.5.0

FluxFlow.Components.Timers.Composition

Optional FluxFlow.Composition registration helpers for standalone timer nodes from FluxFlow.Components.Timers.

This package does not scan assemblies, resolve CLR types from strings, add hot reload behavior, or convert schedule time zone ids. Hosts register closed generic transform node types explicitly and provide optional keyed TimeProvider services.

Registration

services.AddKeyedSingleton<TimeProvider>("fixed", timeProvider);

services
    .AddFluxFlowComposition(configuration)
    .RegisterNodes(registry => registry
        .RegisterTimerInterval()
        .RegisterTimerSchedule()
        .RegisterTimerDelay<OrderMessage>()
        .RegisterTimerThrottle<OrderMessage>()
        .RegisterTimerDebounce<OrderMessage>());

Use custom node type names when a host needs more than one input shape:

registry
    .RegisterTimerDelay<OrderMessage>("timer.delay.order")
    .RegisterTimerDebounce<HttpMessage>("timer.debounce.http");

Node Types

The composition runtime starts interval and schedule sources through the normal IFlowSource lifecycle. Transform nodes preserve the input correlation id when they re-emit the original payload.

Design Metadata

TimersComponentDesignMetadataProvider exposes neutral Designer metadata for the five timer composition nodes. Hosts can add it to a ComponentDesignMetadataCatalog to populate palettes, editors, validation views, or generated documentation.

The provider describes node options, ports, option grouping/editor hints, and a resource picker hint for the optional clock resource. The clock remains a host-owned composition resource with a clock key-pattern hint and is not exposed as an editable node option. Schedule metadata covers cron/default UTC composition behavior. It declares timeZone as an omitted editable option because TimerScheduleSettings.TimeZone requires typed configuration and this package still does not add time-zone id conversion.

Configuration

{
  "FluxFlow": {
    "Composition": {
      "workflows": {
        "main": {
          "nodes": {
            "poll": {
              "type": "timer.interval",
              "resources": {
                "clock": "fixed"
              },
              "configuration": {
                "name": "poll",
                "interval": "00:00:01",
                "emitImmediately": true,
                "maxTicks": 10,
                "boundedCapacity": 128
              }
            },
            "rate-limit": {
              "type": "timer.throttle",
              "configuration": {
                "name": "rate-limit",
                "interval": "00:00:00.100",
                "emitFirstImmediately": true,
                "boundedCapacity": 128
              }
            }
          },
          "links": []
        }
      }
    }
  }
}

Timer settings bind to the existing settings records. timer.schedule uses the existing TimerScheduleSettings shape; no additional time zone id conversion is added by this adapter. Invalid timer settings, such as non-positive intervals, negative delays, or non-positive boundedCapacity, fail during composition build and surface as factory diagnostics when build failures are configured as diagnostics.