Skip account valuation on entry balance_after_entry #1435

Merged
bruno-costanzo merged 1 commits from 1418-skip-account-valuation-on-balance-after-entry into main 2024-11-08 22:17:55 +08:00
bruno-costanzo commented 2024-11-08 21:00:10 +08:00 (Migrated from github.com)

Why?

Partially Fixes 1418

When creating a transaction after an account valuation, the latter should not be considered in the calculation of the balance of the entry.

What?

Change the entry model in order to skip the account valuation amount in the balance_after_entry
image

What should we test?

Create an account valuation and a transaction after, and ensure the account valuation is not part of the calculation of the balance_after_entry within the context of the transaction.

Pending

There is another error related with Issue 1418, related to the way in which the amount of an account valuation is calculated, which in turn can cause the incorrect icon to be displayed.

Paired with @nicogaldamez

### Why? Partially Fixes [1418](https://github.com/maybe-finance/maybe/issues/1418) When creating a transaction after an account valuation, the latter should not be considered in the calculation of the balance of the entry. ### What? Change the entry model in order to skip the account valuation amount in the balance_after_entry ![image](https://github.com/user-attachments/assets/3b3739ab-63f2-4c09-923b-6fe05562db43) ### What should we test? Create an account valuation and a transaction after, and ensure the account valuation is not part of the calculation of the balance_after_entry within the context of the transaction. ### Pending There is another error related with [Issue 1418](https://github.com/maybe-finance/maybe/issues/1418), related to the way in which the amount of an account valuation is calculated, which in turn can cause the incorrect icon to be displayed. Paired with @nicogaldamez
zachgoll (Migrated from github.com) approved these changes 2024-11-08 22:17:38 +08:00
zachgoll (Migrated from github.com) left a comment

Thanks for the fix here!

Thanks for the fix here!
Sign in to join this conversation.