Wire up "clear coco data" button in Settings #394
Comments
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. |
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 I guess we could also remove the associated repositories as it won't be possible to re-add them since they have a |
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
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
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.
The text was updated successfully, but these errors were encountered: