Innovabit.DotNet.Interceptors.Configuration 2.0.117

Innovabit.DotNet.Interceptors.Configuration

Drives the interceptor pipeline from IConfiguration. Switch interceptors off, move them in the pipeline and set each feature's defaults from appsettings.json — per environment, without recompiling.

Usage

builder.Services
    .AddInterceptors()
    .AddLogging()
    .AddRetry()
    .AddTracing()
    .BindConfiguration(builder.Configuration.GetSection("Interceptors"))
    .BindDefaults<LogDefaults>(builder.Configuration.GetSection("Interceptors:Log"));

{
  "Interceptors": {
    "Disabled": [ "TraceInterceptor" ],
    "Order": { "CacheInterceptor": 150 },
    "Log": { "IncludeInput": false, "IncludeOutput": false }
  }
}

Disabled takes interceptors out of every proxy while leaving the registrations that put them there alone. Order is the same scale as InterceptorOrders — lower runs further from the method — and does the same job as SetOrder<T>(…) without needing the type.

Names are type names, short (TraceInterceptor) or full (Innovabit.DotNet.Interceptors.Telemetry.TraceInterceptor), case-insensitively. A name that matches nothing registered is ignored, so one shared file can cover several applications that register different interceptors.

Run services.LogInterceptorPipeline(Console.WriteLine) after building the host to see what the file actually did: the report lists disabled interceptors as (disabled) and shows each method's interceptors at their effective order.

What to know

Code wins over the file for ordering. Register<T>(order) and SetOrder<T>(order) are keyed by type, Order entries by name, and a type override is checked first. Both Disabled and Order replace what an earlier bind left, so deleting an entry and reloading puts the default back rather than leaving the last value applied.

Reloading reaches services resolved afterwards. A proxy captures its interceptors when it is built, so a change during a reload applies to scoped and transient services from the next resolution on — the next request, typically — and never to a singleton that has already been created. Pass reloadOnChange: false if you would rather the pipeline was fixed at start-up.

A bad edit at run time does not take the process down. An order that is not a number throws at start-up, where it should. The same mistake made while the application is running leaves the last good values in place instead of throwing from the file-watcher thread.

BindDefaults<T> binds onto the instance the interceptors resolve, so it also reaches ones already holding a reference to it, and it works whether it runs before or after the feature's Add*. Properties the binder cannot build from a string — the Type-valued ones such as LogDefaults.UseFormatter — have to stay in code.

License

MIT