hakierspejs/ksiemgowy

Program powiadamiający o statusie składek HSŁódź

ksiemgowy's Issues

Migrate to new sqlalchemy ORM style

I think I'm currently using version 1 of sqlalchemy ORM. Docs seem to suggest that it's deprecated, so let's migrate to v2.

Nie używaj zmiennych środowiskowych do odbierania parametrów

Get rid of the concept of corrections

While refactoring corrections, I realized how bad idea it really was. Let's add an external seed file that contains all transactions that were not mentioned in e-mails and keep consistency this way.

Run some performance tests, optimize

Not a high priority, but it would be nice to know which parts of the project fall apart when stress tested and how much data it takes for that to happen. Pretty sure it will uncover some missing indices or inefficient queries.

Fix overdue notifications in case of paying upfront

Add a way to disable anonymization

Deployment would be simpler without it, so maybe let's make it optional.

Napisz test na główny kod homepage_updater

Dołącz homepage_updatera do ksiemgowyd?

Zaczynam mieć wrażenie że robienie oddzielnych kontenerów na takie rzeczy niepotrzebnie komplikuje kod i lepiej byłoby włączyć to w kompetencje ksiemgowyd.

Prawdopodobnie ułatwi #4.

homepage_updater: make things specific to Hakierspejs optional (d33tah's fees, autoreservations)

This includes:

• d33tah's fees
• autoreservations

Because of that, the code could be reused in other scenarios.

Split out sender_acc_no_to_email into sender_acc_no_to_email and notification_settings

User might have more than one account, but just one set of settings. E-mail will probably be the primary key.

Once SSH agent is not needed anymore, terminate it

Combine expenses and positive_actions in one table

Given that we have interface for separately getting expenses and incoming transfers, it might be as simple as storing ones with a negative number and then flipping it in the iterator (and during saving)

W przypomnieniach o przelewie, podawaj nowy numer konta

Change types of notify_* in in_acc_no_to_email from string to boolean

Don't store financial data as floating-point numbers

Multiplying them by 100 could lead to better predictability.

Zmień nazwę mbank_actions na positive_actions

Albo coś w tym stylu.

Połącz private_state i public_state

Ten eksperyment chyba nie wyszedł, a kod się uprości po takim refactorze

Nie wymagaj MBANK_ANONYMIZATION_KEY przy importowaniu

To komplikuje używanie różnego rodzaju narzędzi. MBANK_ANONYMIZATION_KEY powinien być przekazywany przez stos, a nie zmienną globalną.

Between 55 and 65 days of overdue, CC the operator

Zoptymalizuj was_imap_id_already_handled

Document administrative tasks

Keep in mind that the anonymization complicates the picture.

Fix too-many-instance-attributes in ReportBuilderConfig

Right now we have a manual pylint override for ReportBuilderConfig class that contains too many instance attributes. It might be a good idea to try fixing it.

Napisz test end-to-end

1. Zamockuj sprawdzanie maili
2. Zamockuj schedule
3. Sprawdź, czy wysłano potwierdzenie przelewu
4. Sprawdź, czy działa update na github

Add an automated way to unsubscribe

Document how to make manual corrections to the balance

Add discrepancy detection when handling single transfers

Sometimes, we're only getting a single transfer in a given e-mail update. This transfer contains the "balance" field, which allows us to compare whether what we think the account balance is matches the reality. It might be a good idea to add a routine that compares the latest balance to our information and reports it to the operator.

Add a way to not specify the list of watched accounts

On some setups, watching for any transfer that was observed in any account is fine. Let's add such an option.

Fix too-many-instance-attributes in MbankAction

Right now we have a manual pylint override for MbankAction class that contains too many instance attributes. It might be a good idea to try fixing it.