[Bug] Diarium tracker values with a colon are imported incorrectly

[EvanFreyer]

Describe the bug

When importing a Diarium export that includes tracker values with a colon, they will be parsed incorrectly. Only the last part of the string will be saved as the value while everything before the colon will be imported as part of the tracker name.

For example: If you have a tracker called "Foo" and add a tracker value called "Foo: Bar" into an entry, it will appear as a property named "Foo: Foo" with the value "Bar" after importing it to Obsidian

To Reproduce

Steps to reproduce the behavior:

1. Create a Diarium tracker called "Foo"
2. Create a Diarium entry with a tracker value "Foo: Bar"
3. Export the Diarium data and import in Obsidian
4. Look into the imported entry and observe created property

Expected behavior

The property should be called "Foo" with a value "Foo: Bar"

Specs

• Platform: Export on iOS 18, Import on macOS 14.7.2
• Plugin version: 1.2.22

Additional context

I love your plugin! Thanks for creating it!

[Erallie]

@EvanFreyer So this is actually more difficult, because the way that the tracker values are stored in the .json file that it exports is a single string for each tracker, with the tracker name and the tracker value only separated by a colon. So if you have a tracker named "Foo" and the tracker value named "Foo: Bar", it would look like, "Foo: Foo: Bar" in the .json that it exports. You would either need to choose to split the key and the value at the first colon or the last colon.

Given, I was able to make a setting in the import so that you can choose between the two options. Please try out the latest release, and let me know if it works!