copy pasting a related post from discord (01/03/2022) :
The config.edn template workflow has always bothered me : newer settings introduced with a new logseq version can’t be seen in existing graphs as the config.edn can’t be updated automatically.
Currently the only way to ‘update’ a config.edn with new settings is by checking changelogs, then manually comparing with the current github source, or by creating a new empty graph to generate a new default config.edn, then compare/edit.
There should be a way to automatically get new available setting/config options after an update.
short-term / medium-term proposal :
Maybe there should be a separate config.edn and a config-user.edn similar to style.css vs custom.css ? or similar to how config files are set-up in sublimeText or VSCode (default settings, user settings, workspace settings) :
- the default
config.ednwould contain all available options + comments and gets updated automatically, user is not supposed to edit it manually. - the
config-user.ednwould override contents of config.edn and contains specific user-settings that differ from the default of config.edn, journal queries, etc…
I realize this is only a short-term/medium-term solution that is not great in terms of user-friendliness/ux,
long term / ideal solution :
ideally a GUI should handle all options, with maybe an additional freeform textarea for advanced users who want to manually add specific flags/overrules (similar to a custom.css textarea in most website builders) .
Users should not have to edit config.edn at all, only add additional settings via the textarea.