Important Journal CLI updates
Just a couple quick updates to the Journal CLI I published yesterday that I wanted everyone who was trying it out to know about before they have too much data in it.
First, if keys were nested using dot syntax, e.g. health.rating
and health.sleep
, it would create a hash like:
{
"health": {
"health": {
"rating" : 5,
"sleep": 7
}
}
As you can see, the “health” key got doubled and nested inside of the section key. This isn’t the way it was supposed to work with the dot syntax. Version 1.0.15 fixes this, if a key is repeated it’s merged with the parent key instead of nesting.
I also added options for defining custom folders to save entries in. At the top level you can include entries_folder
with a path to any folder on your system. Journals will all save to that folder with subdirectories for each of their keys. You can instead define entries_folder
within a journal definition, allowing each journal to have a custom location. JSON and Markdown will be written to these folders based on settings.
That should help make this tool a bit more useful, sorry for changing the data format, but better sooner than later. Check out the project page for more details.