FluxFlow.Components.Validation
1.0.0
dotnet add package FluxFlow.Components.Validation --version 1.0.0
NuGet\Install-Package FluxFlow.Components.Validation -Version 1.0.0
<PackageReference Include="FluxFlow.Components.Validation" Version="1.0.0" />
<PackageVersion Include="FluxFlow.Components.Validation" Version="1.0.0" />
<PackageReference Include="FluxFlow.Components.Validation" />
paket add FluxFlow.Components.Validation --version 1.0.0
#r "nuget: FluxFlow.Components.Validation, 1.0.0"
#:package FluxFlow.Components.Validation@1.0.0
#addin nuget:?package=FluxFlow.Components.Validation&version=1.0.0
#tool nuget:?package=FluxFlow.Components.Validation&version=1.0.0
FluxFlow.Components.Validation
Reusable validation components for FluxFlow.
Nodes
| Node type | Shape | Purpose |
|---|---|---|
json.schema-validator |
Input → Result, Valid, Invalid |
Validates a selected value with a JSON schema. |
The package does not know application payload types. Hosts register type aliases and optional value selectors during registration.
var registry = new RuntimeNodeFactoryRegistry()
.RegisterValidationComponents(options => options
.RegisterType<AppMessage>("app.message")
.UseValueSelector<AppMessage>("payload", (message, context) => message.PayloadText));
Basic configuration:
{
"type": "json.schema-validator",
"inputType": "object",
"schemaId": "orders",
"schema": {
"type": "object",
"required": [ "id" ],
"properties": {
"id": { "type": "string" }
}
},
"valueSelector": "input",
"boundedCapacity": 128
}
Use schemaPath instead of schema when the host wants the package to read a
schema file. payloadSelector is accepted as an alias for valueSelector.
Invalid data emits a result and routes the original input to Invalid; it is
not reported as a processing error. Schema loading, value selection, value
conversion, and evaluation failures emit FlowError and the node continues
processing later messages where possible.
Runtime Timing
Validation results use the package clock for Timestamp. Existing callers use
the default system clock. Hosts and tests can provide a deterministic clock
through registration:
registry.RegisterValidationComponents(options => options
.UseClock(validationClock));
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.Engine (>= 1.0.0)
- JsonSchema.Net (>= 9.2.1)
-
net8.0
- FluxFlow.Engine (>= 1.0.0)
- JsonSchema.Net (>= 9.2.1)
- System.Threading.Tasks.Dataflow (>= 9.0.4)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 1.0.0 | 0 | 6/4/2026 |
| 0.2.0-alpha.1 | 73 | 6/2/2026 |
| 0.1.1-alpha.1 | 45 | 6/2/2026 |
| 0.1.0-alpha.1 | 106 | 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.