-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New setting: Allow creating subfolders for each profile #69
Changes from 4 commits
13c7a73
e6f152e
41a2354
cc1d19a
8d89b75
f284a6d
61403f2
a402958
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -136,6 +136,15 @@ export namespace Settings { | |
label: i18n.__("settings.createSubfolder.label"), | ||
description: i18n.__("settings.createSubfolder.description"), | ||
}, | ||
createSubfolderPerProfile: { | ||
value: false, | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think we should enable this by default ... But not for already installed versions. Or what do you think? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Currently, the upstream pull request makes Joplin responsible for setting the default backup directory to the home directory (rather this plugin). As such, there are tradeoffs to having this setting enabled by default. Some reason(s) to not enable this by default:
Some reasons to enable this by default:
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. To summarize, I think enabling this by default only makes sense in the version built-in to Joplin. In other versions, the default backup location is within the profile directory, which is different for each profile. |
||
type: SettingItemType.Bool, | ||
section: "backupSection", | ||
public: true, | ||
advanced: true, | ||
label: i18n.__("settings.createSubfolderPerProfile.label"), | ||
description: i18n.__("settings.createSubfolderPerProfile.description"), | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It might make sense to use There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. My opinion is that there must be a Joplin API to backup all plugin settings and restore settings from selected plugins. |
||
}, | ||
zipArchive: { | ||
value: "no", | ||
type: SettingItemType.String, | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is what Joplin's profile structure currently looks like. However, it doesn't seem to be documented anywhere...
Reading
profiles.json
(which seems to not always exist) in the root profile directory may be another way to get this information. It also doesn't seem to be documented though.