FluxFlow.Components.Http.Composition 1.4.0

FluxFlow.Components.Http.Composition

Optional FluxFlow.Composition registration helpers for the standalone HTTP node from FluxFlow.Components.Http.

This package does not create HttpClient instances, own base addresses, configure handlers, or choose retry/auth/security policy. The host or adapter DI registers keyed HttpClient services. Composition definitions reference those keys as resources.

Registration

services.AddKeyedSingleton<HttpClient>("primary", httpClient);

services
    .AddFluxFlowComposition(configuration)
    .RegisterNodes(registry => registry.RegisterHttpNodes());

Node Types

clock is an optional keyed TimeProvider resource for deterministic timestamps and request timeout tests.

Configuration

{
  "FluxFlow": {
    "Composition": {
      "workflows": {
        "main": {
          "nodes": {
            "api": {
              "type": "http.client",
              "resources": {
                "client": "primary"
              },
              "configuration": {
                "boundedCapacity": 32,
                "maxResponseBodyBytes": 1048576,
                "treatNonSuccessStatusAsError": false,
                "maxDegreeOfParallelism": 1,
                "defaultTimeoutMilliseconds": 30000
              }
            }
          },
          "links": []
        }
      }
    }
  }
}

The composition package binds only HttpClientNodeOptions. HTTP method, URL, headers, body, content type, and per-message timeout still come from HttpRequestInput messages at runtime. Transport policy stays on the injected HttpClient. Invalid numeric HttpClientNodeOptions values fail during composition build and surface as factory diagnostics when build failures are configured as diagnostics.

Design Metadata

HttpComponentDesignMetadataProvider exposes neutral Designer metadata for http.client so hosts can build palettes, editors, validation hints, or documentation without copying package descriptors. The metadata describes the existing HttpClientNodeOptions configuration surface, option grouping/editor hints, the required client resource picker hint, the optional clock resource picker hint, and fixed request/result ports. The metadata is authored through the shared validated Designer metadata builder while preserving the same public metadata contracts consumed by hosts. Resource metadata is descriptive only, so HttpClient instances and optional keyed TimeProvider clocks remain host-owned resources with key-pattern hints and are not modeled as editable node options.