Initial implementation of per project settings#1700
Draft
Conversation
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.
In order to more fully restore the working state, certain states need to be saved on a per project basis.
For example
This is an initial PR for doing this, restoring only one boolean setting - whether the project is expanded in the sidebar.
Rather than create our own backend, a relocatable GSettings schema is used. The only drawback is the possible accumulation of unused schemas for abandoned projects. It is not clear how this can be managed through the UI.
At the moment all folders opened as "projects" in the sidebar generate a corresponding setting schema - to be decided whether to limit this to e.g. git repositories.