Move autosaved data to dedicated config file #499
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This might still need some mentions in the docs before it's ready for full review. |
jwueller
force-pushed
the
feature/autosave-file
branch
3 times, most recently
from
df2f2f4 to
989eacd
Compare
Autosaved data is instead saved to a *.autosave.cfg config file, which is automatically loaded along it's associated main *.cfg file. The goal is to eventually no longer modify user-authored configuration automatically, so that it can't introduce unintended changes. This will also allow proper version control of config files without producing unnecessarily noisy diffs. Autosaved data will keep being read from both embedded and dedicated sources, but the SAVE_CONFIG command will only write the dedicated file from now on. This maintains backwards-compatibility, while gradually migrating existing autosaved settings to the *.autosave.cfg file whenever the command keeps being used. This is just the first step in a bigger migration process, and therefore still requires some automated changes to the user config files at the moment. However, this will reduce the necessary changes, and is only required while the embedded autosave system is still supported.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Autosaved data is instead saved to a
*.autosave.cfgconfig file, which is automatically loaded along it's associated main*.cfgfile.The goal is to eventually no longer modify user-authored configuration automatically, so that it can't introduce unintended changes. This will also allow proper version control of config files without producing unnecessarily noisy diffs.
Autosaved data will keep being read from both embedded and dedicated sources, but the
SAVE_CONFIGcommand will only write the dedicated file from now on. This maintains backwards-compatibility, while gradually migrating existing autosaved settings to the*.autosave.cfgfile whenever the command keeps being used.This is just the first step in a bigger migration process, and therefore still requires some automated changes to the user config files at the moment. However, this will reduce the necessary changes, and is only required while the embedded autosave system is still supported.
Checklist