Preferred approach for implementing multi-card per merchant support? about debbit HOT 4 CLOSED

I've gotten requests from some users to support differing numbers of transactions per card. One user has four cards which need 60, 60, 15, and 15 transactions respectively.

This is a complicated change to make. I'm also looking at redesigning the config system in general to separate out merchant by merchant. Another user just wrote a module for AT&T which now brings the monolith config file to 4 merchants. It's getting long and hard to read through in a text editor.

How about I handle this change? I've got the whole day open so I was planning on working on debbit anyway. 🙂

from debbit.

Nice - that's why I checked, I'll hold off!

I'm also looking at redesigning the config system in general to separate out merchant by merchant.

That'd be really cool. I've got the auto-archive thing I alluded to over in #3 working, but it uses this hacky approach (the dry_run feature was something else I was playing with):

--- a/src/sample_config.txt
+++ b/src/sample_config.txt
@@ -11,6 +11,10 @@ amazon_gift_card_reload:
     # change this to True after configuring the options below
     enabled: False
 
+    merchant_specific_config:
+        # Set to true to automatically archive the latest gift card reload
+        archive: True
+
     # Set this to true to skip the actual GC-reload - useful for testing
     dry_run: False

Might put up a PR anyway, even if I have to rebase/redo it later.

from debbit.

Has the multi-card per merchant feature been implemented yet? I'm not seeing it, but I'm new to this site so I may not be looking in the right place. I have 3 debit cards that I put 10-12 Amazon reload transactions on every month, and it would be great to get it automated!

from debbit.

Given this is implemented now, closing!

from debbit.