Don't create empty settings_old folder for fresh installs#2735
Merged
joeyballentine merged 1 commit intochaiNNer-org:mainfrom Apr 4, 2024
Merged
Don't create empty settings_old folder for fresh installs#2735joeyballentine merged 1 commit intochaiNNer-org:mainfrom
settings_old folder for fresh installs#2735joeyballentine merged 1 commit intochaiNNer-org:mainfrom
Conversation
joeyballentine
approved these changes
Apr 4, 2024
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This fixes a small oversight in #2640.
Fresh installs have neither a
settings.jsonnor asettingsfolder, but node local storage will create thesettingsfolder. This cause fresh installs to always create an emptysettingsfolder that was then migrated to asettings_oldfolder.Of course, none of this was necessary. So I now check whether the
settingsfolder exists before doing the migration.