Don't hide taskbook directories

[djhworld]

Is your feature request related to a problem? Please describe.

Taskbook stores its metadata under ~/.taskbook/, e.g.

• ~/.taskbook/.archive
• ~/.taskbook/.storage

If configure my taskbook config to point to say, /Users/me/google drive/taskbook, it will create the .archive and .storage folders in there.

As they are hidden, the google drive client won't sync them

Describe the solution you'd like

Under the taskbook directory, all data within should not be hidden

e.g.

/Users/me/google_drive/taskbook/archive
/Users/me/google_drive/taskbook/storage

[rjoydip-zz]

I agree with you. Also there should be some mechanism to ziped those files and synced with google drive

[djhworld]

Just looking at the state of my google drive now, I might have misrepresented the above, my taskbook.json looks like the following

{
    "taskbookDirectory": "/Users/me/google_drive/taskbook",
    "displayCompleteTasks": true,
    "displayProgressOverview": true
}

and the contents of /Users/me/google_drive/taskbook is

Projects/fftest|▶ ls -1 -a ~/google_drive/taskbook
./
../
.taskbook/
.temp/

It's the fact that taskbook creates a directory called .taskbook that is causing the issue.

[anirath]

Just looking at the state of my google drive now, I might have misrepresented the above, my taskbook.json looks like the following

{
    "taskbookDirectory": "/Users/me/google_drive/taskbook",
    "displayCompleteTasks": true,
    "displayProgressOverview": true
}

and the contents of /Users/me/google_drive/taskbook is

Projects/fftest|▶ ls -1 -a ~/google_drive/taskbook
./
../
.taskbook/
.temp/

It's the fact that taskbook creates a directory called .taskbook that is causing the issue.

This! I don't understand why taskbook just creates a hidden directory, .taskbook/, that houses more hidden content. It defeats the purpose of allowing a customizable config directory in the first place. It should definitely be that if a user designates a config directory that taskbook stores the config contents in that directory without hiding them.

Perhaps, if the user wants the contents to be hidden there could be a config option for designating filenames for the config files to be stored in the designated, or default, config directory.