#3817 (Store debit movements as a negative number instead of using a separate DebitOrCreditField)
by Luc Saffre · in Developers · assigned to Luc Saffre
Résumé
Concepts sous-jacents
Commentaires
- 5 ans, 10 mois ago by Luc Saffre about #3817 (Store debit movements as a negative number instead of using a separate DebitOrCreditField) : Uff, seems that I got it right now. Still waiting for the test results of welfare, and I should probably do manual tests tomorrow.
- 5 ans, 10 mois ago by Luc Saffre about #3817 (Store debit movements as a negative number instead of using a separate DebitOrCreditField) : Seems that there are still some bugs caused by a misinterpretation of the new format.
- 6 ans ago by Luc Saffre about #3817 (Store debit movements as a negative number instead of using a separate DebitOrCreditField) : #1985 is fixed, there is still one susceptible failure in the welfare test suite: Debtors and Creditors have now 15 and 0 instead of 10 and 5 rows.
- 6 ans ago by Luc Saffre about #3817 (Store debit movements as a negative number instead of using a separate DebitOrCreditField) : #1985 seems to have been improved by thise change, but is not yet fixed. ATM it seems not urgent to fix it; i will just disable or adapt the tests without much investigation.
- 6 ans ago by Luc Saffre about #3817 (Store debit movements as a negative number instead of using a separate DebitOrCreditField) : Hurra, it seems that I found the last mistake. Now just some routine work to get the test suites passing.
- 6 ans ago by Luc Saffre about #3817 (Store debit movements as a negative number instead of using a separate DebitOrCreditField) : TODO: sales.DueInvoices should show positive balances (shouldn't it?)
- 6 ans ago by Luc Saffre about #3817 (Store debit movements as a negative number instead of using a separate DebitOrCreditField) : I am almost done... this ticket took more time than expected because accounting demos are a complex network of debits and credits, and because the internal differentiation between d and c is different than before. Lots of subtle changes, and one mistake can cause a lot of changes in the test suite w...
- 6 ans ago by Luc Saffre about #3817 (Store debit movements as a negative number instead of using a separate DebitOrCreditField) : I meanwhile believe that the separate DebitOrCreditField is useless, difficult to explain and has some disadvantages. It is much more intuitive to say that a positive Movement.amount means CREDIT and a negative amount DEBIT. This will cause lots of doctests to fail, will potentially require data mig...