Change config life cycle to always write on change#253
Merged
Conversation
unstrike
pushed a commit
to unstrike/Relay
that referenced
this pull request
Mar 28, 2026
* Remove release script * Rework config life cycle to always write * Format
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
1 participant
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.
Instead of manually writing and auto-reading the config, this pr switches it around the other way. Meaning we always save changes when they happen and only read on app boot or when the user clicks a button.
If there's a conflict, ie. the config file has been updated but not loaded, the user is prompted to pick which version to go with.