Schema change

[ebcrowder]

Changes:

• Refactors each module and related integration tests to utilize a new YAML schema. A populated example of this new schema is as follows:

  
  accounts:
  - account: asset:cash_checking
  amount: 1500
  - account: asset:cash_savings
  amount: 2000
  - account: liability:credit_card_amex
  amount: 0
  - account: equity:equity
  amount: -3500
  - account: expense:grocery
  amount: 0
  - account: expense:general
  amount: 0
  - account: expense:mortgage
  amount: 0
  - account: income:general
  amount: 0

transactions:

• date: 11/4/2019 amount: 455 description: weekly groceries account: expense:grocery offset_account: liability:credit_card_amex
• date: 07/04/2020 amount: 2000 description: mortage account: expense:mortgage offset_account: asset:cash_checking
• date: 07/04/2020 description: stuff transaction:
  • amount: 1000 account: expense:general
  • amount: -1000 account: asset:cash_savings
• date: 06/21/2020 description: grocery store transaction:
  • amount: 20 account: expense:general
  • amount: 180 account: expense:grocery
  • amount: -200 account: asset:cash_checking

    
    Compared to the original schema, the new schema includes less fields and therefore significantly improves readability and reduces redundancy. 

• Further, transactions are more flexible and declarative. Transactions that only involve two accounts (a debit and an offsetting credit, or vice-versa) can be expressed in a short-hand method:

  - date: 11/4/2019
  amount: 455
  description: weekly groceries
  account: expense:grocery
  offset_account: liability:credit_card_amex

  Alternatively, the transaction postings can be specified in detail:

  - date: 11/4/2019
  description: weekly groceries
  transaction: 
    - amount: 455
      account: expense:groceries
    - amount: -455
      account: liability:credit_card_amex

  rust_ledger treats both of the above transactions in the same manner. This allows the user more flexibility in expressing transactions in their individual YAML file.

transactions that involve more than two accounts would need to use the second format.

[ebcrowder]

I believe all of the modules are working and meet parity with the current implementation.

I am working on formatting the register output a bit to expand the 3rd and 4th columns for readability. Currently, account names with a certain length throw off the terminal output a bit. Running the code with example.yaml will illustrate this. Any comments you may have regarding this or any other items you may find would be appreciated.

Thanks!

[dantuck]

This looks really clear. I did make some suggested changes but then removed them because I made a mistake in how I was writing the code. Your work looks great and this is a solid step. Great work!

[ebcrowder]

Appreciate the review, @dantuck!