Standardize setting names #5066
Description
Situation
We have lots of boolean settings, and because they were added over time, they do not have the same naming convention. This puts a undue burden on the user to figure out what the on/off logic is in each case, in addition to understanding what the setting does.
Proposed solution
- Edit the existing setting names so that they are consistent, except in cases where the new name would be unclear (some exceptions will always remain).
- If it makes sense, change the on/off logic to avoid double negatives. For example, if a setting is "Disable X" with a default value of
"", we may be able to change this to a setting called "X" with a default value of"on". - Edit the setting groups if needed to add clarity.
- Edit the setting descriptions if needed, though Updating in app documentation #4916 has already done some of this work.
- Write a data migration.
Context
See the new documentation that is being written about this in the markdown-based developer docs.