Thank you for your contribution - this should make the config more readable.
Especially now, when we use dual pane settings editor when editing settings with command ST: Settings.
There are some minor things that could be improved in your PR:
the trailing commas in some settings you have added - those trailing commas are not a valid JSON and threrefore I would prefer if we don't introduce new json incompatibilities. I know the comments in JSON specification are not allowed as well, but those are neccessary evil for documentation and ease of use purposses.
I would keep the order unchanged, namely the settings debug, safe_limit, unescape_quotes were specificly moved to the latter part of settings file, because they are either of a low interest to an average end user or they are not working properly with all DB's (and threrfore might be removed in next releases).
Thank you for your contribution - this should make the config more readable. Especially now, when we use dual pane settings editor when editing settings with command
ST: Settings.There are some minor things that could be improved in your PR:
debug,safe_limit,unescape_quoteswere specificly moved to the latter part of settings file, because they are either of a low interest to an average end user or they are not working properly with all DB's (and threrfore might be removed in next releases).