From 1df9235036a94825c0bff4735806407a856542ea Mon Sep 17 00:00:00 2001
From: Developer 02 <developer02@didaloghe.onmicrosoft.com>
Date: Thu, 15 Jan 2026 23:54:28 +0100
Subject: [PATCH] Disambiguate Profile mapping in AutoMapper configuration

Updated the mapping configuration in `DtoMappingProfile` to use
the fully qualified name `Domain.Entities.Profile` for the
`Profile` entity. This change resolves potential ambiguity with
other classes named `Profile` in the codebase.
---
 src/ReC.Application/Common/Dto/DtoMappingProfile.cs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/ReC.Application/Common/Dto/DtoMappingProfile.cs b/src/ReC.Application/Common/Dto/DtoMappingProfile.cs
index 3709e7b..3040c4c 100644
--- a/src/ReC.Application/Common/Dto/DtoMappingProfile.cs
+++ b/src/ReC.Application/Common/Dto/DtoMappingProfile.cs
@@ -15,7 +15,7 @@ public class DtoMappingProfile : AutoMapper.Profile
         CreateMap<EndpointAuth, EndpointAuthDto>();
         CreateMap<Endpoint, EndpointDto>();
         CreateMap<EndpointParam, EndpointParamDto>();
-        CreateMap<Profile, ProfileDto>();
+        CreateMap<Domain.Entities.Profile, ProfileDto>();
         CreateMap<RecAction, RecActionDto>();
 
         CreateMap<ResultView, ResultViewDto>();