Skip to content
This repository was archived by the owner on Sep 6, 2021. It is now read-only.

Conversation

@peterflynn
Copy link
Member

Store code-folding view state in project-specific buckets for cleaner organization. If we later offer a way for users to delete stored data for a project, this ensures code folding data will be cleaned up along with
everything else. (This is also how we store Quick Edit expand/collapse state, which is very similar).

I suggested this originally in #10850 (comment). It's not super critical, but it will be much easier to do now (before code folding initially ships) -- if we did this later, we'd have to write and test additional preferences migration code.

@thehogfather does this look ok to you?

organization. If we later offer a way for users to delete stored data for
a project, this ensures code folding data will be cleaned up along with
everything else. (This is also how we store Quick Edit expand/collapse
state, which is very similar).
@abose
Copy link
Contributor

abose commented Apr 17, 2015

#10869 will be fixed by this change list. Testing the changes as this would be good to go in today's prerelease.

@abose
Copy link
Contributor

abose commented Apr 17, 2015

Thanks for submitting this fix @peterflynn. The state.json has the fold stated bucketed in the project prefs now, Also all the unit tests are passing. Also the fold states are persisted across project switch and brackets restart.
Merging .

abose added a commit that referenced this pull request Apr 17, 2015
Store code-folding view state in project-specific buckets
@abose abose merged commit 9dfbebe into master Apr 17, 2015
@abose abose deleted the pflynn/code-folding-state branch April 17, 2015 09:38
@thehogfather
Copy link
Contributor

looks great 👍

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants