admin/CMS
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: refactor week number handling to use WeekDefinitionId across multiple entities and queries

Browse Source
This commit is contained in:
masoodafar-web
2025-12-19 10:41:22 +03:30
parent 3cb95dc349
commit 8b784101be
83 changed files with 17592 additions and 566 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/CMSMicroservice.WebApi/Controllers/AdminController.cs
+4 -4
View File
@@ -34,13 +34,13 @@ public class AdminController : ControllerBase
/// <param name="weekNumber">Week number in YYYY-Www format (e.g., 2025-W48). If null, uses previous week.</param>
/// <returns>Job ID for tracking</returns>
[HttpPost("trigger-weekly-calculation")]
public IActionResult TriggerWeeklyCalculation([FromQuery] string? weekNumber = null)
public IActionResult TriggerWeeklyCalculation([FromQuery] long? weekDefinitionId = null)
{
_logger.LogInformation("🔧 Manual trigger requested by admin for week: {WeekNumber}", weekNumber ?? "previous");
_logger.LogInformation("🔧 Manual trigger requested by admin for WeekDefinitionId: {WeekDefinitionId}", weekDefinitionId?.ToString() ?? "previous");
// Enqueue immediate job execution with specified week number
// Enqueue immediate job execution with specified week
var jobId = _backgroundJobClient.Enqueue<WeeklyCommissionJob>(
job => job.ExecuteAsync(weekNumber, CancellationToken.None));
job => job.ExecuteAsync(weekDefinitionId, CancellationToken.None));
_logger.LogInformation("✅ Job enqueued with ID: {JobId}", jobId);