Fix inaccurate comment in SaveEntitiesAsync

[rhodi2436]

The original comment claimed that dispatching domain events AFTER SaveChanges (option B) would result in multiple transactions. This was true before TransactionBehavior was introduced, but since TransactionBehavior wraps the entire command handler in an explicit transaction, both orderings now result in a single database transaction.

Update the comment to accurately describe the real trade-off between the two approaches, and note that the explicit transaction uses ReadCommitted isolation (see BeginTransactionAsync), which means handlers in option B can observe already-flushed state via SQL queries within the same transaction.

[rhodi2436]

@dotnet-policy-service agree

[Copilot]

Pull request overview

Updates the SaveEntitiesAsync documentation in Ordering’s EF Core DbContext to reflect the current transactional behavior now that MediatR commands are wrapped in an explicit transaction via TransactionBehavior.

Changes:

• Replaces the outdated “multiple transactions” explanation with an updated trade-off discussion for dispatching domain events before vs. after SaveChanges.
• Notes the explicit transaction and mentions ReadCommitted isolation and what handlers can observe in option B.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (1)

src/Ordering.Infrastructure/OrderingContext.cs:69

• The comment says the SaveChangesAsync call "will be committed", but when SaveEntitiesAsync runs under TransactionBehavior the changes are only flushed to the database and are not committed until CommitTransactionAsync commits the explicit transaction. Consider rewording this to avoid implying the data is committed at this point.

        // After executing this line all the changes (from the Command Handler and Domain Event Handlers) 
        // performed through the DbContext will be committed
        _ = await base.SaveChangesAsync(cancellationToken);