You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DKBRobo.get_credit_limits() - ✅ - released with 0.25
DKBRobo.get_exemption_order()- ❌
DKBRobo.get_points() - ❌
DKBRobo.get_standing_orders()) - ✅ - released with 0.25
DKBRobo.get_transactions()-:white_check_mark: - released with 0.23
DKBRobo.last_login- ❌
DKBRobo.login() - ✅ - released with 0.22
DKBRobo.scan_postbox - ✅ - released with 0.25
breaking changes when migrating to the new frontend:
I am trying to ensure a certain level of backwards compatibility however there are a few changes you need to be aware when migrating to the new frontend.
general
default date format is changed to %Y-%m-%d
DKBRobo.account_dic()
account ordering is based on the new frontend
debit cards are shown in overview
IBANs are now represented without spaces
card numbers are masked
product groups (taken from UI) are shown in account overview
The old frontend will be supported as long it is available. The plan is to use the legacy_login parameter switch between old and new frontend. I will also try to keep method names inside the DKBRobo() class the same. There might be some smaller changes (f.iiorder of accounts and cards in dkb.account_dic) but overall look and feel should stay more or less similar.
migration status
breaking changes when migrating to the new frontend:
I am trying to ensure a certain level of backwards compatibility however there are a few changes you need to be aware when migrating to the new frontend.
general
%Y-%m-%d
DKBRobo.account_dic()
DKBRobo.get_standing_orders()
interval
subtree added)DKBRobo.get_transactions()
DKBRobo.scan_postbox()
The text was updated successfully, but these errors were encountered: