maraphon-app/src/Marathon.Application/ApplicationModule.cs

using Marathon.Application.UseCases;
using Microsoft.Extensions.DependencyInjection;

namespace Marathon.Application;

/// <summary>
/// DI registration helpers for the Marathon.Application layer.
/// Call <see cref="AddMarathonApplication"/> from the composition root (host or
/// <c>InfrastructureModule</c>).
/// </summary>
public static class ApplicationModule
{
    /// <summary>
    /// Registers all Application-layer use cases with <c>Scoped</c> lifetime.
    /// Use cases are scoped so that each background-service cycle or UI request
    /// gets a fresh unit-of-work from its own DI scope.
    /// </summary>
    /// <remarks>
    /// No <see cref="Microsoft.Extensions.Configuration.IConfiguration"/> is
    /// required here — the Application layer has no direct configuration bindings.
    /// Infrastructure and UI layers bind their own options against the shared
    /// JSON sections.
    /// </remarks>
    public static IServiceCollection AddMarathonApplication(this IServiceCollection services)
    {
        ArgumentNullException.ThrowIfNull(services);

        services.AddScoped<PullUpcomingEventsUseCase>();
        services.AddScoped<PullLiveOddsUseCase>();
        services.AddScoped<PullResultsUseCase>();
        services.AddScoped<ExportToExcelUseCase>();
        services.AddScoped<DetectAnomaliesUseCase>();
        services.AddScoped<EvaluateAnomalyOutcomesUseCase>();

        services.AddScoped<RecordPlacedBetUseCase>();
        services.AddScoped<ResolvePendingBetsUseCase>();
        services.AddScoped<BuildBetJournalReportUseCase>();
        services.AddScoped<DeletePlacedBetUseCase>();

        return services;
    }
}