address inconsistency with the naming of "description" in transaction structures #123
Description
A basic double journal entry is:
Date:
Amount:
Account:
Description:
In several places throughout the codebase the description field is named something else (ie Payee) mostly due to copying other code bases code. This description field ultimately will contain all information about the transactions and should be large enough to contain an extremely detailed and long field.
In addition this is where the second layer of transaction descriptions would occur. So serializing the transaction data and saving as JSON in this description to allow for clients to investigate a general transaction without a human decoding what happened.