title: When do we need to create a new custom DTO?
body: <p>I had an Entity named User that can have many services (Entity Service) and I have two actions one of them with the name GetUser() and the other with name GetUserServices()</p>
  <ul>
  <li>GetUser() : fetch the user and return an Custom DTO with name UserDto</li>
  </ul>
  <pre class="lang-cs prettyprint-override"><code>public class UserDto
  {
  public int Id {get;set;}
  public string Username {get;set;}
  } 
  </code></pre>
  <ul>
  <li>GetUserServices() : fetch the user and its services ids, let's say at some point I want to return on this function these properties [UserId, Username, ServicesIds] my question is should I modify the UserDto by adding ServicesId property [1] or create another Custom DTO [2] ?</li>
  </ul>
  <hr />
  <ol>
  <li>If I go with the solution [1] means that GetUser() will return a JSON object with empty ServicesId property and that's will lead to bad UX</li>
  <li>If I go with the solution [2] that will lead to create for each action I had, a custom DTO depends on the shape of data returned, and also I'll struggle with figure out the name for each created custom DTO.</li>
  </ol>