Commit Graph

4 Commits

Author SHA1 Message Date
3a21b3ba94 Improve RabbitMQ configuration handling in DI setup
Refactor the `DependencyInjection` class to enhance the
validation and setup process for `RabbitMQ` when used as
the `ConsumerType`. Remove the outdated logic for adding
an HTTP client based on `options.ApiUrl`. Introduce a
check for `options.RabbitMQ` and throw a detailed
`InvalidOperationException` if it is missing. Use
`services.AddMessagingServiceClient` to configure the
messaging service client with the appropriate section name.
2026-11-17 20:22:50 +01:00
224d029c18 Refactor DI and update dependencies
- Enhanced `AddAutoMapper` configuration for flexibility.
- Replaced `IEnvelopeMailService` with `IEnvelopeNotificationService`.
- Migrated from `IUserRepository` to `EGDbContext` for data access.
- Updated RabbitMQ configuration to use `AddMessagingServiceHttpClient`.
- Removed `AddUserManager` and `AddDispatcher` registrations.
- Added conditional `FluentValidation` dependencies for target frameworks.
- Upgraded `MediatR` to 14.2.0 and `AutoMapper` to 16.2.0.
- Added `HtmlSanitizer` dependency.
- Improved error handling and logging in `ReadOnlyController`.
2026-11-17 20:09:23 +01:00
2913514da8 feat(notification): make messaging consumer configurable
Replace the hard-coded RabbitMQ setup with NotificationOptions bound from a configurable section. The new ConsumerType switch wires either the HTTP API client or the RabbitMQ client, and startup now fails with a clear error when required settings are missing.

Bump DigitalData.MessagingService.Client to 3.0.1 for the abstraction used by both transports.
2026-11-05 12:03:26 +01:00
658cb28e1c Add notification infrastructure project 2026-10-22 01:35:18 +02:00