Currently, the time code is stored as an integer. When I am reading my daily note or the CSV my brain has difficulty in determining date and time as we know it. Besides, using the integer timestamp might introduce problems if the time parsing library happens to use a different epoch. Like, excel and matlab use different epochs.
I know it puts more load on the parsing process when the simple time tracker is loaded, but as I want to use my MarkDown notes also outside Obsidian and Simple Time Tracker I would be very happy if date time is stored in a neutral, globally known format. In something like ISO8601.
This would also save me a lot of trouble correcting date and time when I started the tracker too late or want to add extra entries manually.
codejager
commented
12 months ago
Currently, the time code is stored as an integer. When I am reading my daily note or the CSV my brain has difficulty in determining date and time as we know it. Besides, using the integer timestamp might introduce problems if the time parsing library happens to use a different epoch. Like, excel and matlab use different epochs.
I know it puts more load on the parsing process when the simple time tracker is loaded, but as I want to use my MarkDown notes also outside Obsidian and Simple Time Tracker I would be very happy if date time is stored in a neutral, globally known format. In something like ISO8601. This would also save me a lot of trouble correcting date and time when I started the tracker too late or want to add extra entries manually.