mirror of
https://github.com/jrnl-org/jrnl.git
synced 2025-05-20 13:08:31 +02:00
1fa851ed0c
Ever since version 2.0, when parsing a journal file, jrnl would not use the custom date format string anymore. Instead, it relied on the dateutil library to get the parsing right. This change was made to allow people to change their date format without having to manually change their file. However, this broke some existing date formats like %d.%m.%Y, as it would falsely interpret the month as day and vice versa. This commit adds some tests to catch this error and fixes it by trying to parse the dates using the custom format first, only falling back to dateutil when needed.
34 lines
1.3 KiB
Gherkin
34 lines
1.3 KiB
Gherkin
Feature: Upgrading Journals from 1.x.x to 2.x.x
|
|
|
|
Scenario: Upgrade and parse journals with square brackets
|
|
Given we use the config "upgrade_from_195.json"
|
|
When we run "jrnl -9" and enter "Y"
|
|
Then the output should contain
|
|
"""
|
|
2010-06-10 15:00 A life without chocolate is like a bad analogy.
|
|
|
|
2013-06-10 15:40 He said "[this] is the best time to be alive".
|
|
"""
|
|
Then the journal should have 2 entries
|
|
|
|
Scenario: Upgrading a journal encrypted with jrnl 1.x
|
|
Given we use the config "encrypted_old.json"
|
|
When we run "jrnl -n 1" and enter
|
|
"""
|
|
Y
|
|
bad doggie no biscuit
|
|
bad doggie no biscuit
|
|
"""
|
|
Then we should see the message "Password"
|
|
And the output should contain "2013-06-10 15:40 Life is good"
|
|
|
|
Scenario: Upgrade and parse journals with little endian date format
|
|
Given we use the config "upgrade_from_195_little_endian_dates.json"
|
|
When we run "jrnl -9" and enter "Y"
|
|
Then the output should contain
|
|
"""
|
|
10.06.2010 15:00 A life without chocolate is like a bad analogy.
|
|
|
|
10.06.2013 15:40 He said "[this] is the best time to be alive".
|
|
"""
|
|
Then the journal should have 2 entries
|