FluxFlow.Components.FileSystem.Composition 1.5.0

FluxFlow.Components.FileSystem.Composition

Optional FluxFlow.Composition registration helpers for the standalone file system nodes from FluxFlow.Components.FileSystem.

This package does not scan assemblies, resolve CLR types from strings, create file-system abstraction resources, or own path policy. Hosts register file system factories explicitly and may provide an optional keyed TimeProvider.

Registration

services
    .AddFluxFlowComposition(configuration)
    .RegisterNodes(registry => registry
        .RegisterFileRead()
        .RegisterFileWrite()
        .RegisterDirectoryEnumerate()
        .RegisterFileWatch());

Node Types

The factories expose Events and Errors. clock is an optional keyed TimeProvider resource for deterministic result, event, and error timestamps. Path safety is still configured through the existing node options such as baseDirectory and allowAbsolutePaths.

Configuration

{
  "FluxFlow": {
    "Composition": {
      "workflows": {
        "main": {
          "nodes": {
            "read": {
              "type": "file.read",
              "resources": {
                "clock": "fixed"
              },
              "configuration": {
                "baseDirectory": "data",
                "allowAbsolutePaths": false,
                "defaultEncoding": "utf-8",
                "maxBytes": 16777216,
                "boundedCapacity": 128
              }
            },
            "enumerate": {
              "type": "directory.enumerate",
              "configuration": {
                "directory": "inbox",
                "filter": "*.json",
                "includeFiles": true,
                "includeDirectories": false,
                "baseDirectory": "data"
              }
            }
          },
          "links": []
        }
      }
    }
  }
}

The adapter binds the existing FileSystem option records from composition configuration. CompositionRuntime.StartAsync() starts directory.enumerate and file.watch; normal runtime stop/dispose stops file.watch. Invalid option values fail during composition build through the node factory. If build failures are configured as diagnostics, the runtime is not created and the host receives a FactoryFailed diagnostic with the relevant option name.

Design Metadata

FileSystemComponentDesignMetadataProvider exposes neutral Designer metadata for the four file-system composition nodes. The metadata describes fixed request/result ports, source outputs, the existing FileSystem option records, option section/importance/editor hints, and optional host-owned clock resource picker hints for hosts that build palettes, editors, validators, or documentation views.

Path safety remains runtime configuration through baseDirectory and allowAbsolutePaths. The optional clock resource remains host-owned and is not represented as an editable node option. The metadata is authored through the shared validated Designer metadata builder while preserving the same public metadata contracts consumed by hosts.