feat: add IValidateOptions and ValidateOnStart for existing options classes

[samtrion]

Summary

Adds IValidateOptions<T> validators for the following options classes, each registered with the fail-fast pattern (AddOptions<T>().ValidateOnStart() + TryAddEnumerable(... IValidateOptions<T> ...)) in their respective existing Add*/Use* extension method:

• TimeoutRequestInterceptorOptions (AddRequestTimeout) — GlobalTimeout must be null or > TimeSpan.Zero.
• QueryCachingOptions (AddQueryCaching) — DefaultExpiry must be null or > TimeSpan.Zero.
• OutboxOptions (AddOutbox) — TableName must not be null/empty/whitespace.
• OutboxProcessorOptions (AddOutbox) — BatchSize > 0, PollingInterval > 0, MaxRetryCount >= 0, ProcessingTimeout > 0; when EnableExponentialBackoff is true, also BackoffMultiplier > 1.0, BaseRetryDelay > 0, MaxRetryDelay >= BaseRetryDelay.
• AzureServiceBusTransportOptions (UseAzureServiceBusTransport) — either ConnectionString or FullyQualifiedNamespace must be set.
• RabbitMqTransportOptions (UseRabbitMqTransport) — ExchangeName not empty; MaxChannelPoolSize >= 1 (the latter property was added by feat: RabbitMQ channel pooling in RabbitMqMessageTransport #241).
• DaprMessageTransportOptions (UseDaprTransport) — PubSubName not empty.

Each validator lives next to its options class, following the existing {OptionsClassName}Validator naming convention used by LoggingInterceptorOptionsValidator.

Deviations from the issue text

• LoggingInterceptorOptions is intentionally left untouched. It already has a validator (LoggingInterceptorOptionsValidator) but registration doesn't call .ValidateOnStart(). This class was explicitly called out as out of scope for this change.
• AzureServiceBusTransportOptions: the transport previously validated its options imperatively at ServiceBusClient-creation time via a private static ValidateOptions method, throwing InvalidOperationException. This is replaced by AzureServiceBusTransportOptionsValidator registered via the options pipeline. Behavior is equivalent (same required-field check, still throws at first options resolution / at host startup with ValidateOnStart), but the thrown exception type changes to Microsoft.Extensions.Options.OptionsValidationException. Existing tests were updated to expect the new exception type.
• SQLiteOutboxOptions does not exist as a distinct type in the current codebase — the SQLite provider (src/NetEvolve.Pulse.SQLite/Outbox/OutboxOptionsExtensions.cs) reuses the shared OutboxOptions. This row from the issue is covered by the OutboxOptionsValidator added for OutboxOptions (TableName not empty). OutboxOptions.ConnectionString is intentionally not validated as required, since it is legitimately null for EF Core-based outbox usage (only ADO.NET-based providers need it) — making it mandatory would break existing valid configurations.

Dependency

This branch is based on feature/241-rabbitmq-channel-pool (not yet merged to main), since RabbitMqTransportOptions.MaxChannelPoolSize — validated here — was introduced there. The diff shown in this PR is scoped to the #238-specific changes on top of that branch.

Notes

Because IValidateOptions<T> runs validation whenever the options are resolved (via IOptions<T>/IOptionsMonitor<T>), not only through the ValidateOnStart() eager startup check, a couple of pre-existing tests that resolved default (and now invalid) option values needed small updates to assert the resulting OptionsValidationException instead of the previous default values / exception types.

Closes #238

Test plan

• dotnet build Pulse.slnx succeeds with no errors.
• csharpier format . run before commit.
• New validator unit tests (one class per validator) covering valid configuration and each invalid field — 59 tests, all passing.
• Existing/updated extension registration tests (OutboxExtensionsTests, RabbitMqExtensionsTests, AzureServiceBusExtensionsTests, etc.) — 557 tests, all passing.
• Verified ValidateOnStart's effect end-to-end: resolving IOptions<OutboxOptions> (and similarly for RabbitMQ/AzureServiceBus) with an invalid configuration throws OptionsValidationException when the service provider builds the options.

[coderabbitai]

Important

Review skipped

Auto reviews are limited based on label configuration.

🏷️ Required labels (at least one) (1)

• state:ready for merge

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 482e9500-9da0-4d3f-a394-81e598ad59e5

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}