1ad896b07e
Adds a manual bet-tracking journal that turns the analyzer into an actual bet tracker. Users record wagers; the journal auto-grades them when event results land and computes per-bet Closing-Line-Value against the latest pre-match snapshot — the strongest long-run indicator of betting skill. Domain: - PlacedBet entity (reuses Bet vocabulary for Scope/Type/Side/Value/Rate) with stake, placed-at, outcome, and notes. Derived GrossReturn / NetProfit. - BetOutcome enum (Pending / Won / Lost / Void). - BetOutcomeResolver: pure function grading any Match-scope bet against an EventResult. Handles 1X2, draws, handicap (incl. push), and totals. Period-scope bets stay manual since EventResult only carries full-time. Application: - IPlacedBetRepository abstraction. - ClosingLineValueCalculator: pure CLV math (implied-probability delta) + snapshot-matching predicate by Scope/Type/Side/Value. - BetJournalReport + BetJournalStats records. - Four use cases: Record / ResolvePending / BuildReport / Delete. - New ISnapshotRepository.GetLatestPreMatchAsync pushes the closing-line pick into a single SQLite query rather than materialising the 30-day window in memory per event. - ROI turnover excludes Void stakes — pushes are not real turnover and including them would dilute the user's edge. Infrastructure: - PlacedBetEntity / Configuration / Repository / Mapping helpers. - 20260516 migration adding the PlacedBets table with EventCode and Outcome indices. Intentionally NO foreign key to Events — the journal is user data and must survive snapshot-retention pruning. Covered by an explicit round-trip test. UI: - Pages/MyBets/Journal.razor: hero header, 4-card KPI strip (ROI / strike rate / avg CLV / net profit, tinted by tone), inline add-bet form with the same invariants as the Bet record, drill-down table with per-row outcome pills, CLV percentage-points column, P&L, notes underline, and inline-confirm delete. RU + EN i18n. - Nav entry under Analysis. Tests: +55 across Domain / Application / Infrastructure (resolver math including handicap push and total push boundaries, PlacedBet invariants and derived properties, CLV math + null-handling, four use cases under NSubstitute, EF round-trip including survives-event-deletion). All 379 tests pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
85 lines
3.1 KiB
C#
85 lines
3.1 KiB
C#
using Marathon.Application.Abstractions;
|
|
using Marathon.Domain.Betting;
|
|
using Marathon.Domain.Entities;
|
|
using Marathon.Domain.Enums;
|
|
using Microsoft.Extensions.Logging;
|
|
using DomainEventId = Marathon.Domain.ValueObjects.EventId;
|
|
|
|
namespace Marathon.Application.UseCases;
|
|
|
|
/// <summary>
|
|
/// Sweeps the journal for <see cref="BetOutcome.Pending"/> bets whose events
|
|
/// have been graded, and updates them in bulk via
|
|
/// <see cref="BetOutcomeResolver"/>.
|
|
/// </summary>
|
|
/// <remarks>
|
|
/// Called on demand from the Journal page's "Resolve pending" button. The
|
|
/// design is idempotent — bets that cannot be auto-graded (period-scope, or
|
|
/// no result yet) are left untouched and surface again on the next pass.
|
|
/// </remarks>
|
|
public sealed class ResolvePendingBetsUseCase
|
|
{
|
|
private readonly IPlacedBetRepository _bets;
|
|
private readonly IResultRepository _results;
|
|
private readonly ILogger<ResolvePendingBetsUseCase> _logger;
|
|
|
|
public ResolvePendingBetsUseCase(
|
|
IPlacedBetRepository bets,
|
|
IResultRepository results,
|
|
ILogger<ResolvePendingBetsUseCase> logger)
|
|
{
|
|
_bets = bets ?? throw new ArgumentNullException(nameof(bets));
|
|
_results = results ?? throw new ArgumentNullException(nameof(results));
|
|
_logger = logger ?? throw new ArgumentNullException(nameof(logger));
|
|
}
|
|
|
|
/// <summary>
|
|
/// Returns the number of bets that were transitioned out of Pending in this pass.
|
|
/// </summary>
|
|
public async Task<int> ExecuteAsync(CancellationToken ct = default)
|
|
{
|
|
var pending = await _bets.ListByOutcomeAsync(BetOutcome.Pending, ct).ConfigureAwait(false);
|
|
if (pending.Count == 0)
|
|
{
|
|
_logger.LogInformation("ResolvePendingBetsUseCase: no pending bets");
|
|
return 0;
|
|
}
|
|
|
|
// Cache results per event so we do not re-query for each bet on the same event.
|
|
var resultCache = new Dictionary<DomainEventId, EventResult?>();
|
|
var resolvedCount = 0;
|
|
|
|
foreach (var bet in pending)
|
|
{
|
|
ct.ThrowIfCancellationRequested();
|
|
|
|
if (!resultCache.TryGetValue(bet.EventId, out var result))
|
|
{
|
|
result = await _results.GetAsync(bet.EventId, ct).ConfigureAwait(false);
|
|
resultCache[bet.EventId] = result;
|
|
}
|
|
|
|
if (result is null) continue;
|
|
|
|
var graded = BetOutcomeResolver.Resolve(bet.Selection, result);
|
|
if (graded is null) continue;
|
|
|
|
var updated = bet.WithOutcome(graded.Value);
|
|
await _bets.UpdateAsync(updated, ct).ConfigureAwait(false);
|
|
resolvedCount++;
|
|
}
|
|
|
|
// Save before logging — if the batch fails, an exception bubbles out and
|
|
// the success-count log is never emitted; we never report a graded count
|
|
// that was rolled back.
|
|
if (resolvedCount > 0)
|
|
await _bets.SaveChangesAsync(ct).ConfigureAwait(false);
|
|
|
|
_logger.LogInformation(
|
|
"ResolvePendingBetsUseCase: graded {Resolved} of {Pending} pending bets",
|
|
resolvedCount, pending.Count);
|
|
|
|
return resolvedCount;
|
|
}
|
|
}
|