From ed4e00268567916e5d0e081a2e349649c418e87b Mon Sep 17 00:00:00 2001 From: Enes Doner <95379442+EnesDONER@users.noreply.github.com> Date: Mon, 20 May 2024 17:20:39 +0300 Subject: [PATCH] Update docs/en/Community-Articles/2024-05-09-what-is-object-to-object-mapping/post.md Co-authored-by: Engincan VESKE --- .../2024-05-09-what-is-object-to-object-mapping/post.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/en/Community-Articles/2024-05-09-what-is-object-to-object-mapping/post.md b/docs/en/Community-Articles/2024-05-09-what-is-object-to-object-mapping/post.md index a9cb6d8d53..1c6586cf12 100644 --- a/docs/en/Community-Articles/2024-05-09-what-is-object-to-object-mapping/post.md +++ b/docs/en/Community-Articles/2024-05-09-what-is-object-to-object-mapping/post.md @@ -57,7 +57,9 @@ Create a domain entity similar to this one: public DateTime MembershipDate { get; set; } } ```` -`Custumer` contains a lot of attributes. we don't want to give all of these attributes to users, so create dto with only the necessary attributes: +`Customer` entity contains some properties (such as `FirstName`, `LastName`, ... and other audited properties coming from the base class - `DeleterId`, `IsDeleted`, `CreationTime` etc. -). Typically, you would not want to show/return all of these properties to end users, at that point, you can create a DTO class and only define the properties that you want to return to the end users. + +Let's create the `CustomerGetDto` class in the `*.Application.Contracts` project as follows: ````csharp public class CustomerGetDto