You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I discussed some improvements to the "Reset to Default" button in #1232, but they were beyond the scope of the original issue. This is not a critical change, but we should revisit it if it starts causing problems.
I agree that I would prefer to not see workspaces reset here, since it would be a pain to recreate them. We do have other options to remove workspaces if needed, and it is pretty efficient at deleting multiple workspaces.
That said, I'm thinking about what a user would expect from the current text. We may want to add some text clarifying what is and is not included:
I'm also thinking about the practical cases where we would want to use this feature:
Reset to default options - perhaps after more defaults are added/changed after a Moonshine update
Clear the settings if they end up in a bad state because of a bug
Clear the workspaces if they get corrupted because of a bug. In this case, we might not be able to clean them up with the Workspace management interface
We could consider giving checkbox options for what to delete, with explanations for each entry. This would give more control, but it would be more complicated to implement and test. If we are interested in this, I'd need a summary of the different files we could clear separately.
Another use case would be to clear other stored data, though this might be beyond the scope of the current issue. For example, here are the different files that I see in thee Application Support directory:
One case where this might be useful is for clearing old language server or other temporary files. I see I have 11 GB of files in the java folder at the moment.
The text was updated successfully, but these errors were encountered:
I discussed some improvements to the "Reset to Default" button in #1232, but they were beyond the scope of the original issue. This is not a critical change, but we should revisit it if it starts causing problems.
One case where this might be useful is for clearing old language server or other temporary files. I see I have 11 GB of files in the
java
folder at the moment.The text was updated successfully, but these errors were encountered: