cilynx / all-of-the-things Goto Github PK

If you have multiple identical (same date, action, memo, and price) transactions in an import, the dedupe logic assumes only the first transaction is legit and drops the rest. One possible solution is to add logic to the import routine not to dedupe transactions that came from the current import session. That still leaves the edge case of an existing transaction matching a newly imported transaction, but legitimately being two transactions. Managing that edge case may require real-time user-input.

Everyone else seems to be doing local database integration. I feel like taskd integration would be better, but setting up taskd looks like a PITA. At the end of the day, we should probably support both.