title: Is redundancy ok in GraphQL?
body: <p>Say I have the following types in my schema:</p>
  
  <pre><code>type Deposit { timestamp, ... }
  
  type Withdrawal { timestamp, ... }
  
  type Cancellation { timestamp, ... }
  </code></pre>
  
  <p>There's a page in my app where I display the transaction history. Since there's no rule enforcing the order of transactions (except for the first deposit, of course), I can't know the chronological order in advance, even if each type has a <code>timestamp</code> property.</p>
  
  <p>Now, I could write a sorting algorithm, but I'd avoid adding complexity to my codebase.</p>
  
  <p>So I thought about doing this:</p>
  
  <pre><code>type History { transactionType }
  </code></pre>
  
  <p>Where <code>transactionType</code> is either "Deposit", "Withdrawal" or "Cancellation".</p>
  
  <p>But of course, this comes at the expense of redundancy on my server. Is this good GraphQL practice?</p>