jrnl/features
Peter Schmidbauer 1fa851ed0c Fix handling of little-endian date format
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.
2019-10-26 21:58:15 +02:00
..
data Fix handling of little-endian date format 2019-10-26 21:58:15 +02:00
steps Fix issue #584 YAMLLoadWarning (#585) 2019-04-14 09:47:31 -07:00
core.feature Split tests 2015-04-20 14:13:34 +02:00
custom_dates.feature Fix handling of little-endian date format 2019-10-26 21:58:15 +02:00
encryption.feature [GH-632] confirming that each journal can be parsed during upgrade, and aborting upgrade if not 2019-08-24 13:50:10 -07:00
environment.py Tests for new structure 2013-11-29 10:23:16 -08:00
exporting.feature [Markdown Export] deal with linebreaks in jrnl files 2019-08-01 21:00:53 -06:00
multiple_journals.feature Modify test to test for returned strings 2019-08-04 08:44:17 +12:00
regression.feature [GH-632] confirming that each journal can be parsed during upgrade, and aborting upgrade if not 2019-08-24 13:50:10 -07:00
starring.feature Update all tests to new time format 2015-04-05 03:25:39 +04:00
tagging.feature Add tests for the excluding tags with -not 2019-08-07 20:58:35 -04:00
upgrade.feature Fix handling of little-endian date format 2019-10-26 21:58:15 +02:00