Refactor BuildVerifyUserEmailAction to accept User entity instead of user ID

- Updated IUserRepository and its implementations to change the parameter of BuildVerifyUserEmailAction from Guid userId to User user.
- Modified related repository methods in Dapper and Entity Framework to utilize the User entity for email verification.
- Adjusted tests to reflect the new method signature, ensuring proper functionality and integration with the updated user verification process.
This commit is contained in:
Rui Tome
2026-01-29 17:19:37 +00:00
parent 7ed77176e2
commit 71047bee2a
6 changed files with 13 additions and 19 deletions

View File

@@ -320,7 +320,7 @@ public class OrganizationRepositoryTests
{
organizationRepository.BuildUpdateOrganizationAction(organization),
organizationUserRepository.BuildConfirmOrganizationUserAction(organizationUser),
userRepository.BuildVerifyUserEmailAction(user.Id)
userRepository.BuildVerifyUserEmailAction(user)
};
var collection = new Collection
@@ -403,7 +403,7 @@ public class OrganizationRepositoryTests
{
organizationRepository.BuildUpdateOrganizationAction(organization),
organizationUserRepository.BuildConfirmOrganizationUserAction(organizationUser),
userRepository.BuildVerifyUserEmailAction(user.Id)
userRepository.BuildVerifyUserEmailAction(user)
};
// Execute all updates in single transaction
@@ -453,7 +453,7 @@ public class OrganizationRepositoryTests
{
organizationRepository.BuildUpdateOrganizationAction(organization),
organizationUserRepository.BuildConfirmOrganizationUserAction(organizationUser),
userRepository.BuildVerifyUserEmailAction(user.Id),
userRepository.BuildVerifyUserEmailAction(user),
// Add a failing action to trigger rollback
(Microsoft.Data.SqlClient.SqlConnection? _, Microsoft.Data.SqlClient.SqlTransaction? _, object? __) =>
{