This repository has been archived by the owner on Feb 25, 2022. It is now read-only.
Introduce config flag for N26 to only import processed transactions #38
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background story
Because the values that we get from the (not official) N26 API change from time to time, people often end up with duplicated transactions.
There has already been effort in avoiding that but it is still happening.
What the PR will do
This PR will introduce a new config flag for the N26 Dumper called
skip_pending_transactions
.This setting will be set to
false
by default. When set to true, all transactions that are still pending (= not processed by N26) won't be imported by the script until they are processed.This will prevent duplicate entries but comes with the tradeoff that it might take a few days for transactions to show up in your YNAB.
The PR will fix #36.