Feature Request: management of files and spliting and restructuring and USE GIT so that any changes that will applied with a button or shortcut can be reversed using git!
Is your feature request related to a problem? Please describe. I have used Cursor for 10 days and the main issue I have is management of codebase that seem to me (I am a new dev) super simple to be implemented.
- asking to restructure the project gives you instructions to create folders and create files.
- asking to split a file into more files gives you instructions to create those files and then you need to click apply while you are in the correct new file and clicking in the correct code snippet (asking if its the correct file)
Describe the solution you'd like
- propose a new structure new files with their content
- split the file by creating the new files and proposing the code for each
Ultimately USE GIT. in every autocompletion and every generated code and edits and file creation and stuff you can simply either commit with an auto commit message with the user prompt and the cursor plan for edits and file creation or create a branch for each chat or ctrl+K
that way you dont care about lost code or irreversible changes
that way you can have a button or shortcut where you show the user some snippet and when the user presses that button or shortcut its auto applied, the new files are auto generated, the structure changes etc
Additional context should I apply to hiring just for this feature implementation? I think I can easily implement all of this functionality!!! but I am a new dev and you state you want the best (i believe I am good [not best as I just started my dev journey], like my IQ is high and all and I am a high output person)
ultimately the user should be able to manage cursor from the chat and everything be automated.
- user asks for some feature
- cursor chat proposes x new files x edits on files x restructure and x spliting of files
- user can use up down left right keys to navigate the proposed changes and can type corrections and edits and addittions 4a. the user can either press a keystroke twice to auto apply all proposed changes. there is a new git branch created. the proposed changes gets applied. (files are auto saved). git commit. then run a final analysis of what the proposed changes did:
this can be running the command for tests, this may be checking if the code flow has any syntax errors or flow errors or type errors or missing arguments etc. so like a aftermath check of status of codebase.
4b. the other solution is again with up down left right to accept step by step, again save the files and git commit immediatly.