Skip to content
This repository has been archived by the owner on Aug 1, 2022. It is now read-only.

Wire up "clear coco data" button in Settings #394

Closed
rudolfs opened this issue May 15, 2020 · 2 comments · Fixed by #626
Closed

Wire up "clear coco data" button in Settings #394

rudolfs opened this issue May 15, 2020 · 2 comments · Fixed by #626
Labels
feature Something that doesn't exist yet

Comments

@rudolfs
Copy link
Member

rudolfs commented May 15, 2020

Clicking the button should be the same as:
rm -rf ~/Library/Preferences/xyz.radicle.radicle && rm -rf ~/Library/Application\ Support/xyz.radicle.radicle

There's probably a more elegant way via the library we use for preference storage.

Screenshot 2020-05-15 at 09 13 26

@rudolfs rudolfs added proxy feature Something that doesn't exist yet labels May 15, 2020
@rudolfs rudolfs added this to the Release II milestone May 15, 2020
@xla
Copy link
Contributor

xla commented May 15, 2020

What you describe is wiping all the state, not just the projects. Could you outline what we actually trying to accomplish with this button, or what the common issue is we trying to address while running the app?

A larger issue with just going ahead and wiping these paths is that state is captured in more places, for example the repositories we use to initiate a project on have local state that will make it imposssible to reinitate them as radicle projects even after we wiped the state.

@rudolfs
Copy link
Member Author

rudolfs commented May 15, 2020

Whenever I do a demo of the app at bi-weekly I want to have a clean slate and create only a set of projects that I'll use for the demo. For that I clean the coco data with rm -rf ~/Library/Preferences/xyz.radicle.radicle && rm -rf ~/Library/Application\ Support/xyz.radicle.radicle. So that the project list under my Profile is empty.

I guess we could also remove the associated repositories as it won't be possible to re-add them since they have a rad branch. If we remove both the data and the state there should be a confirmation between clicking the button and performing the cleanup.

@rudolfs rudolfs removed this from the Release II milestone Jun 26, 2020
xla added a commit that referenced this issue Jul 2, 2020
Developers often are unable to start up the app because the state on
disk is not compatible with code versions or it has been corrupted in
other ways. To remedy that and provide a drastic tool to get uninitated
unstuck without the knowledge of the on disk fs layout, this change-set
introduces `yarn nuke`.

Closes #394
@xla xla closed this as completed in #626 Jul 2, 2020
xla added a commit that referenced this issue Jul 2, 2020
Developers often are unable to start up the app because the state on
disk is not compatible with code versions or it has been corrupted in
other ways. To remedy that and provide a drastic tool to get uninitated
unstuck without the knowledge of the on disk fs layout, this change-set
introduces `yarn nuke`.

Closes #394

***
* Remove unused button
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature Something that doesn't exist yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants