Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ability to recategorize based on config (or ignore existing QIF category) #66

Closed
Koguni31 opened this issue Oct 22, 2016 · 4 comments
Labels
Milestone

Comments

@Koguni31
Copy link

Koguni31 commented Oct 22, 2016

My bank exports credit card transactions in QIF format with two already existing categories - "expense" and "income". Then using qifqif on such an file, only applicable but unusable mode is "-a", because it asks on every single transaction to acknowledge existing category, or edit.

It would be great to have switch to ignore existing categories and rewrite them based on qifqif config file and user input (if no match on config entries).

@Kraymer Kraymer changed the title Feature request: add ability to recategorize based on config (or ignore existing QIF category) Add ability to recategorize based on config (or ignore existing QIF category) Oct 22, 2016
@Kraymer
Copy link
Owner

Kraymer commented Oct 22, 2016

Make a lotta sense.

What do you think of adding an [a]llwayschoice to the Edit 'xxx' category ? question in audit mode ?
So you press A twice (one for each category present in file) then all transactions of file are processed directly in edit mode.

@Kraymer
Copy link
Owner

Kraymer commented Oct 22, 2016

Forget that I'll probably just add a --force mode.

@Koguni31
Copy link
Author

May be --ignore category1,category2,category3 and --ignoreall switches?

Kraymer added a commit that referenced this issue Oct 23, 2016
.qif files downloaded from bank websites may have a category
already set. `-force` flag enable easy editing of such file by
discarding file categories that are not keys of config dict.
@Kraymer Kraymer modified the milestone: 0.7.0 Oct 24, 2016
@Kraymer
Copy link
Owner

Kraymer commented Oct 29, 2016

Version 0.7.0 with this fix has been just shipped and can be installed via pip.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants