Fix enex import stores wrong format in database for dateCreated, dateModified

[contributor]

This PR fixes bug in enex import.

The problem is that dateCreated, dateModified field values get wrong format during import (Z, without hours offset), while trilium app expects the fields to be in format 2025-11-12 21:38:51.110+0100 (or in 2025-11-12 21:38:51.110+0000 if your timezone is UTC).

Data from DB to illustrate the problem:

Data from enex file:

<created>20180719T222544Z</created><updated>20230418T211749Z</updated>
<created>20131108T144429Z</created><updated>20220610T112525Z</updated>

Original data in evernote:

With this PR, data in DB is:

dateCreated and dateModified are converted to electron/server local time zone from enex's UTC value. This is what most users would expect.

[gemini-code-assist]

Summary of Changes

Hello @contributor, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a critical bug in the Enex import functionality that caused dateCreated and dateModified fields to be stored in an incompatible format within the database. By implementing a dedicated date formatting utility and utilizing standardized format constants, the changes ensure that all imported dates adhere to the application's expected timestamp structure, thereby resolving data integrity issues and improving consistency.

Highlights

• Date Formatting Correction: Fixed a bug in the Enex import process where dateCreated and dateModified fields were stored in an incorrect format in the database. The previous format (Z without offset) did not match the application's expected format (YYYY-MM-DD HH:mm:ss.SSS+ZZZZ).
• New Date Formatting Utility: Introduced a new helper function, formatDateTimeToLocalDbFormat, within the Enex import service to correctly format dates from Enex for database storage, ensuring they include the necessary timezone offset.
• Exported Date Format Constants: Exported LOCAL_DATETIME_FORMAT and UTC_DATETIME_FORMAT from date_utils.ts to make these standard date formats reusable across the application.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly addresses a bug where dateCreated and dateModified were stored in an incorrect format during ENEX file imports. The introduction of the formatDateTimeToLocalDbFormat function and its use of dayjs to format dates into the expected local time format with a timezone offset is a solid fix. The changes are logical and well-contained. I've added one suggestion to refactor the new helper function for improved readability and to align with modern TypeScript best practices.