Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding an option to auto-remove files in .temp and .catalyst and competitive-companion extension #21

Open
lampardnk opened this issue Mar 3, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@lampardnk
Copy link

  1. My .catalyst and .temp folders have been piling up and taking unnecessary disk space after a few contests so I would like a button to remove all the contest-related files (except my solution files) from my workspace folder
  2. Adding a timer above the contest statement window would be very useful
  3. There is a browser extension named competitive-companion that passes codeforce contest data as in json to vscode and i think you guys can utilize it for easier contest-starting, so instead of providing url, can just click on extension and all done

Great extension, hope to see these new features soon

@RudreshVeerkhare
Copy link
Owner

.catalyst and .temp folders are essential for working of the extension.
.catalyst has problem data stored in it and .temp folder is temporary folder where compiled source code is stored temporarily.

You can assign a global path to .catalyst folder so that it will not be created in each workspace. Check "Save Location" in extension settings.

Adding Timer for contest is a really good idea.. I'll look into how to do it...

I've written custom scrapers for Catalyst and same exact data is not accessible using competitive-companion, similar thing would be a catalyst browser extension that would automatically trigger problem/contest loading in vscode.

Let me know your thoughts on this...

@RudreshVeerkhare RudreshVeerkhare added the enhancement New feature or request label Apr 6, 2022
Repository owner deleted a comment from luangkhot Jan 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants