Intropy.Framework.Blocks 2.0.0-beta.1

Intropy.Framework.Blocks

Reusable pipeline blocks for the Intropy.Framework pipeline framework.

Each block is a ready-made pipeline shape for a common integration pattern:

Each block exposes a fluent builder and wires up deserialization, validation, transformation, idempotency, and finalizers in the right order.

Configuring steps: DI vs. instance

The builders follow one rule for how steps are supplied:

• External edges are DI-resolvable. Idempotency (WithIdempotency), business incidents (WithBusinessIncidents), and the send/publish edge (WithDaprTopicPublisher, WithDaprServiceInvoker, WithSenderFromServices) resolve their infrastructure clients from the service provider. This keeps the "which external system?" decision in service registration, and lets tests substitute a fake by replacing the registration.
• Component logic is instance-passed. Deserializers, validators, transformers, serializers, and extract steps are component-owned and passed directly to the builder (WithDeserializer, WithTransformer, ...).

For the send edge, WithSenderFromServices() resolves the sender registered against its abstract base type — SendStep<TCtx> for the Extractor, SendStep<TOutput, TCtx> for the Loader:

// Registration (composition root)
services.AddSingleton<SendStep<OrderContext>>(sp =>
    new DaprTopicPublisher<OrderContext>(
        sp.GetRequiredService<DaprClient>(), "pubsub", "orders",
        new Uri("urn:company:system:erp"), "com.company.order.extracted"));

// Builder
var extractor = ExtractorBuilder<Order, OrderDto, OrderContext>.Create("orders", sp)
    // ... other steps ...
    .WithSenderFromServices()
    .Build();

The sender is resolved once, when WithSenderFromServices() is called — register it as a singleton (or transient), not scoped.

The CloudEvent envelope (Extractor)

CloudEventSerializeStep builds the envelope from component-supplied extractors — subject, time, and optionally type. The send steps (DaprTopicPublisher, DaprServiceInvoker) set source from configuration and apply their configured type as a fallback when the serializer did not set one.

The optional type extractor classifies the same payload into different event types, from the output and the pipeline context:

.WithSerializer(new CloudEventSerializeStep<Order, OrderContext>(
    subject: o => o.OrderId,
    time: o => o.ChangedAt,
    type: (o, _) => o.Status == 0 ? "io.intropy.orders.new" : "io.intropy.orders.cancelled"))

A configured type extractor that resolves to null, empty, or whitespace is a technical failure — consumers route on the type, so an event without one must never be published.

Install

dotnet add package Intropy.Framework.Blocks

License

MIT. See the repository for source and documentation.