v0.2.0-beta.1

[RecurPixel]

[0.2.0-beta.1] — March 2026

New Packages

• RecurPixel.Notify — merged meta-package replacing the separate Core + Orchestrator install
• RecurPixel.Notify.Email.AzureCommEmail
• RecurPixel.Notify.Sms.AzureCommSms
• RecurPixel.Notify.Mattermost
• RecurPixel.Notify.RocketChat

Breaking Changes

• TriggerAsync return type — now returns TriggerResult with IReadOnlyList<NotifyResult> ChannelResults, AllSucceeded, AnySucceeded, and Failures for per-channel inspection
• BulkTriggerAsync return type — now returns BulkTriggerResult with one TriggerResult per input context
• TriggerResult / BulkTriggerResult moved to Core — namespace is now RecurPixel.Notify.Core.Models
• Package restructure — RecurPixel.Notify is now the primary install (Core + Orchestrator). Users of beta.1 should remove RecurPixel.Notify.Core and RecurPixel.Notify.Orchestrator and add RecurPixel.Notify
• Core setup method renamed — AddRecurPixelNotify in Core renamed to AddNotifyOptions to avoid confusion with the Orchestrator overload
• InAppOptions.OnDeliver renamed to UseHandler — aligns with the handler-as-implementation pattern
• Dead properties removed — NotifyOptions.OnDelivery and NotifyOptions.InApp removed; use OrchestratorOptions.OnDelivery and AddInAppChannel respectively
• Namespace reorganization — Major cleanup for cleaner public API surface:
  • Models (NotificationPayload, NotifyResult, BulkNotifyResult, NotifyContext, NotifyUser) moved from RecurPixel.Notify.Core.Models → RecurPixel.Notify
  • Channel interfaces and bases (INotificationChannel, NotificationChannelBase, ChannelAdapterAttribute) moved from RecurPixel.Notify.Core.Channels → RecurPixel.Notify.Channels
  • Core options (NotifyOptions, RetryOptions, FallbackOptions, BulkOptions) moved from RecurPixel.Notify.Core.Options → RecurPixel.Notify
  • Channel-specific options (EmailOptions, SmsOptions, PushOptions, WhatsAppOptions) and all provider credential options moved from RecurPixel.Notify.Core.Options.* → RecurPixel.Notify.Configuration
  • All public channel implementation classes moved to RecurPixel.Notify.Channels (e.g., SendGridChannel, SlackChannel, TwilioSmsChannel, etc.)
  • Services (INotifyService, NotifyService) moved from RecurPixel.Notify.Orchestrator.Services → RecurPixel.Notify
  • All adapter ServiceCollectionExtensions moved from RecurPixel.Notify.[Channel].[Provider] → RecurPixel.Notify

Bug Fixes

• Simple channel registration key mismatch — all simple channels (InApp, Slack, Discord, Teams, Telegram, Facebook, Line, Viber, Mattermost, RocketChat) now register and resolve as "channel:default"
• IOptions<NotifyOptions> not registered — both raw NotifyOptions POCO and IOptions<NotifyOptions> are now registered; ChannelDispatcher receives the correct options
• Adapter credentials not reaching DI — ConfigureAllKnownOptions now maps every provider's credentials from the NotifyOptions POCO into IOptions<TAdapterOptions> at startup; adapters constructed by DI receive real credentials instead of empty defaults
• Telegram ChatId fallback — TelegramChannel now falls back to TelegramOptions.ChatId when payload.To is empty, with a clear error if neither is set
• Misleading XML doc on AddSmtpChannel — corrected; the method is not called internally by AddRecurPixelNotify

DX Improvements

• Single setup call — AddRecurPixelNotify(Action<NotifyOptions>, Action<OrchestratorOptions>) combines options binding, adapter auto-registration, and orchestrator setup in one call
• Auto-registration via assembly scanning — install a provider package and configure its credentials; no Add{X}Channel() call required. [ChannelAdapter] attribute drives discovery at startup
• Config-filtered registration — only adapters with credentials present in NotifyOptions are registered; unconfigured providers have zero DI footprint
• Startup validation — ValidateActiveProviders throws InvalidOperationException at startup when Provider is set but credentials are missing — never silently at send time
• OnDelivery composable — multiple OnDelivery / OnDelivery<TService> registrations are additive; all handlers fire in registration order
• OnDelivery<TService> scoped resolution — creates a fresh DI scope per call; DbContext and other scoped services are safe to use directly without IServiceScopeFactory
• AddInAppChannel + UseHandler<TService> — InApp delivery wired via a typed scoped handler; OnDelivery remains a separate audit hook
• Silent no-send warning — NotifyService logs a warning when a channel is in the event definition but has no payload in NotifyContext.Channels
• Improved ResolveAdapter error — multi-cause diagnostic message when a channel adapter key is not found in DI
• INotifyService channel properties — added Line, Viber, Mattermost, RocketChat direct channel properties
• All adapter extensions use TryAddKeyedSingleton — idempotent; explicit Add{X}Channel() calls and auto-registration no longer conflict

Documentation

• All docs updated — getting-started.md, usage-tiers.md, quick-start.md, features.md rewritten to reflect current API
• New examples.md — Tier 1 (single-channel OTP), Tier 2 (e-commerce), Tier 3 (full SDK), and a production-ready pattern with InApp + OnDelivery + event definitions
• Scoped services pattern documented — OnDelivery<TService> and UseHandler<TService> DI scope behaviour explained
• UseChannels key names documented — logical channel names only ("email", "sms"), not provider names

---

This discussion was created from the release v0.2.0-beta.1.