Double check behavior works (for the most part) for all core product requirements

[ChrisRichardMiles]

Verify frontend works for:

• [x] POST /entries

  • Create a new credit or debit ledger entry

• [x] GET /entries

  • Retrieve all ledger entries

• [x] GET /entries/{entry_id}

  • Retrieve a ledger entry, filtered by id

• [x] GET /entries?account_name={name}

  • Retrieve all ledger entries, filtered by account name

• [x] PATCH /entries/{entry_id}

  • Update the amount and/or description of a ledger entry, filtered by id.
  • Note: Other fields are not editable.

• [x] DELETE /entries/{entry_id}

  • Delete a ledger entry, filtered by id

• [x] GET /summary

  • Retrieve a summary of the ledger, with the following fields:
  • Total number of debits
  • Total debit amount
  • Total number of credits
  • Total credit amount
  • is_balanced: True or False (credit amount == debit amount)

[ChrisRichardMiles]

They definitely work correct if you use them correctly. As far as I know, they do not violate any specific tech specs, but they may do more than they should (maybe there's a way to add a negative number in an entry when you shouldn't be able to or something).

[ChrisRichardMiles]

closed