FluxFlow.Components.Control
1.0.0
See the version list below for details.
dotnet add package FluxFlow.Components.Control --version 1.0.0
NuGet\Install-Package FluxFlow.Components.Control -Version 1.0.0
<PackageReference Include="FluxFlow.Components.Control" Version="1.0.0" />
<PackageVersion Include="FluxFlow.Components.Control" Version="1.0.0" />
<PackageReference Include="FluxFlow.Components.Control" />
paket add FluxFlow.Components.Control --version 1.0.0
#r "nuget: FluxFlow.Components.Control, 1.0.0"
#:package FluxFlow.Components.Control@1.0.0
#addin nuget:?package=FluxFlow.Components.Control&version=1.0.0
#tool nuget:?package=FluxFlow.Components.Control&version=1.0.0
FluxFlow.Components.Control
Reusable expression-driven control components for FluxFlow.
Nodes
| Node type | Shape | Purpose |
|---|---|---|
flow.filter |
Input → Output |
Emits only input values that match an expression. |
flow.when |
Input → WhenTrue / WhenFalse |
Routes each input value by expression result. |
The package does not choose an expression language. Applications provide one or
more IFlowExpressionEngine implementations during registration.
var registry = new RuntimeNodeFactoryRegistry()
.RegisterControlComponents(options => options
.UseExpressionEngine(appExpressionEngine)
.RegisterType<AppMessage>("app.message")
.UseContextFactory(new AppMessageContextFactory()));
Basic configuration:
{
"type": "flow.when",
"inputType": "object",
"engine": "my-engine",
"expressionId": "route-v1",
"expressionName": "route-important",
"expression": "..."
}
inputType defaults to object. Register type aliases when a control node
needs to connect to typed ports. Omit engine to use the default expression
engine configured by the host.
Expression evaluation failures emit FlowError and the node continues
processing later messages. Nodes emit diagnostics with input type, engine,
expression id, expression name, and route metadata where available.
Composition Guidance
Use this package as one part of a host-composed graph. See Component Composition for recommended host boundaries, package boundaries, and extraction timing.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- FluxFlow.Components.Expressions (>= 1.0.0)
- FluxFlow.Engine (>= 1.0.0)
-
net8.0
- FluxFlow.Components.Expressions (>= 1.0.0)
- FluxFlow.Engine (>= 1.0.0)
- System.Threading.Tasks.Dataflow (>= 9.0.4)
NuGet packages (1)
Showing the top 1 NuGet packages that depend on FluxFlow.Components.Control:
| Package | Downloads |
|---|---|
|
FluxFlow.Components.Control.Composition
Optional FluxFlow.Composition registration helpers for standalone control nodes over host-owned keyed expression resources. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 3.0.2 | 142 | 7/3/2026 |
| 3.0.1 | 166 | 7/2/2026 |
| 3.0.0 | 117 | 6/19/2026 |
| 2.0.0 | 139 | 6/18/2026 |
| 1.2.1 | 120 | 6/15/2026 |
| 1.2.0 | 417 | 6/12/2026 |
| 1.1.0 | 115 | 6/5/2026 |
| 1.0.0 | 123 | 6/4/2026 |
| 0.3.0-alpha.1 | 248 | 6/2/2026 |
| 0.2.1-alpha.1 | 74 | 6/2/2026 |
| 0.2.0-alpha.1 | 94 | 6/1/2026 |
| 0.1.0-alpha.1 | 108 | 6/1/2026 |
Stable 1.0.0 component package boundary for FluxFlow.Engine 1.0.0 with package-owned contracts, neutral diagnostics, and release readiness documentation.