From 6cf7b9615cac2f9bbc2b3619b001dd5554f9edde Mon Sep 17 00:00:00 2001 From: Enes Doner <95379442+EnesDONER@users.noreply.github.com> Date: Mon, 20 May 2024 17:17:44 +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 | 2 +- 1 file changed, 1 insertion(+), 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 aeb341a42d..38d5650214 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 @@ -1,4 +1,4 @@ -# What is Object to Object Mapping +# What is Object to Object Mapping? Mapping the properties of one object to the properties of another object is called Object to object mapping. Most of the time we don't want to show the data we store to end users as it is. We only give users the information they will use for that operation. In tables that contain relationships, we analyze the relationships and present meaningful data to users. For example, suppose we have a product and a category object, we keep an attribute called categoryId in the product object. However, it would be illogical to show the categoryId attribute to users. Therefore, we create dto's (data transfer objects) and show the category name attribute to users instead of the category Id attribute.