Allow space separator in date parsing in import
Reported by frog | April 9th, 2012 @ 08:02 AM
One of my banks produces CSV files with dates in the following
format: "04 APR 2012"
moneyGuru does not like this because the separator is a space,
rather than a hyphen '-' or forwardslash '/' character.
If it doesn't break any other functionality of the CSV parsing, it'd be useful for me if moneyGuru could allow space separators for dates
(to be honest it's only an issue for me because of the other bug I reported in QIF importing, but seems general enough to me that it might be useful to others too)
Comments and changes to this ticket
-
Virgil Dupras April 10th, 2012 @ 05:00 PM
- State changed from new to accepted
- Tag changed from import to feature, import
If it exists somewhere, it's worth supporting.
-
Virgil Dupras September 13th, 2012 @ 04:17 PM
- Assigned user set to Virgil Dupras
-
Virgil Dupras September 13th, 2012 @ 04:30 PM
- State changed from accepted to fixed
(from [26431e6aad84]) [#324 state:fixed] Added spaces as a possible date element separator in date format guessing routine. https://bitbucket.org/hsoft/moneyguru/changeset/26431e6aad84/
-
Virgil Dupras September 14th, 2012 @ 05:49 PM
(from [4d76edec957f]) [#324] Fixed the bogus commit previously fixing this ticket.
First, I hadn't noticed that there was already a higher-level, more proper place for date format guessing tests in import_test, so I didn't put the test in the right place. Moreover, the test being more high level revealed that I didn't adjust the regexp for possibly correct dates, which I do in this commit.
https://bitbucket.org/hsoft/moneyguru/changeset/4d76edec957f/
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป